From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 215729] amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU
Date: Thu, 28 Apr 2022 08:49:40 +0000 [thread overview]
Message-ID: <bug-215729-137361-dkqvhBHJQe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215729-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215729
Joe (sujinzhou2008@126.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sujinzhou2008@126.com
--- Comment #8 from Joe (sujinzhou2008@126.com) ---
Hello,
I reproduce this issue on my local.
Your device (CPU family: 25, Model: 33) should be shared memory solution with
AMD P-state driver. Updating CPPC request with shared memory will need more
energy than writing MSR register directly. We are checking this issue now.
For ondemand governor, could you please try to reduce the sampling_rate and
then check to energy consumption again? Thanks a lot!
Here is the command
cd /sys/devices/system/cpu/cpufreq/ondemand
echo 50000 > sampling_rate
Thanks
Joe
--
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:[~2022-04-28 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 23:58 [Bug 215729] New: amd-pstate driver has a much higher idle power consumption for a desktop Zen 3 CPU bugzilla-daemon
2022-03-22 23:59 ` [Bug 215729] " bugzilla-daemon
2022-03-23 0:01 ` bugzilla-daemon
2022-03-23 2:09 ` bugzilla-daemon
2022-03-23 15:35 ` bugzilla-daemon
2022-03-23 15:41 ` bugzilla-daemon
2022-03-23 15:58 ` bugzilla-daemon
2022-03-23 16:04 ` bugzilla-daemon
2022-04-28 8:49 ` bugzilla-daemon [this message]
2022-05-09 8:38 ` bugzilla-daemon
2023-07-07 13:24 ` bugzilla-daemon
2023-09-15 10:24 ` 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-215729-137361-dkqvhBHJQe@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).