From: Carsten Schiers <carsten@schiers.de>
To: Akio Takebe <takebe_akio@jp.fujitsu.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Tian, Kevin" <kevin.tian@intel.com>, Yu Ke <ke.yu@intel.com>
Subject: AW: How to use Px/Cx for power saving?
Date: Wed, 14 Jan 2009 16:07:19 +0100 [thread overview]
Message-ID: <7198961.251231945639314.JavaMail.root@uhura> (raw)
Hi,
cpufreq support can be either handled by xen or dom0-kernel. You have to specify cpufreq=xen or
cpufreq=dom0-kernel as parameters when starting the hypervisor.
Kevin Tian wrote yesterday:
> It's intentional since Xen itself supports cpufreq now. To avoid
> dependency on dom0's CONFIG_CPU_FREQ and also intrusive
> checks on whether external control is enabled in every linux
> cpufreq drivers, CPU_FREQ in dom0 is silented by default now.
> It's not a neat approach, but makes sense since xen controlled
> cpufreq is sure a better model. You can enable CPU_FREQ in
> dom0 manually though, by removing below dependency.
> (drivers/cpufreq/Kconfig)
> config CPU_FREQ
> bool "CPU Frequency scaling"
> ----> depends on !PROCESSOR_EXTERNAL_CONTROL
> However once that dependency is removed, there's no automatic
> check to avoid confliction when dom0 and xen both want to
> control freq change, and then you should keep an eye yourself.
For AMD, pre-Family 10 CPUs you are supposed to use dom0-kernel, where you can encounter problems
with TSC drifts. For other CPUs, I have no knowledge. Family 10 CPUs will have P-State invariant
TSCs and will be should be supported by xen cpufreq. C-State handling is switched on by cpuidle as
parameter.
Note: xenpm is used to handle xen cpufreq support. In dom0-kernel, you use the dom0 tools.
BR,
Carsten.
----- Originalnachricht -----
Von: Akio Takebe <takebe_akio@jp.fujitsu.com>
Gesendet: Mit, 14.1.2009 15:32
An: xen-devel <xen-devel@lists.xensource.com> ; "Tian, Kevin" <kevin.tian@intel.com> ; Yu Ke <ke.yu@intel.com>
Betreff: [Xen-devel] How to use Px/Cx for power saving?
Hi,
If we want to use ACPI power saving(Cx/Px), how do we use them?
I tried to turn CONFIG_xxxx of cpufreq on with linux-2.6.18-xen.hg,
but I couldn't turn them on.
Also xenpm said the following error.
# xenpm get-cpuidle-states
Xen cpuidle is not enabled!
# xenpm get-cpufreq-states
Xen cpufreq is not enabled!
What should I do?
If there are some good documents, please tell me.
Best Regards,
Akio Takebe
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2009-01-14 15:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 15:07 Carsten Schiers [this message]
2009-01-15 0:01 ` AW: How to use Px/Cx for power saving? Akio Takebe
2009-01-15 1:30 ` Tian, Kevin
2009-01-15 2:04 ` Akio Takebe
2009-01-15 2:40 ` Tian, Kevin
-- strict thread matches above, loose matches on Subject: below --
2009-01-15 10:53 AW: " Carsten Schiers
2009-01-15 12:02 ` Tian, Kevin
2009-01-15 17:20 ` Langsdorf, Mark
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=7198961.251231945639314.JavaMail.root@uhura \
--to=carsten@schiers.de \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=takebe_akio@jp.fujitsu.com \
--cc=xen-devel@lists.xensource.com \
/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.