lkml.org 
[lkml]   [2019]   [Dec]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH] KVM: x86: Fix some comment typos
From
Date
On 06/12/19 09:20, linmiaohe wrote:
> From: Miaohe Lin <linmiaohe@huawei.com>
>
> Fix some typos in comment.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> arch/x86/kvm/mmu/mmu.c | 2 +-
> arch/x86/kvm/vmx/vmx.c | 2 +-
> arch/x86/kvm/x86.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index a81c605abbba..0684b90070de 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -1525,7 +1525,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/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index e58a0daf0f86..e82772d9ab48 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -1371,7 +1371,7 @@ void vmx_vcpu_load_vmcs(struct kvm_vcpu *vcpu, int cpu)
> /*
> * VM exits change the host TR limit to 0x67 after a VM
> * exit. This is okay, since 0x67 covers everything except
> - * the IO bitmap and have have code to handle the IO bitmap
> + * the IO bitmap and we have code to handle the IO bitmap
> * being lost after a VM exit.
> */
> BUILD_BUG_ON(IO_BITMAP_OFFSET - 1 != 0x67);
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index 3ed167e039e5..392d473252f8 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -9790,7 +9790,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.
>

Queued, thanks.

Paolo

\
 
 \ /
  Last update: 2019-12-06 14:17    [W:0.031 / U:6.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site