Re: [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event [LWN.net]

From:		Ingo Molnar <mingo-AT-kernel.org>
To:		Arjan van de Ven <arjan-AT-linux.intel.com>
Subject:		Re: [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event
Date:		Thu, 17 May 2012 10:06:52 +0200
Message-ID:		<20120517080651.GC17419@gmail.com>
Cc:		Dave Jones <davej-AT-redhat.com>, Linus Torvalds <torvalds-AT-linux-foundation.org>, Steven Rostedt <rostedt-AT-goodmis.org>, LKML <linux-kernel-AT-vger.kernel.org>, Ingo Molnar <mingo-AT-elte.hu>, Frederic Weisbecker <fweisbec-AT-gmail.com>, David Sharp <dhsharp-AT-google.com>, Vaibhav Nagarnaik <vnagarnaik-AT-google.com>, Peter Zijlstra <peterz-AT-infradead.org>, Andrew Morton <akpm-AT-linux-foundation.org>
Archive-link:		Article, Thread

* Arjan van de Ven <arjan@linux.intel.com> wrote:

> > One possibility would be a config symbol to enable the 
> > deprecated field (kind of like what we did with compat 
> > vdso).  Distros that have a new enough powertop can then 
> > disable it.
> 
> this isn't really about distro kernels; a distro that pushes a 
> 3.7 kernel to Fedora 15 might as well do a powertop upgrade.. 
> the later is much simpler and lighter (the main difference 
> between 1.98 and 2.0 is the use of the perfevent library 
> anyway)
> 
> it's about people who compile their own upstream kernel...

Nor should we waste too much time over these 4 bytes really. Is 
the kernel really in such a good shape that we must spend our 
time trying to break working apps, over a mostly cosmetic detail 
in an ABI which will soon be messed up with our next set up 
mistakes anyway? ;-)

Thanks,

	Ingo

(Log in to post comments)