Il 22/09/2014 04:31, Tiejun Chen ha scritto: > s/drity/dirty and s/vmsc01/vmcs01 > > Signed-off-by: Tiejun Chen <tiejun.chen@xxxxxxxxx> > --- > arch/x86/kvm/mmu.c | 2 +- > arch/x86/kvm/vmx.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c > index 76398fe..f76bc19 100644 > --- a/arch/x86/kvm/mmu.c > +++ b/arch/x86/kvm/mmu.c > @@ -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. > diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c > index 6ffd643..305e667 100644 > --- a/arch/x86/kvm/vmx.c > +++ b/arch/x86/kvm/vmx.c > @@ -8008,7 +8008,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 > Thanks, applying. Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
