|| ||Arjan van de Ven <arjan-AT-linux.intel.com> |
|| ||Jean Pihet <jean.pihet-AT-newoldbits.com> |
|| ||Re: [PATCH] tracing, perf: add more power related events |
|| ||Wed, 22 Sep 2010 09:32:51 -0700|
|| ||Thomas Renninger <trenn-AT-suse.de>, Ingo Molnar <mingo-AT-elte.hu>,
Peter Zijlstra <peterz-AT-infradead.org>,
Len Brown <len.brown-AT-intel.com>, arjan-AT-infradead.org,
Kevin Hilman <khilman-AT-deeprootsystems.com>,
|| ||Article, Thread
On 9/22/2010 8:36 AM, Jean Pihet wrote:
> On Wed, Sep 22, 2010 at 5:33 PM, Arjan van de Ven<firstname.lastname@example.org> wrote:
>> On 9/22/2010 8:31 AM, Jean Pihet wrote:
>>> Here is a patch that redefines the power events API. The advantages
>>> are: easier maintainance of the kernel and the
>>> user space tools, a cleaner and more generic interface, more
>>> parameters for fine tracing and even documentation!
>>> Thomas, this patch has your patch above merged in ('power-trace: Use
>>> power_switch_state instead of power_start and power_end'). The revised
>>> ACPI patch is coming asap.
>>> The trace points for x86 and OMAP are also udated accordingly.
>>> The pytimechart tool needs an update for the new API. This can be done
>>> as soon as the kernel code gets merged in.
>> unfortunately this code is changing a userspace ABI... we really shouldn't
>> do that if we can avoid it,
>> and here we can avoid it.
>> applications ARE using this stuff!
> 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
.... and likely many local tools that aren't.
To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)