From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 75121] New: Intel Pstate driver - powersave mode - CPU frequency too low
Date: Tue, 29 Apr 2014 23:47:53 +0000 [thread overview]
Message-ID: <bug-75121-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=75121
Bug ID: 75121
Summary: Intel Pstate driver - powersave mode - CPU frequency
too low
Product: Power Management
Version: 2.5
Kernel Version: 3.15rc3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
Assignee: cpufreq@vger.kernel.org
Reporter: dsmythies@telus.net
Regression: No
Until recently, the difference between the intel_pstate driver in performance
mode verses powersave mode was minimal to imperceptible. Now, the frequency
response (meaning the rate of load / noload on a CPU) is drastically different
than it used to be and often not even as good as the acpi-cpufreq driver in
ondemand mode.
This is a negative side effect from Commit fcb6a15c2e7e - intel_pstate: Take
core C0 time into account for core busy calculation.
I can revert to the same performance as previously for the intel_pstate driver
in powersave mode by changing one line in the code (kernel = 3.15rc3-doug on
the graphs). From this:
sample->core_pct_busy = mul_fp(core_pct, c0_pct);
to this:
sample->core_pct_busy = core_pct;
basically, reverting the commit.
There has been other bug reports and threads:
References:
https://bugzilla.kernel.org/show_bug.cgi?id=70941
https://bugzilla.kernel.org/show_bug.cgi?id=66581
https://lkml.org/lkml/2014/2/19/626
In a moment, I will add 3 attachment graphs that detail the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-04-29 23:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 23:47 bugzilla-daemon [this message]
2014-04-29 23:54 ` [Bug 75121] Intel Pstate driver - powersave mode - CPU frequency too low bugzilla-daemon
2014-04-29 23:56 ` bugzilla-daemon
2014-04-29 23:59 ` bugzilla-daemon
2014-04-30 0:08 ` bugzilla-daemon
2014-05-02 14:25 ` bugzilla-daemon
2014-05-02 23:42 ` bugzilla-daemon
2014-05-02 23:58 ` bugzilla-daemon
2014-05-03 0:03 ` bugzilla-daemon
2014-05-03 0:05 ` bugzilla-daemon
2014-05-03 0:11 ` bugzilla-daemon
2014-05-03 0:19 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 0:47 ` bugzilla-daemon
2014-05-03 3:49 ` bugzilla-daemon
2014-05-03 3:58 ` bugzilla-daemon
2014-05-03 4:59 ` bugzilla-daemon
2014-05-03 5:00 ` bugzilla-daemon
2014-05-04 19:18 ` bugzilla-daemon
2014-05-05 18:05 ` bugzilla-daemon
2014-05-05 18:52 ` bugzilla-daemon
2014-05-08 22:19 ` bugzilla-daemon
2014-05-08 22:21 ` bugzilla-daemon
2014-05-08 22:26 ` bugzilla-daemon
2014-05-28 21:22 ` bugzilla-daemon
2014-06-03 20:45 ` bugzilla-daemon
2015-07-21 19:28 ` 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-75121-12968@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.