From: Anthony Liguori <anthony@codemonkey.ws>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Anthony.Perard@citrix.com, xen-devel@lists.xensource.com,
Xudong Hao <xudong.hao@intel.com>,
qemu-devel@nongnu.org,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PULL] Xen tree 2012-10-03
Date: Thu, 04 Oct 2012 21:11:21 -0500 [thread overview]
Message-ID: <87391thdme.fsf@codemonkey.ws> (raw)
In-Reply-To: <alpine.DEB.2.02.1210031452190.29232@kaball.uk.xensource.com>
Stefano Stabellini <stefano.stabellini@eu.citrix.com> writes:
> Hi Anthony,
> please pull from the following tree based on
> e744c06fca438dc08271e626034e632a270c91c8:
>
> git://xenbits.xen.org/people/sstabellini/qemu-dm.git xen-2012-10-03
Pulled. Thanks.
Regards,
Anthony Liguori
>
>
> Anthony PERARD (6):
> xen: Fix, no unplug of pt device by platform device.
> QMP, Introduce xen-set-global-dirty-log command.
> xen: Introduce xen_modified_memory.
> exec: Introduce helper to set dirty flags.
> exec, memory: Call to xen_modified_memory.
> xen: Set the vram dirty when an error occur.
>
> Xudong Hao (1):
> qemu/xen: Add 64 bits big bar support on qemu
>
>
> exec-obsolete.h | 2 +
> exec.c | 53 ++++++++++++++++-------------------------------
> hw/xen.h | 1 +
> hw/xen_platform.c | 8 +++++-
> hw/xen_pt.c | 7 ++++-
> hw/xen_pt_config_init.c | 39 +++++++++++++++++++++++-----------
> qapi-schema.json | 13 +++++++++++
> qmp-commands.hx | 24 +++++++++++++++++++++
> xen-all.c | 39 +++++++++++++++++++++++++++++++++-
> xen-stub.c | 9 ++++++++
> 10 files changed, 142 insertions(+), 53 deletions(-)
>
> Cheers,
>
> Stefano
prev parent reply other threads:[~2012-10-05 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 14:00 [Qemu-devel] [PULL] Xen tree 2012-10-03 Stefano Stabellini
2012-10-05 2:11 ` Anthony Liguori [this message]
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=87391thdme.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Anthony.Perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xudong.hao@intel.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).