From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Stefano Stabellini" <stefano.stabellini@eu.citrix.com>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Fix ram_memory initialization under Xen
Date: Mon, 2 Sep 2013 18:27:59 +0300 [thread overview]
Message-ID: <20130902152759.GA4382@redhat.com> (raw)
In-Reply-To: <1378135002-10052-1-git-send-email-anthony.perard@citrix.com>
On Mon, Sep 02, 2013 at 04:16:40PM +0100, Anthony PERARD wrote:
> Hi all,
>
> The first patch fix the initialization of ram_memory in pc_init1() in pc_piix.c.
>
> The second call the initialization code of Xen while running with the Q35
> chipset even if Q35 still those not work with Xen. There need some work in the
> HVM Loader and in libxl at least.
>
> Thanks,
For the series,
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Anthony PERARD (2):
> pc: Initializing ram_memory under Xen.
> pc_q35: Initialize Xen.
>
> hw/i386/pc_piix.c | 2 +-
> hw/i386/pc_q35.c | 5 +++++
> include/hw/xen/xen.h | 4 +---
> xen-all.c | 7 ++++---
> 4 files changed, 11 insertions(+), 7 deletions(-)
>
> --
> Anthony PERARD
next prev parent reply other threads:[~2013-09-02 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-02 15:16 [Qemu-devel] [PATCH v2 0/2] Fix ram_memory initialization under Xen Anthony PERARD
2013-09-02 15:16 ` [Qemu-devel] [PATCH v2 1/2] pc: Initializing ram_memory " Anthony PERARD
2013-09-02 15:16 ` [Qemu-devel] [PATCH v2 2/2] pc_q35: Initialize Xen Anthony PERARD
2013-09-02 15:27 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-06 12:25 [Qemu-devel] [PATCH v2 0/2] Fix ram_memory initialization under Xen Fabio Fantoni
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=20130902152759.GA4382@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony.perard@citrix.com \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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;
as well as URLs for NNTP newsgroup(s).