linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219110] amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume
Date: Tue, 30 Jul 2024 18:09:20 +0000	[thread overview]
Message-ID: <bug-219110-137361-6sEYCVgqop@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219110-137361@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219110

--- Comment #2 from Artem S. Tashkinov (aros@gmx.com) ---
(In reply to xiaojian.du from comment #1)
> So you do one suspend cycle on your device?

I have to set/restore energy_performance_preference on every resume.

> I think CPU power status is reset after one suspend cycle.
> Yes, it should be a function to restore CPU power register status and
> governor status after s3/s4/s2idle.
> For you case, i think add one more shell script will fix this problem, you
> know, you are setting cpu enegy policy during booting, then your can add one
> same action during suspend, any chance for this?

I can certainly do that, but with acpi-cpufreq you didn't have to do that :-(

You set performance/powersave/ondemand and it perfectly survives
suspend/resume.

I wonder why amd-pstate cannot. A kernel module can keep this state as a simple
variable and restore the energy preference on resume.

And secondly it's quite misleading that it reports a wrong value after
resuming.

-- 
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-07-30 18:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 17:40 [Bug 219110] New: amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume bugzilla-daemon
2024-07-30 17:56 ` [Bug 219110] " bugzilla-daemon
2024-07-30 18:09 ` bugzilla-daemon [this message]
2024-07-30 18:29 ` bugzilla-daemon
2024-07-30 18:31 ` bugzilla-daemon
2024-08-23 18:07 ` bugzilla-daemon
2024-08-23 19:54 ` bugzilla-daemon
2024-08-23 19:56 ` bugzilla-daemon
2024-08-26 17:23 ` bugzilla-daemon
2024-08-26 18:14 ` bugzilla-daemon
2024-08-26 18:19 ` bugzilla-daemon
2024-08-26 18:22 ` bugzilla-daemon
2024-08-26 18:27 ` 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-219110-137361-6sEYCVgqop@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).