linux-kernel - Re: [PATCH] tracing, perf: add more power related events

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimcXHBw+cbPWATXv=VGFwCHvf8Has4H6bLXPFd=@mail.gmail.com>
Date:	Mon, 16 Aug 2010 13:25:43 +0200
From:	Jean Pihet <jean.pihet@...oldbits.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	Thomas Renninger <trenn@...e.de>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Len Brown <len.brown@...el.com>,
	Arjan Van De Ven <arjan@...ux.intel.com>
Subject: Re: [PATCH] tracing, perf: add more power related events

On Mon, Aug 16, 2010 at 1:15 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Mon, 2010-08-16 at 13:09 +0200, Jean Pihet wrote:
>> This patch adds new generic events for dynamic power management
>> tracing:
>> - clock events class: used for clock enable/disable and for
>>    clock rate change,
>> - power_domain events class: used for power domains transitions.
>>
>> The OMAP architecture is using the new events for PM debugging, however
>> the new events are made generic enough to be used by all platforms.
>
> Even though I'm blissfully ignorant on power stuffs, the proposed set of
> trace thingies doesn't appear to even start covering x86..
Ok, let's discuss it! The intention is to provide new generic events.

>
> CC'ed people who know more on the subject.
>
Thanks!
--
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/