public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
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 13:28:08 +0000	[thread overview]
Message-ID: <bug-219332-137361-lJ0ymHZKqh@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 #7 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to Dhananjay Ugwekar (AMD) from comment #6)
> 
> I see from the attachment that you are using performance governor, so you
> are limited to only performance EPP hint, trying to write other EPP hints
> (power/balance_power/balance_performance) will show the above error. 
> 
> You'll need to change to powersave governor to use these hints. Please let
> me know if this fixes your issue.

That's indeed the case and changing the CPU frequency governor to "powersave"
has fixed the issue but I wonder if you could log an error message in dmesg if
the governor is incompatible with what the user has requested.

It still makes my head hurt trying to understand the interaction between
classic CPU governors and energy_performance_preference modes.

From the testing I've done it looks like classic CPU governors are 100%
useless/have zero effect in the presence of amd-pstate in which case I don't
understand why they are exposed/exist in the first place. Is it possible to
hide them? Make them read only? Just to avoid further useless bug reports.

-- 
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-09-30 13:28 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 [this message]
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

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-lJ0ymHZKqh@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