From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 206307] New: AMD Ryzen CPU frequency monitoring subsystem is insufficient
Date: Sat, 25 Jan 2020 23:39:53 +0000 [thread overview]
Message-ID: <bug-206307-137361@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206307
Bug ID: 206307
Summary: AMD Ryzen CPU frequency monitoring subsystem is
insufficient
Product: Power Management
Version: 2.5
Kernel Version: All
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: cpufreq
Assignee: linux-pm@vger.kernel.org
Reporter: aros@gmx.com
Regression: No
These are the features which are available under Windows but not possible under
Linux in any shape or form:
1) You cannot set the desired CPU frequency except for predefined values (in my
case 3600000 2800000 2200000Hz). In Windows you can set any desired frequency
between base and boost.
2) time_in_state is extremely coarse and shows neither boost, nor CPU sleep. At
least with Intel CPUs there's an additional CPU frequency MAX + 100KHz which
indicates boost. There's no such thing for AMD Ryzen CPUs.
3) Reported frequencies values in /proc/cpuinfo and
/sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq are again limited to
the predefined values.
/cpu/cpufreq/policy*/scaling_cur_freq contains a lot more varied values but
again, CPU sleeping or boosting are not reported.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-01-25 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 23:39 bugzilla-daemon [this message]
2020-01-25 23:53 ` [Bug 206307] AMD Ryzen CPU frequency monitoring subsystem is insufficient bugzilla-daemon
2020-01-28 5:53 ` bugzilla-daemon
2022-04-11 7:23 ` 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-206307-137361@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).