From: Wei Liu <wei.liu2@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Wei Liu <wei.liu2@citrix.com>,
qemu-devel@nongnu.org, Xen-devel <xen-devel@lists.xenproject.org>,
Igor Mammedov <imammedo@redhat.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Sander Eikelenboom <linux@eikelenboom.it>
Subject: Re: [Qemu-devel] [PATCH v2] PCMachineState: introduce acpi_build_enabled field
Date: Wed, 2 Nov 2016 15:49:36 +0000 [thread overview]
Message-ID: <20161102154936.GO30231@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1611011530070.19454@sstabellini-ThinkPad-X260>
On Tue, Nov 01, 2016 at 03:30:59PM -0700, Stefano Stabellini wrote:
> On Tue, 1 Nov 2016, Eduardo Habkost wrote:
> > On Tue, Nov 01, 2016 at 05:44:16PM +0000, Wei Liu wrote:
> > > Introduce this field to control whether ACPI build is enabled by a
> > > particular machine or accelerator.
> > >
> > > It defaults to true if the machine itself supports ACPI build. Xen
> > > accelerator will disable it because Xen is in charge of building ACPI
> > > tables for the guest.
> > >
> > > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> >
> > Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
>
> Thank you Eduardo. I can queue it up unless you have other stuff in
> progress.
I would like to backport this to qemu-xen tree, so it would be great if
this patch can be merged in the next two weeks. Thanks!
Wei.
next prev parent reply other threads:[~2016-11-02 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 17:44 [Qemu-devel] [PATCH v2] PCMachineState: introduce acpi_build_enabled field Wei Liu
2016-11-01 18:35 ` Sander Eikelenboom
2016-11-01 19:29 ` Stefano Stabellini
2016-11-01 22:05 ` Eduardo Habkost
2016-11-01 22:30 ` Stefano Stabellini
2016-11-02 15:49 ` Wei Liu [this message]
2016-11-03 13:14 ` Eduardo Habkost
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=20161102154936.GO30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=linux@eikelenboom.it \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).