From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: gleb@redhat.com
Cc: avi.kivity@gmail.com, mtosatti@redhat.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Subject: [PATCH 3/7] KVM: MMU: document write_flooding_count
Date: Wed, 19 Jun 2013 17:09:21 +0800 [thread overview]
Message-ID: <1371632965-20077-4-git-send-email-xiaoguangrong@linux.vnet.ibm.com> (raw)
In-Reply-To: <1371632965-20077-1-git-send-email-xiaoguangrong@linux.vnet.ibm.com>
Document write_flooding_count to Documentation/virtual/kvm/mmu.txt
Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
---
Documentation/virtual/kvm/mmu.txt | 8 ++++++++
arch/x86/include/asm/kvm_host.h | 5 +++++
2 files changed, 13 insertions(+)
diff --git a/Documentation/virtual/kvm/mmu.txt b/Documentation/virtual/kvm/mmu.txt
index ce6df51..5a6b2e2 100644
--- a/Documentation/virtual/kvm/mmu.txt
+++ b/Documentation/virtual/kvm/mmu.txt
@@ -214,6 +214,14 @@ Shadow pages contain the following information:
It is only used on 32bit host which helps us to detect whether updating the
64bit spte is complete so that we can avoid reading the truncated value out
of mmu-lock.
+ write_flooding_count:
+ In order to sync the page table between guest and host, the page sometimes
+ needs to be write-protected (see "Synchronized and unsynchronized pages"
+ below), any write to the page can cause write emulation. If the emulation
+ on the page is too frequent we'd better unmap the page to avoid the
+ future emulation. write_flooding_count aims at this optimization which is
+ increased when the page needs to be write emulated and cleared when the
+ page is actually used.
Reverse map
===========
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index 1dac2c1..5eb5382 100644
--- a/arch/x86/include/asm/kvm_host.h
+++ b/arch/x86/include/asm/kvm_host.h
@@ -234,6 +234,11 @@ struct kvm_mmu_page {
int clear_spte_count;
#endif
+ /*
+ * Increased when the page needs to be write emulated, cleared
+ * when the page is actually used as page table to avoid frequent
+ * emulation on the page.
+ */
int write_flooding_count;
};
--
1.8.1.4
next prev parent reply other threads:[~2013-06-19 9:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:09 [PATCH 0/7] KVM: MMU: update mmu documentation Xiao Guangrong
2013-06-19 9:09 ` [PATCH 1/7] KVM: MMU: update the documentation for reverse mapping of parent_pte Xiao Guangrong
2013-06-19 10:32 ` Paolo Bonzini
2013-06-19 9:09 ` [PATCH 2/7] KVM: MMU: document clear_spte_count Xiao Guangrong
2013-06-19 11:32 ` Paolo Bonzini
2013-06-19 11:53 ` Xiao Guangrong
2013-06-19 11:55 ` Paolo Bonzini
2013-06-19 12:25 ` Xiao Guangrong
2013-06-19 12:41 ` Paolo Bonzini
2013-06-19 13:29 ` Xiao Guangrong
2013-06-19 11:40 ` Paolo Bonzini
2013-06-19 12:39 ` Xiao Guangrong
2013-06-19 9:09 ` Xiao Guangrong [this message]
2013-06-19 11:58 ` [PATCH 3/7] KVM: MMU: document write_flooding_count Paolo Bonzini
2013-06-19 12:43 ` Xiao Guangrong
2013-06-19 9:09 ` [PATCH 4/7] KVM: MMU: document mmio page fault Xiao Guangrong
2013-06-19 12:10 ` Paolo Bonzini
2013-06-19 12:59 ` Xiao Guangrong
2013-06-19 9:09 ` [PATCH 5/7] KVM: MMU: document fast page fault in Xiao Guangrong
2013-06-19 12:13 ` Paolo Bonzini
2013-06-19 13:00 ` Xiao Guangrong
2013-06-19 9:09 ` [PATCH 6/7] KVM: MMU: document fast invalidate all pages Xiao Guangrong
2013-06-19 12:25 ` Paolo Bonzini
2013-06-19 13:07 ` Xiao Guangrong
2013-06-19 9:09 ` [PATCH 7/7] KVM: MMU: document fast invalidate all mmio sptes Xiao Guangrong
2013-06-19 12:35 ` Paolo Bonzini
2013-06-19 13:10 ` Xiao Guangrong
2013-06-20 5:21 ` Rob Landley
2013-06-20 8:19 ` Paolo Bonzini
2013-06-19 17:41 ` [PATCH 0/7] KVM: MMU: update mmu documentation Paolo Bonzini
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=1371632965-20077-4-git-send-email-xiaoguangrong@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=avi.kivity@gmail.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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
all inboxes | Powered by JetHome®