From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215800] amd-pstate does not allow to set arbitrary maximum CPU frequency above 2200MHz for a desktop Zen 3 CPU
Date: Tue, 08 Aug 2023 17:58:46 +0000 [thread overview]
Message-ID: <bug-215800-137361-ILCxiNGCdP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215800-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215800
--- Comment #31 from Artem S. Tashkinov (aros@gmx.com) ---
Created attachment 304797
--> https://bugzilla.kernel.org/attachment.cgi?id=304797&action=edit
Power Options Processor Power Management in Windows.png
(In reply to Mario Limonciello (AMD) from comment #30)
> > It's a little bit confusing though, as in Windows I can perfectly set
> minimum
> > and maximum CPU frequencies and I totally expected this driver to actually
> > allow that.
>
> I suppose I'm confused as well. Windows should be using EPP as well, and
> various software constructs like the power slider will be changing that bias.
>
> Maybe you can better explain exactly what you do in Windows and exactly what
> is happening.
In Windows I'm free to set minimum and maximum CPU clock speeds to my liking.
Why is it necessary?
1) For instance you want to do benchmarking at certain clock speeds which are
not known to be hitting TDP/TTP/temperature limits, thus they show the true
potential of your CPU.
2) For instance you want to make you CPU run cooler with a very precise
control.
>
> > Lastly the documentation mentions:
> energy_performance_available_preferences,
> > the file that I don't have.
>
> Eh? Didn't your above comment show this:
>
> /sys/devices/system/cpu/cpufreq/policy0 $ grep -r .
> energy_performance_available_preferences:default performance
> balance_performance balance_power power
>
> > Lastly there's no boost configuration support which is available both for
> > acpi-cpufreq and Intel's native CPPC driver.
>
> Something seems quite wrong if you're not getting boost support.
> It registers for boost, see
> https://github.com/torvalds/linux/blob/v6.4/drivers/cpufreq/amd-pstate.
> c#L1121
Will recheck in 6.4.x soon.
>
> > It's worse than acpi-cpufreq from seemingly any PoV. Maybe there are some
> > advantages for APUs but on my desktop I only see major disadvantages
>
> I /suspect/ what you'll want to do is change the scaling_governor from
> 'powersave' to 'performance' for your desktop use case.
These two options are very coarse vs. being simply able to set maximum clock
speeds.
--
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:[~2023-08-08 18:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 1:16 [Bug 215800] New: amd-pstate does not allow to set arbitrary maximum CPU frequency above 2200MHz for a desktop Zen 3 CPU bugzilla-daemon
2022-04-05 1:31 ` [Bug 215800] " bugzilla-daemon
2022-04-11 7:22 ` bugzilla-daemon
2022-04-11 13:33 ` bugzilla-daemon
2022-04-11 16:28 ` bugzilla-daemon
2022-04-12 3:25 ` bugzilla-daemon
2022-04-12 4:15 ` bugzilla-daemon
2022-04-12 7:25 ` bugzilla-daemon
2022-04-12 7:26 ` bugzilla-daemon
2022-04-12 8:46 ` bugzilla-daemon
2022-04-12 8:50 ` bugzilla-daemon
2022-04-13 6:50 ` bugzilla-daemon
2022-04-13 7:06 ` bugzilla-daemon
2022-04-13 7:12 ` bugzilla-daemon
2022-04-13 9:41 ` bugzilla-daemon
2022-05-17 8:07 ` bugzilla-daemon
2022-05-17 8:25 ` bugzilla-daemon
2022-05-19 2:34 ` bugzilla-daemon
2022-05-19 2:41 ` bugzilla-daemon
2022-06-12 14:34 ` bugzilla-daemon
2022-06-12 14:54 ` bugzilla-daemon
2022-06-12 15:04 ` bugzilla-daemon
2022-06-13 11:16 ` bugzilla-daemon
2022-07-05 1:14 ` bugzilla-daemon
2022-07-06 22:10 ` bugzilla-daemon
2022-09-19 12:08 ` bugzilla-daemon
2022-10-12 2:36 ` bugzilla-daemon
2023-07-07 13:27 ` bugzilla-daemon
2023-07-07 13:30 ` bugzilla-daemon
2023-07-07 13:35 ` bugzilla-daemon
2023-07-07 14:51 ` bugzilla-daemon
2023-07-07 15:07 ` bugzilla-daemon
2023-07-07 15:23 ` bugzilla-daemon
2023-08-08 17:58 ` bugzilla-daemon [this message]
2023-09-15 10:22 ` bugzilla-daemon
2023-09-20 11:07 ` 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-215800-137361-ILCxiNGCdP@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).