Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1634872

[PATCH 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track

Show all headers | View raw

From: Xiao Guangrong <xiaoguangrong@tencent.com>

Current behavior of mmu_spte_update_no_track() does not match
the name of _no_track() as actually the A/D bits are tracked
and returned to the caller

This patch introduces the real _no_track() function to update
the spte regardless of A/D bits and rename the original function
to _track()

The _no_track() function will be used by later patches to update
upper spte which need not care of A/D bits indeed

Signed-off-by: Xiao Guangrong <xiaoguangrong@tencent.com>
---
 arch/x86/kvm/mmu.c | 25 ++++++++++++++++++++++---
 1 file changed, 22 insertions(+), 3 deletions(-)

diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 5586765..ba8e7af 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -583,10 +583,29 @@ static void mmu_spte_set(u64 *sptep, u64 new_spte)
 }
 
 /*
- * Update the SPTE (excluding the PFN), but do not track changes in its
+ * Update the SPTE (excluding the PFN) regardless of accessed/dirty
+ * status which is used to update the upper level spte.
+ */
+static void mmu_spte_update_no_track(u64 *sptep, u64 new_spte)
+{
+	u64 old_spte = *sptep;
+
+	WARN_ON(!is_shadow_present_pte(new_spte));
+
+	if (!is_shadow_present_pte(old_spte)) {
+		mmu_spte_set(sptep, new_spte);
+		return;
+	}
+
+	__update_clear_spte_fast(sptep, new_spte);
+}
+
+/*
+ * Update the SPTE (excluding the PFN), the original value is
+ * returned, based on it, the caller can track changes of its
  * accessed/dirty status.
  */
-static u64 mmu_spte_update_no_track(u64 *sptep, u64 new_spte)
+static u64 mmu_spte_update_track(u64 *sptep, u64 new_spte)
 {
 	u64 old_spte = *sptep;
 
@@ -621,7 +640,7 @@ static u64 mmu_spte_update_no_track(u64 *sptep, u64 new_spte)
 static bool mmu_spte_update(u64 *sptep, u64 new_spte)
 {
 	bool flush = false;
-	u64 old_spte = mmu_spte_update_no_track(sptep, new_spte);
+	u64 old_spte = mmu_spte_update_track(sptep, new_spte);
 
 	if (!is_shadow_present_pte(old_spte))
 		return false;
-- 
2.9.3

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

[PATCH 0/7] KVM: MMU: fast write protect guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 6/7] KVM: MMU: clarify fast_pf_fix_direct_spte guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 5/7] KVM: MMU: allow dirty log without write protect guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 3/7] KVM: MMU: introduce kvm_mmu_write_protect_all_pages guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 7/7] KVM: MMU: stop using mmu_spte_get_lockless under mmu-lock guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 2/7] KVM: MMU: introduce possible_writable_spte_bitmap guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-03 14:30 +0200
    Re: [PATCH 0/7] KVM: MMU: fast write protect Xiao Guangrong <guangrong.xiao@gmail.com> - 2017-05-03 17:00 +0200
      Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-03 17:00 +0200
        Re: [PATCH 0/7] KVM: MMU: fast write protect Xiao Guangrong <guangrong.xiao@gmail.com> - 2017-05-04 05:40 +0200
          Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-04 09:10 +0200

csiph-web