From: Miaohe Lin Date: Fri, 6 Dec 2019 08:20:18 +0000 (+0800) Subject: KVM: x86: Fix some comment typos X-Git-Tag: v5.10.7~3338^2~161 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0a03cbdac115fdcc06fd9d05ce3c389d0ead9a71;p=platform%2Fkernel%2Flinux-rpi.git KVM: x86: Fix some comment typos Fix some typos in comment. Signed-off-by: Miaohe Lin Signed-off-by: Paolo Bonzini --- diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c index 35d3709..c19f3cc 100644 --- a/arch/x86/kvm/mmu/mmu.c +++ b/arch/x86/kvm/mmu/mmu.c @@ -1529,7 +1529,7 @@ struct rmap_iterator { /* * Iteration must be started by this function. This should also be used after * removing/dropping sptes from the rmap link because in such cases the - * information in the itererator may not be valid. + * information in the iterator may not be valid. * * Returns sptep if found, NULL otherwise. */ diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c index 16902d0..3051324 100644 --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -9792,7 +9792,7 @@ static void kvm_mmu_slot_apply_flags(struct kvm *kvm, * * The reason is, in case of PML, we need to set D-bit for any slots * with dirty logging disabled in order to eliminate unnecessary GPA - * logging in PML buffer (and potential PML buffer full VMEXT). This + * logging in PML buffer (and potential PML buffer full VMEXIT). This * guarantees leaving PML enabled during guest's lifetime won't have * any additional overhead from PML when guest is running with dirty * logging disabled for memory slots.