From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all governors. i5-3201M
Date: Thu, 03 Apr 2014 01:12:22 +0000 [thread overview]
Message-ID: <bug-73421-12968-pKJ1yeA7hJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73421-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=73421
Dirk Brandewie <dirk.brandewie@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dirk.brandewie@gmail.com
--- Comment #1 from Dirk Brandewie <dirk.brandewie@gmail.com> ---
2900 MHz max turbo 4 active cores
intel_pstate has an internal governor. If you are using intel_pstate you use
its internal governor which has two modes performance which is equivalent to
the performance governor and powersave roughly equal to ondemand but is better
on power.
When a scaling driver with an internal governor is being used powersave and
performance are the only options
You have a 2.5Ghz processor and are getting 2.9Ghz in both cases which *is* in
the turbo range.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-03 1:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 0:51 [Bug 73421] New: intel/p_state Does not increase into Turbo Boost states and does not display al governors. i5-3201M bugzilla-daemon
2014-04-03 0:53 ` [Bug 73421] intel/p_state Does not increase into Turbo Boost states and does not display all " bugzilla-daemon
2014-04-03 1:12 ` bugzilla-daemon [this message]
2014-04-03 1:33 ` bugzilla-daemon
2014-04-03 1:52 ` bugzilla-daemon
2014-04-03 15:14 ` bugzilla-daemon
2014-04-03 15:37 ` bugzilla-daemon
2014-04-15 6:10 ` bugzilla-daemon
2014-09-22 13:38 ` 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-73421-12968-pKJ1yeA7hJ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox