From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 64251] Intel Pstate driver minimum percent does not change with turbo off
Date: Thu, 07 Nov 2013 05:28:49 +0000 [thread overview]
Message-ID: <bug-64251-12968-kaFKm6JJf7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-64251-12968@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=64251
--- Comment #4 from Doug Smythies <dsmythies@telus.net> ---
(In reply to Dirk Brandewie from comment #3)
> I was trying to provide some useful information by setting min_perf_pct to a
> value.
Which I totally agree with, and do find the information very useful.
I am just suggesting that it would be equally useful to provide that same
information for the other cases.
I see 4 scenarios, maybe there are more (using my computer as the example):
1.) BIOS allows Turbo mode and Turbo on enabled in driver:
min = 42 percent, which represents 1.6 GHz and is accurate
max = 100 percent, which represents 3.8 GHz and is accurate
2.) BIOS allows Turbo mode and Turbo is disabled in driver:
min = 42 percent, which doesn't represent anything.
max = 100 percent, which represents 3.4 GHz and is accurate.
3.) BIOS disabled Turbo mode and Turbo on enabled in driver:
min = 42 percent, which represents 1.6 GHz and is accurate.
max = 100 percent, which represents 3.8 GHz, but can not be achieved.
(a supporting graph will be attached in a minute)
4.) BIOS disabled Turbo mode and Turbo is disabled in driver:
This does not work at all on my computer. The CPU frequency just locks at
whatever it was when the driver Turbo disable transition command is issued.
(a supporting graph will be attached in a minute)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-11-07 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 21:42 [Bug 64251] New: Intel Pstate driver minimum percent does not change with turbo off bugzilla-daemon
2013-11-04 16:35 ` [Bug 64251] " bugzilla-daemon
2013-11-05 7:31 ` bugzilla-daemon
2013-11-05 7:56 ` bugzilla-daemon
2013-11-07 5:28 ` bugzilla-daemon [this message]
2013-11-07 5:36 ` bugzilla-daemon
2014-04-18 3:01 ` 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-64251-12968-kaFKm6JJf7@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;
as well as URLs for NNTP newsgroup(s).