From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 54221] New: ondemand cpufeq governor do not notice Node Manager power limit change
Date: Fri, 22 Feb 2013 12:53:41 +0000 (UTC) [thread overview]
Message-ID: <bug-54221-12968@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=54221
Summary: ondemand cpufeq governor do not notice Node Manager
power limit change
Product: Power Management
Version: 2.5
Kernel Version: 3.0.13
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@vger.kernel.org
ReportedBy: przemyslaw.witka@intel.com
Regression: No
When ondemand governor is active, CPU is not run at high cpu frequency.
Steps to reproduce:
1. Activate ondemand governor
2. Run 100% on CPU (check that CPU runs at the highest frequency)
3. Set Node Manager power limit (policy in CPU domain) to some quite low value
(cpu should run at low freq)
4. Remove Node Manager power limit
Expected result:
CPU should run again at the highest frequency
Actual result:
CPU runs at low frequency
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2013-02-22 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:53 bugzilla-daemon [this message]
2013-02-22 13:07 ` [Bug 54221] ondemand cpufeq governor do not notice Node Manager power limit change bugzilla-daemon
2013-02-28 1:39 ` bugzilla-daemon
2013-02-28 1:39 ` bugzilla-daemon
2013-02-28 1:39 ` bugzilla-daemon
2013-03-07 8:36 ` bugzilla-daemon
2013-07-15 5:18 ` 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-54221-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 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).