public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Brown, Len" <len.brown@intel.com>
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: Wed, 29 Jul 2009 09:43:50 -0700	[thread overview]
Message-ID: <4A707C46.2060405@goop.org> (raw)
In-Reply-To: <E87738D94A6AD54789B5B8D1BAEB06CC5C744C68C2@azsmsx503.amr.corp.intel.com>

On 07/28/09 21:14, Brown, Len wrote:
> Does somebody expect all this dom0 stuff to really live
> in the upstream linux kernel source tree?
>   

The control domain (dom0) patches are held up by a very specific set of
concerns that I'm working on now.  I don't think there's any fundamental
reason it won't make it in at some point, and there's no reason not to
lay the groundwork in the meantime.

These acpi patches are very useful, but not essential functionality. 
I'd like to see them evolve along lines that are acceptable to everyone
before making a serious push upstream.

> s/extcntl/xen/ to make it clear why this code exists --
> or is there an expected "external control" other than Xen?
>   

I dislike making Xen-specific changes.  Ideally we can find a way to fit
these changes into some other abstraction which already exists, or if
added would be useful to more than one user.

    J

  parent reply	other threads:[~2009-07-29 16:43 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
2009-07-31  8:05       ` Yu, Ke
2009-07-29 16:43   ` Jeremy Fitzhardinge [this message]
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=4A707C46.2060405@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