All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Dave Jones <davej@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	David Sharp <dhsharp@google.com>,
	Vaibhav Nagarnaik <vnagarnaik@google.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event
Date: Thu, 17 May 2012 10:06:52 +0200	[thread overview]
Message-ID: <20120517080651.GC17419@gmail.com> (raw)
In-Reply-To: <4FB40B2B.703@linux.intel.com>


* 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

  reply	other threads:[~2012-05-17  8:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 13:44 [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event Steven Rostedt
2012-05-16 17:24 ` [RFC][PATCH v2] " Steven Rostedt
2012-05-16 19:33 ` [RFC][PATCH] " Linus Torvalds
2012-05-16 19:36   ` Arjan van de Ven
2012-05-16 19:47     ` Steven Rostedt
2012-05-16 19:51     ` Linus Torvalds
2012-05-16 20:03       ` Steven Rostedt
2012-05-17  8:04         ` Ingo Molnar
2012-05-16 20:00   ` Steven Rostedt
2012-05-16 20:04     ` Linus Torvalds
2012-05-16 20:07       ` Arjan van de Ven
2012-05-16 20:13         ` Steven Rostedt
2012-05-16 20:14         ` Dave Jones
2012-05-16 20:16           ` Arjan van de Ven
2012-05-17  8:06             ` Ingo Molnar [this message]
2012-05-17 12:11               ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120517080651.GC17419@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=davej@redhat.com \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vnagarnaik@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.