Skip to contentSkip to conversation

x86:kvm: fix two typos in comment

PATCH In review Tiejun Chen 2 participants 2 messages Sep 22, 2014

Subsystems (3)
x86 KVM KVM x86
lore
Share & tools
lore

Tiejun Chen

author
#0 lore raw

PATCH 1/1 x86:kvm: fix two typos in comment

s/drity/dirty and s/vmsc01/vmcs01

Signed-off-by Tiejun Chen <[email protected]>
---
 arch/x86/kvm/mmu.c | 2 +-
 arch/x86/kvm/vmx.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/x86/kvm/mmu.c +1 -1
index 76398fe..f76bc19 100644
@@ -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
index 6ffd643..305e667 100644
@@ -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
Signature · 1 line
1.9.1
maintainer
#1 lore raw

Il 22/09/2014 04:31, Tiejun Chen ha scritto:

Quoted 27 lines

s/drity/dirty and s/vmsc01/vmcs01

Signed-off-by Tiejun Chen <[email protected]>
---
 arch/x86/kvm/mmu.c | 2 +-
 arch/x86/kvm/vmx.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
arch/x86/kvm/mmu.c +1 -1
index 76398fe..f76bc19 100644
@@ -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 +0 -0
index 6ffd643..305e667 100644

arch/x86/kvm/vmx.c static void vmx_start_preemption_timer(struct kvm_vcpu *vcpu) · line 8014

Quoted 8 lines
arch/x86/kvm/vmx.c +1 -1
@@ -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