[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1285173835.2275.1026.camel@laptop>
Date: Wed, 22 Sep 2010 18:43:55 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Arjan van de Ven <arjan@...ux.intel.com>
Cc: Jean Pihet <jean.pihet@...oldbits.com>,
Thomas Renninger <trenn@...e.de>, Ingo Molnar <mingo@...e.hu>,
Len Brown <len.brown@...el.com>, arjan@...radead.org,
Kevin Hilman <khilman@...prootsystems.com>,
linux-kernel@...r.kernel.org, discuss@...swatts.org,
linux-pm@...ts.linux-foundation.org, linux-omap@...r.kernel.org,
linux-perf-users@...r.kernel.org, linux-trace-users@...r.kernel.org
Subject: Re: [PATCH] tracing, perf: add more power related events
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists