From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Yu, Ke" <ke.yu@intel.com>
Cc: "Brown, Len" <len.brown@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 10:23:04 -0700 [thread overview]
Message-ID: <4A71D6F8.9040007@goop.org> (raw)
In-Reply-To: <4D05DB80B95B23498C72C700BD6C2E0B315D6A67@pdsmsx502.ccr.corp.intel.com>
On 07/30/09 02:18, Yu, Ke wrote:
> Can you explain what the deeper design problem is?
>
I don't know. It may be that ACPI and Xen-style virtualization
fundimentally have designs which can't easily co-exist, and it is
unavoidable. I'm simply saying there appears to be a problem because
the need to put a Xen-specific hook in a piece of generic code is
generally a symptom of a design problem.
J
next prev parent reply other threads:[~2009-07-30 17:23 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 [this message]
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
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=4A71D6F8.9040007@goop.org \
--to=jeremy@goop.org \
--cc=ke.yu@intel.com \
--cc=kevin.tian@intel.com \
--cc=len.brown@intel.com \
--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