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, 21 Feb 2024 03:14:06 +0000 [thread overview]
Message-ID: <bug-217931-137361-C5gHAgRHWx@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 #55 from Perry Yuan(AMD) (Perry.Yuan@amd.com) ---
(In reply to Sjoer van der Ploeg from comment #54)
> (In reply to Perry Yuan(AMD) from comment #53)
> > How about the output of "lscpu -ae"?
>
> Sorry for the late reply:
>
> CPU NODE SOCKET CORE L1d:L1i:L2:L3 ONLINE MAXMHZ MINMHZ MHZ
> 0 0 0 0 0:0:0:0 yes 4550.0000 550.0000 3569.5090
> 1 0 0 1 1:1:1:0 yes 4550.0000 550.0000 3552.6860
> 2 0 0 2 2:2:2:0 yes 4550.0000 550.0000 3559.3779
> 3 0 0 3 3:3:3:0 yes 4550.0000 550.0000 3854.7759
> 4 0 0 4 4:4:4:0 yes 4550.0000 550.0000 3590.6599
> 5 0 0 5 5:5:5:0 yes 4550.0000 550.0000 3552.8989
> 6 0 0 6 6:6:6:0 yes 4550.0000 550.0000 3840.7690
> 7 0 0 7 7:7:7:0 yes 4550.0000 550.0000 3584.2910
> 8 0 0 0 0:0:0:0 yes 4550.0000 550.0000 3546.3811
> 9 0 0 1 1:1:1:0 yes 4550.0000 550.0000 3551.5229
> 10 0 0 2 2:2:2:0 yes 4550.0000 550.0000 3591.2500
> 11 0 0 3 3:3:3:0 yes 4550.0000 550.0000 3594.0801
> 12 0 0 4 4:4:4:0 yes 4550.0000 550.0000 3552.0400
> 13 0 0 5 5:5:5:0 yes 4550.0000 550.0000 3572.1050
> 14 0 0 6 6:6:6:0 yes 4550.0000 550.0000 4124.7349
> 15 0 0 7 7:7:7:0 yes 4550.0000 550.0000 3583.7170
The max frequency value is correct to be 4.55GHZ on your system by the CPPC
capabilities reported by your firmware.
4.55GHZ is boost frequency which cannot maintain long time, it can try EPP mode
& performance profile, and run some lighter workload, the freq will be reaching
to max freq.
> 14 0 0 6 6:6:6:0 yes 4550.0000 550.0000 4124.7349
seeing from this, the freq is close to 4.5GHz, please try the EPP and
performance profile on your system.
then check the lscpu -ae output to confirm if it can reach 4.5GHz as well.
Perry.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-02-21 3:14 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 [this message]
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
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-C5gHAgRHWx@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).