From: bugzilla-daemon@bugzilla.kernel.org
To: linux-pm@kernel.org
Subject: [Bug 197009] /proc/cpuinfo does not update frequency
Date: Mon, 20 Nov 2017 22:22:16 +0000 [thread overview]
Message-ID: <bug-197009-137361-bxzIJsYKpH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197009-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197009
Rafael J. Wysocki (rjw@rjwysocki.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|DOCUMENTED |CODE_FIX
--- Comment #13 from Rafael J. Wysocki (rjw@rjwysocki.net) ---
Now, whatever is reported as "cpu MHz" in /proc/cpuinfo in 4.13 and later has a
little to do with the intel_pstate driver in any case. It always comes from
some code outside of this driver, this way or another.
That said, there is mainline commit 7d5905dc14a8 (x86 / CPU: Always show
current CPU frequency in /proc/cpuinfo) causing "cpu MHz" in /proc/cpuinfo to
report the current frequency again. It is going to be backported to 4.13.y and
4.14.y if all goes well.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-11-20 22:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 18:55 [Bug 197009] New: /proc/cpuinfo does not update frequency bugzilla-daemon
2017-09-20 19:03 ` [Bug 197009] " bugzilla-daemon
2017-09-20 19:14 ` bugzilla-daemon
2017-09-22 5:01 ` bugzilla-daemon
2017-10-11 5:51 ` bugzilla-daemon
2017-10-17 1:41 ` bugzilla-daemon
2017-10-24 5:12 ` bugzilla-daemon
2017-11-02 1:44 ` bugzilla-daemon
2017-11-05 22:28 ` bugzilla-daemon
2017-11-18 15:34 ` bugzilla-daemon
2017-11-20 5:28 ` bugzilla-daemon
2017-11-20 14:36 ` bugzilla-daemon
2017-11-20 19:12 ` bugzilla-daemon
2017-11-20 22:16 ` bugzilla-daemon
2017-11-20 22:22 ` bugzilla-daemon [this message]
2017-11-21 1: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-197009-137361-bxzIJsYKpH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-pm@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.