From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: [RFD] Add debugfs for cpuidle ?
Date: Thu, 24 May 2018 10:47:54 +0200 [thread overview]
Message-ID: <bcdbf067-4213-18ed-6d30-dc0dd2376c02@linaro.org> (raw)
In-Reply-To: <2682482.uFPN0cxrGI@aspire.rjw.lan>
On 24/05/2018 10:28, Rafael J. Wysocki wrote:
> On Thursday, May 24, 2018 10:14:31 AM CEST Daniel Lezcano wrote:
>>
>> Hi all,
>
> Hi,
>
>> would it be interesting to add debugfs metrics for cpuidle in order
>> to read some statistics from there and investigate the behavior ?
>
> What exactly would you like to see in there?
It could be interesting to have statistics on a per cpu and global basis
for:
- prediction accuracy:
/sys/kernel/debug/cpuidle/prediction/[good|over|under]
/sys/kernel/debug/cpuidle/cpu*/state*/prediction/[good|over|under]
- exit latency
In addition, it is often the case the idle states values are dropped
randomly, it is interesting to see the average exit latency for the
states. That could give also an indication the cluster idle state success.
/sys/kernel/debug/cpuidle/state*/latency/[min|max|avg|stddev]
/sys/kernel/debug/cpuidle/cpu*/state*/prediction/[min|max|avg|stddev]
And perhaps more information like the tick stopped stat ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2018-05-24 8:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 8:14 [RFD] Add debugfs for cpuidle ? Daniel Lezcano
2018-05-24 8:28 ` Rafael J. Wysocki
2018-05-24 8:47 ` Daniel Lezcano [this message]
2018-05-24 9:39 ` Rafael J. Wysocki
2018-08-30 8:22 ` Ulf Hansson
2018-08-30 8:24 ` Daniel Lezcano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcdbf067-4213-18ed-6d30-dc0dd2376c02@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox