From: Avi Kivity <avi@redhat.com>
To: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/3] KVM: x86: fix broken read emulation spans a page boundary
Date: Thu, 14 Jul 2011 11:59:09 +0300 [thread overview]
Message-ID: <4E1EAFDD.1080406@redhat.com> (raw)
In-Reply-To: <4E1D3BAC.5090109@cn.fujitsu.com>
On 07/13/2011 09:31 AM, Xiao Guangrong wrote:
> If the range spans a page boundary, the mmio access can be broke, fix it as
> write emulation.
>
> And we already get the guest physical address, so use it to read guest data
> directly to avoid walking guest page table again
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-07-14 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 6:31 [PATCH 1/3] KVM: x86: fix broken read emulation spans a page boundary Xiao Guangrong
2011-07-13 6:31 ` [PATCH 2/3] KVM: x86: abstract the operation for read/write emulation Xiao Guangrong
2011-07-13 6:32 ` [PATCH 3/3] KVM: x86: cleanup the code of " Xiao Guangrong
2011-07-14 8:59 ` 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=4E1EAFDD.1080406@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@cn.fujitsu.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