All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219110] New: amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume
Date: Tue, 30 Jul 2024 17:40:34 +0000	[thread overview]
Message-ID: <bug-219110-137361@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 219110
           Summary: amd-pstate's balance_performance
                    energy_performance_preference doesn't survive suspend
                    resume
           Product: Power Management
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: cpufreq
          Assignee: linux-pm@vger.kernel.org
          Reporter: aros@gmx.com
        Regression: No

On boot I'm setting
/sys/devices/system/cpu/cpufreq/*/energy_performance_preference to
`balance_performance` however after a suspend resume cycle it gets reset to
`performance` despite energy_performance_preference reporting that it's set to
`balance_performance` which is basically a lie.

How do I know it?

Start watching a 1440p/4K VP9/AV1 video with video acceleration on on YouTube.

With default performance I'm looking at more than 14W CPU package consumption
on average.

With balance_performance it goes down to roughly 8W.

Upon resume with reportedly balance_performance it's back to > 14W.

Please fix.

That's with kernel 6.9.12. If this has been fixed in 6.10, please let me know.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2024-07-30 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 17:40 bugzilla-daemon [this message]
2024-07-30 17:56 ` [Bug 219110] amd-pstate's balance_performance energy_performance_preference doesn't survive suspend resume bugzilla-daemon
2024-07-30 18:09 ` bugzilla-daemon
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.