From: Arjan van de Ven <arjan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
David Sharp <dsharp@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: Wed, 16 May 2012 12:36:18 -0700 [thread overview]
Message-ID: <4FB401B2.1010906@linux.intel.com> (raw)
In-Reply-To: <CA+55aFzVngkixn-t0mK8QqgnPhCzN2AsUtzfZ3BkLiJAcjNOzQ@mail.gmail.com>
On 5/16/2012 12:33 PM, Linus Torvalds wrote:
> On Wed, May 16, 2012 at 6:44 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
>>
>> But this change will break PowerTop v1. Thus my question is, how long do
>> we need to keep this wasted space in the ring buffers to satisfy an out
>> of date tool?
>
> The wasted space seems of limited importance.
>
> More important is to check which distros have the new powertop.
>
> F16 and F17 seem to have powertop-1.98, which I assume is the new
> world order already. But maybe I assume incorrectly.
this is the one that will break
>
> F14 (which I personally still use, since it doesn't have gnome3) is 1.13.
this one is fine, it does not use perf events at all.
next prev parent reply other threads:[~2012-05-16 19:36 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 [this message]
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
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=4FB401B2.1010906@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dsharp@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.