From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 86461] intel_pstate does not obey min/max frequencies set by user
Date: Fri, 17 Oct 2014 17:02:43 +0000 [thread overview]
Message-ID: <bug-86461-12968-JnKKwq7sTv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86461-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86461
--- Comment #4 from Dirk Brandewie <dirk.brandewie@gmail.com> ---
I looks like everything is working correctly. You have to remember that the
frequencies returned by turbostat and intel_pstate are measured effective
frequency over the time of the sample. Previously with acpi_cpufreq the value
returned through /proc/cpuinfo and the cupfreq sysfs interface was the
requested
frequency and not the actual frequency.
If you want to see that the floor for P states has actually changed you can see
the requested P state with:
rdmsr -a -f15:8 0x199
The actual frequency that all cores on the processor run at is selected by the
processor based on the requests for all cores.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-10-17 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 9:21 [Bug 86461] New: intel_pstate does not obey min/max frequencies set by user bugzilla-daemon
2014-10-17 15:17 ` [Bug 86461] " bugzilla-daemon
2014-10-17 16:43 ` bugzilla-daemon
2014-10-17 16:51 ` bugzilla-daemon
2014-10-17 17:02 ` bugzilla-daemon [this message]
2014-10-17 17:28 ` bugzilla-daemon
2014-10-23 13:57 ` bugzilla-daemon
2014-10-28 5:17 ` 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-86461-12968-JnKKwq7sTv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=cpufreq@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.