From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Len Brown <lenb@kernel.org>
Cc: "Yu, Ke" <ke.yu@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Tian, Kevin" <kevin.tian@intel.com>
Subject: Re: [Xen-devel] [PATCH][pvops_dom0][2/4] Introduce the external control operation interface for domain0 ACPI parser
Date: Thu, 30 Jul 2009 15:04:52 -0700 [thread overview]
Message-ID: <4A721904.7040406@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0907301204260.17818@localhost.localdomain>
On 07/30/09 09:29, Len Brown wrote:
> Unclear that the power management partitioning between xen hypervisor
> and dom0 is fully baked.
>
> Uncear (to me) what xen is doing internally with these power management
> objects, and how that differs from what Linux would do.
>
Yes. The key thing is that Xen is the only entity which really knows
about physical CPUs and how they're being used, and so is the only thing
which can correctly apply the chosen policy. If any particular guest
domain did it, it would only take into account that particular domain's
CPU use, and ignore everyone else (or have the extra complexity of
extracting system-wide usage from Xen then applying that to its own policy).
If I understand correctly, the code currently relies on Linux running
the _PSD method with its AML interpreter, and then feeding the results
to Xen as it doesn't have an AML interpreter. And putting AML into Xen
would be an all-or-nothing proposition, because the entity which runs
AML maintains a lot of state which can't be separated between Xen and
Linux, and can't be shared.
J
next prev parent reply other threads:[~2009-07-30 22:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 2:55 FW: [Xen-devel] [PATCH][pvops_dom0][2/4] Introduce the external control operation interface for domain0 ACPI parser Yu, Ke
2009-07-29 4:14 ` Brown, Len
2009-07-29 6:20 ` Yu, Ke
2009-07-29 16:50 ` Jeremy Fitzhardinge
2009-07-30 9:18 ` Yu, Ke
2009-07-30 16:00 ` Len Brown
2009-07-30 20:36 ` Jeremy Fitzhardinge
2009-07-30 17:23 ` Jeremy Fitzhardinge
2009-07-30 15:37 ` Len Brown
2009-07-30 20:52 ` Jeremy Fitzhardinge
2009-07-29 14:47 ` Yu, Ke
2009-07-30 16:29 ` Len Brown
2009-07-30 22:04 ` Jeremy Fitzhardinge [this message]
2009-07-31 8:05 ` Yu, Ke
2009-07-29 16:43 ` Jeremy Fitzhardinge
2009-07-30 8:59 ` Yu, Ke
2009-07-30 15:03 ` Brown, Len
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=4A721904.7040406@goop.org \
--to=jeremy@goop.org \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@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