[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2b2b8da209a9cf22e80b089a698f78dd5c2f5fb.camel@intel.com>
Date: Sun, 27 Nov 2022 00:43:24 +0800
From: Zhang Rui <rui.zhang@...el.com>
To: Doug Smythies <dsmythies@...us.net>,
'Kajetan Puchalski' <kajetan.puchalski@....com>,
rafael@...nel.org
Cc: daniel.lezcano@...aro.org, lukasz.luba@....com,
Dietmar.Eggemann@....com, yu.chen.surf@...il.com,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v4 0/2] cpuidle: teo: Introduce util-awareness
> > Workflow: sleeping ebizzy 128 threads.
> > Variable: interval (uSecs).
> > Performance Results:
> > http://smythies.com/~doug/linux/idle/teo-util/graphs/ebizzy-128-perf.png
> > Performance power and idle data:
> > http://smythies.com/~doug/linux/idle/teo-util/ebizzy/perf/
>
> for the "Idle state 0/1/2/3 was too deep" graphs, may I know how you
> assert that an idle state is too deep/shallow?
>
is this got from the cpu_idle_miss trace event?
thanks,
rui
Powered by blists - more mailing lists