KVM: fix some typos

Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
[Preserved the iff and a probably intentional weird bracket notation.
 Also dropped the style change to make a single-purpose patch. - Radim]
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>

diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 7c03c0f35444ff9a112a2f3406a894477eaddc2c..1fba9f3562184bc9ae484679e147ab869a7af393 100644 (file)
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -5638,7 +5638,7 @@ void kvm_mmu_slot_remove_write_access(struct kvm *kvm,
         * spte from present to present (changing the spte from present
         * to nonpresent will flush all the TLBs immediately), in other
         * words, the only case we care is mmu_spte_update() where we
-        * haved checked SPTE_HOST_WRITEABLE | SPTE_MMU_WRITEABLE
+        * have checked SPTE_HOST_WRITEABLE | SPTE_MMU_WRITEABLE
         * instead of PT_WRITABLE_MASK, that means it does not depend
         * on PT_WRITABLE_MASK anymore.
         */

diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 70faa3cdc4dc70941324bdcf2844ee34cbc4377a..99e9b6964fce2d0409aa146f5e96ba018cf76f66 100644 (file)
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -9344,7 +9344,7 @@ static void kvm_mmu_slot_apply_flags(struct kvm *kvm,
         * with dirty logging disabled in order to eliminate unnecessary GPA
         * logging in PML buffer (and potential PML buffer full VMEXT). This
         * guarantees leaving PML enabled during guest's lifetime won't have
-        * any additonal overhead from PML when guest is running with dirty
+        * any additional overhead from PML when guest is running with dirty
         * logging disabled for memory slots.
         *
         * kvm_x86_ops->slot_enable_log_dirty is called when switching new slot

diff --git a/virt/kvm/async_pf.c b/virt/kvm/async_pf.c
index 23c2519c5b32a40a2513c7c974ec44ed7199159e..110cbe3f74f80c60c4b0239737f4a03d28d7f8ec 100644 (file)
--- a/virt/kvm/async_pf.c
+++ b/virt/kvm/async_pf.c
@@ -82,7 +82,7 @@ static void async_pf_execute(struct work_struct *work)
        might_sleep();
 
        /*
-        * This work is run asynchromously to the task which owns
+        * This work is run asynchronously to the task which owns
         * mm and might be done in another context, so we must
         * access remotely.
         */