From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 211305] schedutil selects low P-States on AMD EPYC with frequency invariance
Date: Fri, 12 Feb 2021 22:00:00 +0000 [thread overview]
Message-ID: <bug-211305-137361-NeU87X4D09@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211305-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211305
--- Comment #11 from Matt McDonald (gardotd426@gmail.com) ---
Oh, I can also add that the previous patch that was turned down and replaced
with this patchset doesn't cause this issue, cpu frequency and frequency
reporting work as expected with that patch, and I'm able to boost up to 4750MHz
under full load and 5GHz under single-core load.
--
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:[~2021-02-12 22:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 0:55 [Bug 211305] New: schedutil selects low P-States on AMD EPYC with frequency invariance bugzilla-daemon
2021-01-21 0:57 ` [Bug 211305] " bugzilla-daemon
2021-01-21 0:59 ` bugzilla-daemon
2021-01-21 1:00 ` bugzilla-daemon
2021-01-21 1:03 ` bugzilla-daemon
2021-01-27 21:18 ` bugzilla-daemon
2021-02-12 17:28 ` bugzilla-daemon
2021-02-12 18:19 ` Rafael J. Wysocki
2021-02-12 18:19 ` bugzilla-daemon
2021-02-12 19:12 ` bugzilla-daemon
2021-02-12 20:39 ` bugzilla-daemon
2021-02-12 21:15 ` bugzilla-daemon
2021-02-12 22:00 ` bugzilla-daemon [this message]
2021-02-15 13:52 ` bugzilla-daemon
2021-02-15 13:54 ` bugzilla-daemon
2021-02-15 13:55 ` bugzilla-daemon
2021-02-15 14:04 ` bugzilla-daemon
2021-02-15 14:43 ` bugzilla-daemon
2021-02-15 14:47 ` bugzilla-daemon
2021-02-15 15:09 ` bugzilla-daemon
2021-02-15 15:30 ` 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-211305-137361-NeU87X4D09@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).