[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201009290005.18704.rjw@sisk.pl>
Date: Wed, 29 Sep 2010 00:05:18 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
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>,
Peter Zijlstra <peterz@...radead.org>,
Len Brown <len.brown@...el.com>, arjan@...radead.org,
Kevin Hilman <khilman@...prootsystems.com>,
linux-kernel@...r.kernel.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 Tuesday, September 28, 2010, Arjan van de Ven wrote:
> On 9/28/2010 2:22 PM, Rafael J. Wysocki wrote:
> > On Tuesday, September 28, 2010, Jean Pihet wrote:
> >> Hi,
> > Hi,
> >
> >> Here is what I am proposing, in reply to all your comments:
> >>
> >> 1) rename the events to match Thomas's proposal:
> >> power:power_cpu_cstate
> >> power:power_cpu_pstate
> >> power:power_cpu_sstate
> > If that sstate thing is going to mean "suspend", then please drop it.
> > "Suspend" is not a state, let alone a CPU state. It is a procedure by which
> > the (entire) system is put into a sleep state (that is not confined to CPUs).
>
> there are also non-suspend S states, like S0i1 and S0i3 (supported in
> the current Intel "Moorestown" platform)
>
> so it's slightly more complex than "just" suspend :)
That's exactly why I used the conditional above. :-)
--
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