On Wed, Dec 11, 2019 at 02:26:22PM +0800, linmiaohe wrote:
> From: Miaohe Lin <linmiaohe@xxxxxxxxxx>
>
> Fix some typos and add missing parentheses in the comments.
>
> Signed-off-by: Miaohe Lin <linmiaohe@xxxxxxxxxx>
> ---
> arch/x86/kvm/hyperv.c | 2 +-
> arch/x86/kvm/lapic.c | 2 +-
> arch/x86/kvm/vmx/nested.c | 2 +-
> arch/x86/kvm/vmx/vmx.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
> index c7d4640b7b1c..a48d5708f1f8 100644
> --- a/arch/x86/kvm/hyperv.c
> +++ b/arch/x86/kvm/hyperv.c
> @@ -1122,7 +1122,7 @@ static int kvm_hv_set_msr(struct kvm_vcpu *vcpu, u32 msr, u64 data, bool host)
> return 1;
>
> /*
> - * Clear apic_assist portion of f(struct hv_vp_assist_page
> + * Clear apic_assist portion of struct hv_vp_assist_page
> * only, there can be valuable data in the rest which needs
> * to be preserved e.g. on migration.
> */
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index 679692b55f6d..ea402e741bd5 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -969,7 +969,7 @@ bool kvm_irq_delivery_to_apic_fast(struct kvm *kvm, struct kvm_lapic *src,
> * - For single-destination interrupts, handle it in posted mode
> * - Else if vector hashing is enabled and it is a lowest-priority
> * interrupt, handle it in posted mode and use the following mechanism
> - * to find the destinaiton vCPU.
> + * to find the destination vCPU.
> * 1. For lowest-priority interrupts, store all the possible
> * destination vCPUs in an array.
> * 2. Use "guest vector % max number of destination vCPUs" to find
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index 7b01ef1d87e6..63ab49de324d 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -3427,7 +3427,7 @@ static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch)
>
> /*
> * On a nested exit from L2 to L1, vmcs12.guest_cr0 might not be up-to-date
> - * because L2 may have changed some cr0 bits directly (CRO_GUEST_HOST_MASK).
> + * because L2 may have changed some cr0 bits directly (CR0_GUEST_HOST_MASK).
Holy cow this one is hard to see :-)
> * This function returns the new value we should put in vmcs12.guest_cr0.
> * It's not enough to just return the vmcs02 GUEST_CR0. Rather,
> * 1. Bits that neither L0 nor L1 trapped, were set directly by L2 and are now
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index bf24fbb2056c..1be3854f1090 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -6720,7 +6720,7 @@ static struct kvm_vcpu *vmx_create_vcpu(struct kvm *kvm, unsigned int id)
> * If PML is turned on, failure on enabling PML just results in failure
> * of creating the vcpu, therefore we can simplify PML logic (by
> * avoiding dealing with cases, such as enabling PML partially on vcpus
> - * for the guest, etc.
> + * for the guest), etc.
> */
> if (enable_pml) {
> vmx->pml_pg = alloc_page(GFP_KERNEL_ACCOUNT | __GFP_ZERO);
> --
> 2.19.1
>
