From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219332] /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy
Date: Mon, 30 Sep 2024 17:15:40 +0000 [thread overview]
Message-ID: <bug-219332-137361-yIwwmpe9Cj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219332-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219332
--- Comment #11 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> When `amd-pstate=active` whatever is written to
> `/sys/devices/system/cpu/cpufreq/policy0/scaling_governor` has zero effect on
> the CPU behavior/system thermals. That's what I was trying to say.
I wouldn't say zero effect - it definitely can matter. If you start out in
powersave at a more efficiency biased EPP value then switching to performance
is going to increase power consumption and heat etc.
> I wonder if amd-pstate could "simply" hide/disable (i.e. make read-only)
> scaling_available_governors AND scaling_governor.
Userspace can still change the cpufreq governor from performance to powersave
and vice versa. So it should not go away.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2024-09-30 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 13:13 [Bug 219332] New: /sys/devices/system/cpu/cpufreq/policy0/energy_performance_preference: Device or resource busy bugzilla-daemon
2024-09-29 13:14 ` [Bug 219332] " bugzilla-daemon
2024-09-29 13:24 ` bugzilla-daemon
2024-09-29 13:50 ` bugzilla-daemon
2024-09-29 19:18 ` bugzilla-daemon
2024-09-29 19:29 ` bugzilla-daemon
2024-09-30 5:53 ` bugzilla-daemon
2024-09-30 13:28 ` bugzilla-daemon
2024-09-30 15:50 ` bugzilla-daemon
2024-09-30 16:11 ` bugzilla-daemon
2024-09-30 17:04 ` bugzilla-daemon
2024-09-30 17:15 ` bugzilla-daemon [this message]
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-219332-137361-yIwwmpe9Cj@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).