KVM: x86/mmu: Misc shadow paging cleanups
Sean Christopherson
maintainercover KVM: x86/mmu: Misc shadow paging cleanups
A handful of loosely related shadow paging cleanups I unearthed. I believe I wrote them when reviewing eager page splitting?
Sean Christopherson (3):
KVM: x86/mmu: Decrease indentation in logic to sync new indirect
shadow page
KVM: x86/mmu: Drop pointless "return" wrapper label in FNAME(fetch)
KVM: x86/mmu: Reword a misleading comment about checking
gpte_changed()
arch/x86/kvm/mmu/paging_tmpl.h | 61 +++++++++++++++++----------------- 1 file changed, 31 insertions(+), 30 deletions(-)
base-commit: 332d2c1d713e232e163386c35a3ba0c1b90df83f
Signature · 1 line
2.46.0.rc2.264.g509ed76dc8-goog
Sean Christopherson
maintainerPATCH 1/3 KVM: x86/mmu: Decrease indentation in logic to sync new indirect shadow page
Combine the back-to-back if-statements for synchronizing children when linking a new indirect shadow page in order to decrease the indentation, and to make it easier to "see" the logic in its entirety.
No functional change intended.
--- arch/x86/kvm/mmu/paging_tmpl.h | 40 ++++++++++++++++------------------ 1 file changed, 19 insertions(+), 21 deletions(-)
arch/x86/kvm/mmu/paging_tmpl.h +19 -21
@@ -674,27 +674,25 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault, sp =kvm_mmu_get_child_sp (vcpu, it.sptep, table_gfn, false, access); -if (sp !=ERR_PTR (-EEXIST )) { -/* -* We must synchronize the pagetable before linking it -* because the guest doesn't need to flush tlb when -* the gpte is changed from non-present to present. -* Otherwise, the guest may use the wrong mapping. -* -* For PG_LEVEL_4K, kvm_mmu_get_page() has already -* synchronized it transiently via kvm_sync_page(). -* -* For higher level pagetable, we synchronize it via -* the slower mmu_sync_children(). If it needs to -* break, some progress has been made; return -* RET_PF_RETRY and retry on the next #PF. -* KVM_REQ_MMU_SYNC is not necessary but it -* expedites the process. -*/ -if (sp->unsync_children && -mmu_sync_children (vcpu, sp, false)) -return RET_PF_RETRY ; - } +/* +* Synchronize the new page before linking it, as the CPU (KVM) +* is architecturally disallowed from inserting non-present +* entries into the TLB, i.e. the guest isn't required to flush +* the TLB when changing the gPTE from non-present to present. +* +* For PG_LEVEL_4K, kvm_mmu_find_shadow_page() has already +* synchronized the page via kvm_sync_page(). +* +* For higher level pages, which cannot be unsync themselves +* but can have unsync children, synchronize via the slower +* mmu_sync_children(). If KVM needs to drop mmu_lock due to +* contention or to reschedule, instruct the caller to retry +* the #PF (mmu_sync_children() ensures forward progress will +* be made). +*/ +if (sp !=ERR_PTR (-EEXIST ) && sp->unsync_children && +mmu_sync_children (vcpu, sp, false)) +return RET_PF_RETRY ;/* * Verify that the gpte in the page we've just write
Signature · 1 line
2.46.0.rc2.264.g509ed76dc8-goog
Sean Christopherson
maintainerPATCH 2/3 KVM: x86/mmu: Drop pointless "return" wrapper label in FNAME(fetch)
In reply to Sean ChristophersonDrop the pointless and poorly named "out_gpte_changed" label, in FNAME(fetch), and instead return RET_PF_RETRY directly.
No functional change intended.
--- arch/x86/kvm/mmu/paging_tmpl.h | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-)
arch/x86/kvm/mmu/paging_tmpl.h +4 -7
@@ -646,10 +646,10 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,* really care if it changes underneath us after this point). */ if (FNAME (gpte_changed)(vcpu, gw, top_level)) - goto out_gpte_changed; +return RET_PF_RETRY ;if (WARN_ON_ONCE (!VALID_PAGE (vcpu->arch.mmu->root.hpa))) - goto out_gpte_changed; +return RET_PF_RETRY ;/* * Load a new root and retry the faulting instruction in the extremely
@@ -659,7 +659,7 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,*/ if (unlikely (kvm_mmu_is_dummy_root (vcpu->arch.mmu->root.hpa))) {kvm_make_request (KVM_REQ_MMU_FREE_OBSOLETE_ROOTS , vcpu); - goto out_gpte_changed; +return RET_PF_RETRY ; }for_each_shadow_entry (vcpu, fault->addr, it) {
@@ -699,7 +699,7 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,* protected is still there. */ if (FNAME (gpte_changed)(vcpu, gw, it.level -1 )) - goto out_gpte_changed; +return RET_PF_RETRY ;if (sp !=ERR_PTR (-EEXIST ))link_shadow_page (vcpu, it.sptep, sp);
@@ -753,9 +753,6 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,FNAME (pte_prefetch)(vcpu, gw, it.sptep);return ret; - -out_gpte_changed: -return RET_PF_RETRY ; }/*
Signature · 1 line
2.46.0.rc2.264.g509ed76dc8-goog
Sean Christopherson
maintainerPATCH 3/3 KVM: x86/mmu: Reword a misleading comment about checking gpte_changed()
In reply to Sean ChristophersonRewrite the comment in FNAME(fetch) to explain why KVM needs to check that the gPTE is still fresh before continuing the shadow page walk, even if KVM already has a linked shadow page for the gPTE in question.
No functional change intended.
--- arch/x86/kvm/mmu/paging_tmpl.h | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
arch/x86/kvm/mmu/paging_tmpl.h +8 -2
@@ -695,8 +695,14 @@ static int FNAME(fetch)(struct kvm_vcpu *vcpu, struct kvm_page_fault *fault,return RET_PF_RETRY ;/* -* Verify that the gpte in the page we've just write -* protected is still there. +* Verify that the gpte in the page, which is now either +* write-protected or unsync, wasn't modified between the fault +* and acquiring mmu_lock. This needs to be done even when +* reusing an existing shadow page to ensure the information +* gathered by the walker matches the information stored in the +* shadow page (which could have been modified by a different +* vCPU even if the page was already linked). Holding mmu_lock +* prevents the shadow page from changing after this point. */ if (FNAME (gpte_changed)(vcpu, gw, it.level -1 ))return RET_PF_RETRY ;
Signature · 1 line
2.46.0.rc2.264.g509ed76dc8-goog
Quoted 11 lines · Sean Christopherson
A handful of loosely related shadow paging cleanups I unearthed. I believe I wrote them when reviewing eager page splitting?
Sean Christopherson (3):
KVM: x86/mmu: Decrease indentation in logic to sync new indirect
shadow page
KVM: x86/mmu: Drop pointless "return" wrapper label in FNAME(fetch)
KVM: x86/mmu: Reword a misleading comment about checking
gpte_changed()[...]
Applied to kvm-x86 mmu, thanks!
[1/3] KVM: x86/mmu: Decrease indentation in logic to sync new indirect shadow page
https://github.com/kvm-x86/linux/commit/174b6e4a25ea [2/3] KVM: x86/mmu: Drop pointless "return" wrapper label in FNAME(fetch) https://github.com/kvm-x86/linux/commit/7d67b03e6fff [3/3] KVM: x86/mmu: Reword a misleading comment about checking gpte_changed() https://github.com/kvm-x86/linux/commit/1dc9cc1c4c23