From: Keir Fraser <keir@xensource.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Mark Langsdorf <mark.langsdorf@amd.com>,
xen-devel@lists.xensource.com
Subject: Re: [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
Date: Thu, 30 Aug 2007 11:12:28 +0100 [thread overview]
Message-ID: <C2FC569C.15063%keir@xensource.com> (raw)
In-Reply-To: <D470B4E54465E3469E2ABBC5AFAC390F013B21A8@pdsmsx412.ccr.corp.intel.com>
On 30/8/07 10:45, "Tian, Kevin" <kevin.tian@intel.com> wrote:
> Sure, some experiment can be done later to compare dom0 userspace
> and in-xen governor. Agree that in-kernel dom0 approach is not
> charming because anyway it needs help from either user-level or xen
> for global view.
>
> Actually finally we may take both. Xen takes simple heuristic policy
> with user-level governor to adjust with more complex and flexible
> policies based on domain behaviors. :-)
There is the problem, though, that most modern CPUs will need cpufreq info
to be parsed out of the ACPI DSDT. And Xen can't do that itself unaided.
Pushing down some form of cpufreq info table to Xen *is* an option though,
but we'd need more custom dom0 kernel code to do that. Or we'd need to do it
from a userspace program.
-- Keir
next prev parent reply other threads:[~2007-08-30 10:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 22:02 [PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes Mark Langsdorf
2007-08-30 6:41 ` Tian, Kevin
2007-08-30 9:30 ` Keir Fraser
2007-08-30 9:45 ` Tian, Kevin
2007-08-30 10:12 ` Keir Fraser [this message]
2007-08-31 1:20 ` Tian, Kevin
2007-08-31 10:04 ` Keir Fraser
2007-08-31 15:09 ` Tian, Kevin
2007-08-31 15:25 ` Keir Fraser
2007-09-01 0:23 ` Tian, Kevin
2007-09-01 11:07 ` Keir Fraser
2007-09-01 13:31 ` Tian, Kevin
2007-09-01 13:57 ` Keir Fraser
2007-09-01 14:14 ` Tian, Kevin
2007-09-01 14:22 ` Tian, Kevin
2007-09-01 14:12 ` Keir Fraser
2007-09-01 14:18 ` Tian, Kevin
2007-09-01 15:26 ` Keir Fraser
2007-09-01 15:45 ` Tian, Kevin
2007-09-01 16:41 ` Keir Fraser
2007-09-03 4:25 ` Tian, Kevin
2007-09-04 17:23 ` Rik van Riel
2007-08-30 14:45 ` Langsdorf, Mark
2007-08-30 15:04 ` Keir Fraser
2007-08-30 18:23 ` Rik van Riel
[not found] ` <1449F58C868D8D4E9C72945771150BDF0207700B@SAUSEXMB1.amd.com>
2007-08-30 20:56 ` Rik van Riel
2007-08-31 2:43 ` Tian, Kevin
2007-08-31 8:41 ` Jan Beulich
2007-08-30 14:59 ` Rik van Riel
2007-08-31 2:42 ` Tian, Kevin
2007-08-31 9:23 ` Keir Fraser
2007-08-31 13:50 ` Rik van Riel
2007-08-30 14:57 ` Langsdorf, Mark
2007-08-30 15:08 ` Keir Fraser
2007-10-01 8:30 ` xeb
2007-10-01 8:33 ` Keir Fraser
2007-10-02 12:56 ` xeb
2007-10-02 12:57 ` xeb
2007-10-02 13:00 ` xeb
2007-10-02 13:02 ` xeb
-- strict thread matches above, loose matches on Subject: below --
2007-10-02 13:05 xeb
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=C2FC569C.15063%keir@xensource.com \
--to=keir@xensource.com \
--cc=kevin.tian@intel.com \
--cc=mark.langsdorf@amd.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.