From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 10194] New: cpufreq P-state tables can change during runtime, handle it
Date: Fri, 7 Mar 2008 09:35:30 -0800 (PST) [thread overview]
Message-ID: <bug-10194-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=10194
Summary: cpufreq P-state tables can change during runtime, handle
it
Product: Power Management
Version: 2.5
KernelVersion: 2.6.25-rc4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: Matt_Domsch@dell.com
CC: wwlinuxengineering@dell.com
ACPI now allows a BIOS to change the P-state tables during runtime. This can
happen as the result of a power cord being plugged in or out, of a thermal
alarm of some sort which BIOS catches, of a "green" power savings mode set in
BIOS, or possibly other situations.
When BIOS wants to change the tables, it issues an SCI.
acpi-cpufreq does not presently have a way to catch that SCI. It does not
re-read the P-state tables. And it does not inform userspace that the values
have changed.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-03-07 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 17:35 bugme-daemon [this message]
2008-04-04 12:37 ` [Bug 10194] cpufreq P-state tables can change during runtime, handle it bugme-daemon
2008-04-09 23:20 ` bugme-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-10194-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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