From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: [RFD] Add debugfs for cpuidle ? Date: Thu, 24 May 2018 10:47:54 +0200 Message-ID: References: <516d8599-8038-7b47-a3f5-640bf13856c2@linaro.org> <2682482.uFPN0cxrGI@aspire.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <2682482.uFPN0cxrGI@aspire.rjw.lan> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Linux PM mailing list List-Id: linux-pm@vger.kernel.org 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 ? -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog