From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>
Cc: gleb@redhat.com, pbonzini@redhat.com, kvm@vger.kernel.org,
agraf@suse.de, borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
christoffer.dall@linaro.org
Subject: Re: [PATCH 1/2] KVM: Introduce kvm_arch_memslots_updated()
Date: Thu, 04 Jul 2013 18:28:03 +0800 [thread overview]
Message-ID: <51D54E33.60708@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130704134029.4db2736a.yoshikawa_takuya_b1@lab.ntt.co.jp>
On 07/04/2013 12:40 PM, Takuya Yoshikawa wrote:
> This is called right after the memslots is updated, i.e. when the result
> of update_memslots() gets installed in install_new_memslots(). Since
> the memslots needs to be updated twice when we delete or move a memslot,
> kvm_arch_commit_memory_region() does not correspond to this exactly.
>
> In the following patch, x86 will use this new API to check if the mmio
> generation has reached its maximum value, in which case mmio sptes need
> to be flushed out.
Reviewed-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
next prev parent reply other threads:[~2013-07-04 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 4:39 [PATCH 0/2] KVM: Introduce kvm_arch_memslots_updated() and use it for x86's mmio optimization Takuya Yoshikawa
2013-07-04 4:40 ` [PATCH 1/2] KVM: Introduce kvm_arch_memslots_updated() Takuya Yoshikawa
2013-07-04 9:53 ` Gleb Natapov
2013-07-04 10:24 ` Alexander Graf
2013-07-08 10:49 ` Cornelia Huck
2013-07-04 10:28 ` Xiao Guangrong [this message]
2013-07-04 4:41 ` [PATCH v2 2/2] KVM: x86: Avoid zapping mmio sptes twice for generation wraparound Takuya Yoshikawa
2013-07-04 10:27 ` Xiao Guangrong
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=51D54E33.60708@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=christoffer.dall@linaro.org \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.