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: Mon, 08 Apr 2024 03:27:47 +0000	[thread overview]
Message-ID: <bug-217931-137361-A5Lz7B0q7q@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 #59 from Perry Yuan(AMD) (Perry.Yuan@amd.com) ---
(In reply to Artem S. Tashkinov from comment #56)
> Here's my report for 6.8.4 and Ryzen 7 7840HS:
> 
> 1. Setting scaling_max_freq works, cool, but you cannot go below 544MHz. You
> can set 400MHz but the CPU will continue to jump to 544MHz, not a big deal.
> 
> 2. Setting scaling_min_freq sort of works, the CPU _prefers_ to stay at this
> specified frequency but occasionally drops to 400MHz. Then, the CPU doesn't
> totally respect it, i.e. for values below 1.4GHz it stays around 1397MHz.
> The relationship is not linear, setting 4GHz results in the CPU preferring
> 3766Mhz. Or 2GHz -> 1982MHz. Not a big deal. Unlikely anyone would want to
> set the lowest frequency.
> 
> 3. /sys/devices/system/cpu/amd_pstate/cpb_boost is missing altogether:
> 
> # find /sys -iname '*boost*'
> [nothing]
> 
> So, my only remaining question is where's boost support? Or it's not
> supported for all Zen CPUs?
> 
> Thanks a lot for your work regardless!
1.  please try to apply the two patches for your cpb testing. 
https://lore.kernel.org/lkml/cover.1711335714.git.perry.yuan@amd.com/
https://lore.kernel.org/lkml/Zfqv3ckVU4km+RLr@BLR-5CG11610CF.amd.com/

2. are you testing under EPP driver mode? the 400MHz is the lowest freq,
however it dose not mean the CPU will be keeping at 400MHz, it will wake up and
idle and  bump up frequency shortly according to the workload.  you need to
know, when the Core is idle, kernel will not get the realtime frequency by
APERF/MPERF, cpufreq just show the lowest freq as 400MHz. It is not an issue. 

There is one idle frequency defined by power firmware, it is 1.4GHz for some
client system, the lowest active frequency is not 400MHz, it is 1.4GHz.  so you
have no need to worry the 1.4GHz or 400MHz, it is not a problem.

3. the invalid max frequency value issue is caused by wrong highest perf value
defined by pstate driver, I have been working a solution to fix that. with EPP
driver mode, it will not cause any performance problem, just a little
uncomfortable to see the wrong value listed.  

Perry.

-- 
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-04-08  3:27 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 [this message]
2024-06-12 12:01 ` bugzilla-daemon
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-A5Lz7B0q7q@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).