Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b4619660 authored by Tiejun Chen's avatar Tiejun Chen Committed by Paolo Bonzini
Browse files

kvm: x86: fix two typos in comment 



s/drity/dirty and s/vmsc01/vmcs01

Signed-off-by: default avatarTiejun Chen <tiejun.chen@intel.com>
Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
parent 4566654b

arch/x86/kvm/mmu.c

+1 −1
Original line number Diff line number Diff line
@@ -1174,7 +1174,7 @@ static void drop_large_spte(struct kvm_vcpu *vcpu, u64 *sptep) 
 * Write-protect on the specified @sptep, @pt_protect indicates whether

 * spte write-protection is caused by protecting shadow page table.

 *

 * Note: write protection is difference between drity logging and spte

 * Note: write protection is difference between dirty logging and spte

 * protection:

 * - for dirty logging, the spte can be set to writable at anytime if

 *   its dirty bitmap is properly set.

arch/x86/kvm/vmx.c

+1 −1
Original line number Diff line number Diff line
@@ -8005,7 +8005,7 @@ static void vmx_start_preemption_timer(struct kvm_vcpu *vcpu) 
/*

 * prepare_vmcs02 is called when the L1 guest hypervisor runs its nested

 * L2 guest. L1 has a vmcs for L2 (vmcs12), and this function "merges" it

 * with L0's requirements for its guest (a.k.a. vmsc01), so we can run the L2

 * with L0's requirements for its guest (a.k.a. vmcs01), so we can run the L2

 * guest in a way that will both be appropriate to L1's requests, and our

 * needs. In addition to modifying the active vmcs (which is vmcs02), this

 * function also has additional necessary side-effects, like setting various