From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCH] get rid of mmu_only parameter in emulator_write_emulated()
Date: Tue, 13 Apr 2010 12:21:37 +0300 [thread overview]
Message-ID: <4BC437A1.2020208@redhat.com> (raw)
In-Reply-To: <20100413074059.GH23554@redhat.com>
On 04/13/2010 10:40 AM, Gleb Natapov wrote:
> The code path executed in case of cmpxchg crossing page boundary is not
> touched by the patch as far as I can see. In this case
> emulator_write_emulated() is executed with mmu_only false and
> kvm_mmu_pte_write() is called from emulator_write_phys().
>
>
Yes. Patch is correct.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-04-13 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 7:21 [PATCH] get rid of mmu_only parameter in emulator_write_emulated() Gleb Natapov
2010-04-13 7:24 ` Avi Kivity
2010-04-13 7:26 ` Gleb Natapov
2010-04-13 7:35 ` Avi Kivity
2010-04-13 7:40 ` Gleb Natapov
2010-04-13 9:21 ` Avi Kivity [this message]
2010-04-14 17:20 ` Marcelo Tosatti
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=4BC437A1.2020208@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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