Commit bedd9195 authored by David Matlack's avatar David Matlack Committed by Paolo Bonzini

KVM: x86/mmu: Fix comment mentioning skip_4k

This comment was left over from a previous version of the patch that
introduced wrprot_gfn_range, when skip_4k was passed in instead of
min_level.
Signed-off-by: default avatarDavid Matlack <dmatlack@google.com>
Message-Id: <20210526163227.3113557-1-dmatlack@google.com>
Reviewed-by: default avatarSean Christopherson <seanjc@google.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent a2486020
...@@ -1192,9 +1192,9 @@ bool kvm_tdp_mmu_set_spte_gfn(struct kvm *kvm, struct kvm_gfn_range *range) ...@@ -1192,9 +1192,9 @@ bool kvm_tdp_mmu_set_spte_gfn(struct kvm *kvm, struct kvm_gfn_range *range)
} }
/* /*
* Remove write access from all the SPTEs mapping GFNs [start, end). If * Remove write access from all SPTEs at or above min_level that map GFNs
* skip_4k is set, SPTEs that map 4k pages, will not be write-protected. * [start, end). Returns true if an SPTE has been changed and the TLBs need to
* Returns true if an SPTE has been changed and the TLBs need to be flushed. * be flushed.
*/ */
static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root, static bool wrprot_gfn_range(struct kvm *kvm, struct kvm_mmu_page *root,
gfn_t start, gfn_t end, int min_level) gfn_t start, gfn_t end, int min_level)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment