All of lore.kernel.org
 help / color / mirror / Atom feed
From: A L <mail@lechevalier.se>
To: linux-pm@vger.kernel.org
Subject: Schedutil scaling governor is missing time_in_state
Date: Sat, 11 Jul 2020 19:49:44 +0200 (GMT+02:00)	[thread overview]
Message-ID: <6dfd665.397441d8.1733eff4aa2@lechevalier.se> (raw)

Hello,

I am testing the 'schedutil' scaling govenor.

So far it seems to give good results in terms of reduced thermals and energy consumption.

One difference compared to 'ondemand' that I noticed is that /sys/devices/system/cpu/cpu*/cpufreq/stats/time_in_state is never updated. It is always empty. This creates a problem for my munin graphs that log the average CPU frequency for each core.

Example with 'ondemand'
cpu0/cpufreq/stats/time_in_state:3500000 3869872
cpu0/cpufreq/stats/time_in_state:2300000 581995
cpu0/cpufreq/stats/time_in_state:1600000 6895937
cpu0/cpufreq/stats/total_trans:1746213
cpu0/cpufreq/stats/trans_table:   From  :    To
cpu0/cpufreq/stats/trans_table:         :   3500000   2300000   1600000
cpu0/cpufreq/stats/trans_table:  3500000:         0     49335     62476
cpu0/cpufreq/stats/trans_table:  2300000:     58219         0    756854
cpu0/cpufreq/stats/trans_table:  1600000:     53591    765738         0

Example with 'schedutil'
cpu3/cpufreq/stats/time_in_state:<empty>
cpu3/cpufreq/stats/total_trans:1751092
cpu3/cpufreq/stats/trans_table:<empty>

Is this a known problem or perhaps a design choice?

This is on kernel 5.7.8 on and AMD Athlon 3000G CPU using 'acpi_cpufreq' scaling_driver.

Anders


             reply	other threads:[~2020-07-11 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 17:49 A L [this message]
2020-09-03 11:02 ` Schedutil scaling governor is missing time_in_state Viresh Kumar

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=6dfd665.397441d8.1733eff4aa2@lechevalier.se \
    --to=mail@lechevalier.se \
    --cc=linux-pm@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.