From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
Thomas Renninger <trenn@suse.de>, Ingo Molnar <mingo@elte.hu>,
Len Brown <len.brown@intel.com>,
arjan@infradead.org, Kevin Hilman <khilman@deeprootsystems.com>,
linux-kernel@vger.kernel.org, discuss@lesswatts.org,
linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org,
linux-perf-users@vger.kernel.org,
linux-trace-users@vger.kernel.org
Subject: Re: [PATCH] tracing, perf: add more power related events
Date: Wed, 22 Sep 2010 18:43:55 +0200 [thread overview]
Message-ID: <1285173835.2275.1026.camel@laptop> (raw)
In-Reply-To: <4C9A2FB3.105@linux.intel.com>
On Wed, 2010-09-22 at 09:32 -0700, Arjan van de Ven wrote:
> > What are the apps that are using it? I know about builtin-timechart,
> > pytimechart. Is powertop using this as well?
>
> powertop 2.x codebase is as well.
>
> and a bunch of tools we have internal here at Intel.
>
> the thing with ABIs is that you don't know how many users you have.. at
> least here you know the lower bound is 3 different tools that are open
> source.
> .... and likely many local tools that aren't.
These tools should be smart enough to look up the tracepoint name, fail
it its not available, read the tracepoint format, again fail if not
compatible.
I really object to treating tracepoints as ABI and being tied to any
implementation details due to that.
Tools really should be flexible and allow for change.
next prev parent reply other threads:[~2010-09-22 16:44 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 7:21 Jean Pihet
2010-09-07 8:01 ` Jean Pihet
2010-09-08 6:53 ` Ingo Molnar
2010-09-09 7:15 ` Jean Pihet
2010-09-09 7:54 ` Ingo Molnar
2010-09-15 15:45 ` Jean Pihet
2010-09-17 13:08 ` Thomas Renninger
2010-09-17 14:05 ` Jean Pihet
2010-09-17 14:24 ` Ingo Molnar
2010-09-17 15:36 ` Thomas Renninger
2010-09-17 16:24 ` Ingo Molnar
2010-09-17 22:26 ` Thomas Renninger
2010-09-22 15:31 ` Jean Pihet
2010-09-22 15:33 ` Arjan van de Ven
2010-09-22 15:36 ` Jean Pihet
2010-09-22 16:32 ` Arjan van de Ven
2010-09-22 16:43 ` Peter Zijlstra [this message]
2010-09-22 17:06 ` Arjan van de Ven
2010-09-22 17:30 ` Peter Zijlstra
2010-09-22 18:15 ` Steven Rostedt
2010-09-22 18:23 ` Ingo Molnar
2010-09-22 18:30 ` Peter Zijlstra
2010-09-22 18:26 ` Peter Zijlstra
2010-09-22 18:36 ` Steven Rostedt
2010-09-22 18:43 ` Peter Zijlstra
2010-09-22 19:14 ` Frank Ch. Eigler
2010-09-22 17:36 ` Thomas Renninger
2010-09-22 16:47 ` Peter Zijlstra
2010-09-22 17:57 ` Thomas Renninger
2010-09-22 18:13 ` Arjan van de Ven
2010-09-22 18:34 ` Thomas Renninger
2010-09-22 18:09 ` Rafael J. Wysocki
2010-09-22 18:49 ` Rafael J. Wysocki
2010-09-28 8:35 ` Jean Pihet
2010-09-28 21:22 ` Rafael J. Wysocki
2010-09-28 21:43 ` Jean Pihet
2010-09-28 22:05 ` Rafael J. Wysocki
2010-09-28 21:45 ` Arjan van de Ven
2010-09-28 22:05 ` Rafael J. Wysocki
2010-09-29 7:49 ` Thomas Renninger
2010-09-29 9:25 ` Jean Pihet
2010-10-04 17:55 ` [linux-pm] " Pavel Machek
2010-09-17 15:29 ` Thomas Renninger
2010-09-17 21:58 ` Thomas Renninger
2010-09-17 22:04 ` Thomas Renninger
2010-09-17 22:10 ` Thomas Renninger
2010-09-17 22:17 ` Thomas Renninger
2010-09-17 8:28 ` [tip:perf/core] tracing, perf: Add " tip-bot for Jean Pihet
-- strict thread matches above, loose matches on Subject: below --
2010-08-16 11:09 [PATCH] tracing, perf: add " Jean Pihet
2010-08-16 11:15 ` Peter Zijlstra
2010-08-16 11:25 ` Jean Pihet
2010-08-23 10:25 ` Jean Pihet
2010-09-03 17:00 ` Jean Pihet
2010-09-03 18:05 ` Thomas Renninger
2010-09-03 19:55 ` Ingo Molnar
2010-09-03 20:10 ` Thomas Renninger
2010-09-03 20:28 ` Ingo Molnar
2010-09-03 22:56 ` Arjan van de Ven
2010-09-04 8:18 ` Ingo Molnar
2010-09-06 8:56 ` Jean Pihet
2010-09-06 10:42 ` Thomas Renninger
2010-09-06 11:27 ` Jean Pihet
2010-09-06 12:00 ` Thomas Renninger
2010-09-07 7:28 ` Jean Pihet
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=1285173835.2275.1026.camel@laptop \
--to=peterz@infradead.org \
--cc=arjan@infradead.org \
--cc=arjan@linux.intel.com \
--cc=discuss@lesswatts.org \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@deeprootsystems.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=trenn@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome