All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 211305] schedutil selects low P-States on AMD EPYC with frequency invariance
Date: Fri, 12 Feb 2021 21:15:46 +0000	[thread overview]
Message-ID: <bug-211305-137361-YODeokYmAB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211305-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=211305

--- Comment #10 from Matt McDonald (gardotd426@gmail.com) ---
Okay so that's *way* worse. 

Everything's limited and locked to 2.2GHz. And yes, it's actually running at
2.2GHz, it's not misreporting. My Geekbench score was less than a third of what
it should be

cat /proc/cpuinfo | grep MHz
cpu MHz         : 2200.000
cpu MHz         : 2200.088
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2199.982
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000
cpu MHz         : 2200.000


 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq
2199680
2199981
2195932
2199979
2195634
2198726
2199437
2195587
2197662
2198924
2198856
2195535
2196402
2199234
2199880
2195064


analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 2.20 GHz - 6.00 GHz
  available frequency steps:  3.80 GHz, 2.80 GHz, 2.20 GHz
  available cpufreq governors: performance schedutil
  current policy: frequency should be within 2.20 GHz and 2.20 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: 2.20 GHz (asserted by call to hardware)
  boost state support:
    Supported: yes
    Active: no
    Boost States: 0
    Total States: 3
    Pstate-P0:  1000MHz
    Pstate-P1:  700MHz
    Pstate-P2:  500MHz


Both schedutil and performance governors had no effect. 

But I do see in that cpupower output that it says the hardware limits happen to
be 2.20GHz to 6.0GHz.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2021-02-12 21:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21  0:55 [Bug 211305] New: schedutil selects low P-States on AMD EPYC with frequency invariance bugzilla-daemon
2021-01-21  0:57 ` [Bug 211305] " bugzilla-daemon
2021-01-21  0:59 ` bugzilla-daemon
2021-01-21  1:00 ` bugzilla-daemon
2021-01-21  1:03 ` bugzilla-daemon
2021-01-27 21:18 ` bugzilla-daemon
2021-02-12 17:28 ` bugzilla-daemon
2021-02-12 18:19   ` Rafael J. Wysocki
2021-02-12 18:19 ` bugzilla-daemon
2021-02-12 19:12 ` bugzilla-daemon
2021-02-12 20:39 ` bugzilla-daemon
2021-02-12 21:15 ` bugzilla-daemon [this message]
2021-02-12 22:00 ` bugzilla-daemon
2021-02-15 13:52 ` bugzilla-daemon
2021-02-15 13:54 ` bugzilla-daemon
2021-02-15 13:55 ` bugzilla-daemon
2021-02-15 14:04 ` bugzilla-daemon
2021-02-15 14:43 ` bugzilla-daemon
2021-02-15 14:47 ` bugzilla-daemon
2021-02-15 15:09 ` bugzilla-daemon
2021-02-15 15:30 ` bugzilla-daemon

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=bug-211305-137361-YODeokYmAB@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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.