linux-kernel - Re: [RFD] Add debugfs for cpuidle ?

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] [day] [month] [year] [list]

Message-ID: <aafd9a8a-9007-fca4-6ef8-a72920513d5c@linaro.org>
Date:   Thu, 30 Aug 2018 10:24:53 +0200
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     "Rafael J. Wysocki" <rjw@...ysocki.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux PM mailing list <linux-pm@...r.kernel.org>
Subject: Re: [RFD] Add debugfs for cpuidle ?

On 30/08/2018 10:22, Ulf Hansson wrote:
> On 24 May 2018 at 10:47, Daniel Lezcano <daniel.lezcano@...aro.org> wrote:
>> 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 ?
>>
> 
> Daniel,
> 
> Any chance that you have some draft version of actual code implementing this?
> 
> I would be very interested to try then - or help out to implement
> this, in case you haven't started yet.

Yes, I have a draft version, a bit incomplete but easy to fill. I'm just
not fully convinced about the metrics we need yet.


-- 
 <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