From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
'Jeremy Fitzhardinge' <jeremy@goop.org>,
"Brown, Len" <len.brown@intel.com>,
Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"Cihula, Joseph" <joseph.cihula@intel.com>
Subject: Re: [Xen-devel] Re: Paravirtualizing bits of acpi access
Date: Mon, 23 Mar 2009 19:52:27 +0000 [thread overview]
Message-ID: <20090323195227.GB30693@srcf.ucam.org> (raw)
In-Reply-To: <200903231920.12991.rjw@sisk.pl>
On Mon, Mar 23, 2009 at 07:20:12PM +0100, Rafael J. Wysocki wrote:
> On Monday 23 March 2009, Tian, Kevin wrote:
> > And then Xen jumps in to finish remaining steps. From this angle,
> > Xen is not a completely new platform and, well, S3 is more like a
> > 'S1' type from dom0's p.o.v with a different trigger method. Then is
> > it overkilled to introduce a new set of ops with 99% content
> > duplicated?
>
> IMO, no, it isn't.
I'd disagree. Duplicating the code means remembering to apply bugfixes
to both parts.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-03-23 19:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 6:09 Paravirtualizing bits of acpi access Jeremy Fitzhardinge
2009-03-21 17:10 ` Rafael J. Wysocki
2009-03-22 4:26 ` Jeremy Fitzhardinge
2009-03-22 11:28 ` Rafael J. Wysocki
2009-03-22 13:14 ` Ingo Molnar
2009-03-22 13:17 ` Rafael J. Wysocki
2009-03-22 17:07 ` Jeremy Fitzhardinge
2009-03-22 18:00 ` Rafael J. Wysocki
2009-03-23 3:29 ` Tian, Kevin
2009-03-23 18:20 ` [Xen-devel] " Rafael J. Wysocki
2009-03-23 19:07 ` Jeremy Fitzhardinge
2009-03-23 20:27 ` Rafael J. Wysocki
2009-03-23 20:42 ` Jeremy Fitzhardinge
2009-03-24 5:14 ` Jeremy Fitzhardinge
2009-03-24 5:33 ` Tian, Kevin
2009-03-24 5:42 ` Jeremy Fitzhardinge
2009-03-24 5:45 ` Tian, Kevin
2009-03-24 7:05 ` Jeremy Fitzhardinge
2009-03-24 16:45 ` Bjorn Helgaas
2009-03-24 17:28 ` Jeremy Fitzhardinge
2009-03-24 17:51 ` [Xen-devel] " Cihula, Joseph
2009-03-27 21:57 ` Len Brown
2009-03-27 23:20 ` Jeremy Fitzhardinge
2009-03-28 1:01 ` Len Brown
2009-03-28 2:19 ` Tian, Kevin
2009-03-28 3:19 ` Jeremy Fitzhardinge
2009-03-28 13:56 ` Rafael J. Wysocki
2009-03-24 23:40 ` Tian, Kevin
2009-03-24 23:51 ` Tian, Kevin
2009-03-25 0:45 ` Jeremy Fitzhardinge
2009-03-23 19:52 ` Matthew Garrett [this message]
2009-03-23 20:22 ` [Xen-devel] " Rafael J. Wysocki
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=20090323195227.GB30693@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jeremy@goop.org \
--cc=joseph.cihula@intel.com \
--cc=kevin.tian@intel.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox