linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 217931] amd-pstate lacks crucial features: CPU frequency and boost control
Date: Wed, 12 Jun 2024 12:01:10 +0000	[thread overview]
Message-ID: <bug-217931-137361-XA1YZUaGc1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217931-137361@https.bugzilla.kernel.org/>

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

--- Comment #60 from Artem S. Tashkinov (aros@gmx.com) ---
Under Linux 6.9.4 the amd-pstate driver doesn't adhere to the maximum set
frequency for my Ryzen 7 5800X:

# cpupower frequency-info
analyzing CPU 10:
  driver: amd-pstate-epp
  CPUs which run at the same hardware frequency: 10
  CPUs which need to have their frequency coordinated by software: 10
  maximum transition latency:  Cannot determine or is not supported.
  hardware limits: 550 MHz - 4.93 GHz
  available cpufreq governors: performance powersave
  current policy: frequency should be within 550 MHz and 1000 MHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 3.54 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    AMD PSTATE Highest Performance: 166. Maximum Frequency: 4.93 GHz.
    AMD PSTATE Nominal Performance: 128. Nominal Frequency: 3.80 GHz.
    AMD PSTATE Lowest Non-linear Performance: 59. Lowest Non-linear Frequency:
1.75 GHz.
    AMD PSTATE Lowest Performance: 19. Lowest Frequency: 550 MHz.

# lscpu -ae
CPU SOCKET CORE L1d:L1i:L2:L3 ONLINE    MAXMHZ   MINMHZ       MHZ
  0      0    0 0:0:0:0          yes 4929.0000 550.0000 3124.8250
  1      0    1 1:1:1:0          yes 4929.0000 550.0000 3585.6809
  2      0    2 2:2:2:0          yes 4929.0000 550.0000  550.0000
  3      0    3 3:3:3:0          yes 4929.0000 550.0000 3554.8350
  4      0    4 4:4:4:0          yes 4929.0000 550.0000 3434.6189
  5      0    5 5:5:5:0          yes 4929.0000 550.0000 3589.3491
  6      0    6 6:6:6:0          yes 4929.0000 550.0000  550.0000
  7      0    7 7:7:7:0          yes 4929.0000 550.0000  550.0000
  8      0    0 0:0:0:0          yes 4929.0000 550.0000 3377.0410
  9      0    1 1:1:1:0          yes 4929.0000 550.0000 3545.8970
 10      0    2 2:2:2:0          yes 4929.0000 550.0000 3487.3730
 11      0    3 3:3:3:0          yes 4929.0000 550.0000 3185.1221
 12      0    4 4:4:4:0          yes 4929.0000 550.0000  550.0000
 13      0    5 5:5:5:0          yes 4929.0000 550.0000 4315.6221
 14      0    6 6:6:6:0          yes 4929.0000 550.0000 3148.2390
 15      0    7 7:7:7:0          yes 4929.0000 550.0000 3555.2141

---------------------------------------------------------------------------------------

And it's even more confusing since we now have:

1. * /sys/devices/system/cpu/cpufreq/policyX/scaling_available_governors
  performance powersave

2. How is it related to 

/sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference which can
be of 
default performance balance_performance balance_power power?

3. And what's the "default" state?

---------------------------------------------------------------------------------------

It's all so simple with acpi-cpufreq :-(

1. I can enable/disable boost (not possible under amd-pstate on 6.9.4)
2. I can easily set maximum CPU core clock frequency (not possible for Ryzen 7
5800X under amd-pstate on 6.9.4)
3. I can set governors (performance powersave ondemand conservative)

With amd-pstate it's a huge maddening mess.

I'm going back to acpi-cpufreq until 6.10 at least for my desktop.

-- 
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:[~2024-06-12 12:01 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 11:06 [Bug 217931] New: amd-pstate lacks crucial features: CPU frequency and boost control bugzilla-daemon
2023-09-20 11:07 ` [Bug 217931] " bugzilla-daemon
2023-09-20 13:15 ` [Bug 217931] New: " Bagas Sanjaya
2023-09-20 13:15 ` [Bug 217931] " bugzilla-daemon
2023-09-20 13:28 ` bugzilla-daemon
2023-09-21  5:25 ` bugzilla-daemon
2023-09-21  8:21 ` bugzilla-daemon
2023-09-21  8:23 ` bugzilla-daemon
2023-09-21 18:24 ` bugzilla-daemon
2023-09-21 18:27 ` bugzilla-daemon
2023-10-10 12:57 ` bugzilla-daemon
2023-10-10 13:00 ` bugzilla-daemon
2023-10-18 18:38 ` bugzilla-daemon
2023-12-28 19:27 ` bugzilla-daemon
2023-12-28 19:27 ` bugzilla-daemon
2024-01-07  2:38 ` bugzilla-daemon
2024-01-18  7:58 ` bugzilla-daemon
2024-01-18 16:38 ` bugzilla-daemon
2024-01-18 16:41 ` bugzilla-daemon
2024-01-18 16:49 ` bugzilla-daemon
2024-01-18 16:54 ` bugzilla-daemon
2024-01-18 17:08 ` bugzilla-daemon
2024-01-18 19:22 ` bugzilla-daemon
2024-01-18 19:48 ` bugzilla-daemon
2024-01-18 19:53 ` bugzilla-daemon
2024-01-18 20:14 ` bugzilla-daemon
2024-01-18 20:22 ` bugzilla-daemon
2024-01-18 22:39 ` bugzilla-daemon
2024-01-19  0:23 ` bugzilla-daemon
2024-01-19  3:31 ` bugzilla-daemon
2024-01-19  3:32 ` bugzilla-daemon
2024-01-19  7:05 ` bugzilla-daemon
2024-01-19 18:48 ` bugzilla-daemon
2024-01-19 19:11 ` bugzilla-daemon
2024-01-19 21:38 ` bugzilla-daemon
2024-01-20  0:20 ` bugzilla-daemon
2024-01-20  2:24 ` bugzilla-daemon
2024-01-20  5:48 ` bugzilla-daemon
2024-01-20 23:57 ` bugzilla-daemon
2024-01-22 21:46 ` bugzilla-daemon
2024-01-29  7:53 ` bugzilla-daemon
2024-01-29 22:36 ` bugzilla-daemon
2024-01-30 14:03 ` bugzilla-daemon
2024-02-01  7:40 ` bugzilla-daemon
2024-02-01  7:43 ` bugzilla-daemon
2024-02-01  8:56 ` bugzilla-daemon
2024-02-01  9:00 ` bugzilla-daemon
2024-02-01  9:58 ` bugzilla-daemon
2024-02-01 10:48 ` bugzilla-daemon
2024-02-01 12:01 ` bugzilla-daemon
2024-02-01 12:04 ` bugzilla-daemon
2024-02-01 12:05 ` bugzilla-daemon
2024-02-02  3:02 ` bugzilla-daemon
2024-02-02  3:23 ` bugzilla-daemon
2024-02-02  3:26 ` bugzilla-daemon
2024-02-20 23:01 ` bugzilla-daemon
2024-02-21  3:14 ` bugzilla-daemon
2024-04-06  1:38 ` bugzilla-daemon
2024-04-06  1:39 ` bugzilla-daemon
2024-04-06  1:43 ` bugzilla-daemon
2024-04-08  3:27 ` bugzilla-daemon
2024-06-12 12:01 ` bugzilla-daemon [this message]
2024-06-12 12:03 ` bugzilla-daemon
2024-06-12 15:05 ` bugzilla-daemon
2025-02-17  7:23 ` bugzilla-daemon
2025-02-17  7:48 ` bugzilla-daemon
2025-02-17  7:50 ` bugzilla-daemon
2025-02-17  7:51 ` bugzilla-daemon
2025-02-17  7:59 ` bugzilla-daemon
2025-02-17 17:38 ` bugzilla-daemon
2025-02-17 18:44 ` bugzilla-daemon
2025-02-17 18:44 ` bugzilla-daemon
2025-02-17 18:55 ` bugzilla-daemon
2025-02-17 18:56 ` bugzilla-daemon
2025-02-17 19:12 ` bugzilla-daemon
2025-02-17 19:31 ` bugzilla-daemon
2025-02-17 20:11 ` bugzilla-daemon
2025-02-17 20:23 ` bugzilla-daemon
2025-02-17 20:31 ` bugzilla-daemon
2025-02-17 20:32 ` bugzilla-daemon
2025-02-17 21:21 ` bugzilla-daemon
2025-02-17 21:56 ` bugzilla-daemon
2025-02-17 22:09 ` bugzilla-daemon
2025-02-18  9:53 ` 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-217931-137361-XA1YZUaGc1@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).