From: Avi Kivity <avi@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: qemu-trivial@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
Xen Devel <xen-devel@lists.xensource.com>,
QEMU-devel <qemu-devel@nongnu.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH] exec, Fix guest memory access.
Date: Mon, 19 Mar 2012 19:13:48 +0200 [thread overview]
Message-ID: <4F67694C.6000108@redhat.com> (raw)
In-Reply-To: <1332172474-17567-1-git-send-email-anthony.perard@citrix.com>
On 03/19/2012 05:54 PM, Anthony PERARD wrote:
> In cpu_physical_memory_rw, a change has been introduced and qemu_get_ram_ptr is
> no longuer called with the ram addr we want to access, but only with the
> section address. This patch fixes this. (All other call to qemu_get_ram_ptr are
> already called with the right address.)
>
> This patch fixes Xen guest.
>
Thanks, applied to memory/urgent, will push shortly.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-03-19 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 15:54 [Qemu-devel] [PATCH] exec, Fix guest memory access Anthony PERARD
2012-03-19 17:13 ` Avi Kivity [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=4F67694C.6000108@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--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;
as well as URLs for NNTP newsgroup(s).