From: Paolo Bonzini <pbonzini@redhat.com>
To: Liran Alon <liran.alon@oracle.com>,
rkrcmar@redhat.com, kvm@vger.kernel.org
Cc: sean.j.christopherson@intel.com, jmattson@google.com,
vkuznets@redhat.com, Mark Kanda <mark.kanda@oracle.com>
Subject: Re: [PATCH] KVM: nVMX: Use semi-colon instead of comma for exit-handlers initialization
Date: Mon, 18 Nov 2019 23:09:07 +0100 [thread overview]
Message-ID: <83268078-036f-5cc7-9033-b3ad1f05123c@redhat.com> (raw)
In-Reply-To: <20191118191121.43440-1-liran.alon@oracle.com>
On 18/11/19 20:11, Liran Alon wrote:
> Reviewed-by: Mark Kanda <mark.kanda@oracle.com>
> Signed-off-by: Liran Alon <liran.alon@oracle.com>
> ---
> arch/x86/kvm/vmx/nested.c | 26 +++++++++++++-------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index bc11fcbbe12b..229ca7164318 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -6051,23 +6051,23 @@ __init int nested_vmx_hardware_setup(int (*exit_handlers[])(struct kvm_vcpu *))
> init_vmcs_shadow_fields();
> }
>
> - exit_handlers[EXIT_REASON_VMCLEAR] = handle_vmclear,
> - exit_handlers[EXIT_REASON_VMLAUNCH] = handle_vmlaunch,
> - exit_handlers[EXIT_REASON_VMPTRLD] = handle_vmptrld,
> - exit_handlers[EXIT_REASON_VMPTRST] = handle_vmptrst,
> - exit_handlers[EXIT_REASON_VMREAD] = handle_vmread,
> - exit_handlers[EXIT_REASON_VMRESUME] = handle_vmresume,
> - exit_handlers[EXIT_REASON_VMWRITE] = handle_vmwrite,
> - exit_handlers[EXIT_REASON_VMOFF] = handle_vmoff,
> - exit_handlers[EXIT_REASON_VMON] = handle_vmon,
> - exit_handlers[EXIT_REASON_INVEPT] = handle_invept,
> - exit_handlers[EXIT_REASON_INVVPID] = handle_invvpid,
> - exit_handlers[EXIT_REASON_VMFUNC] = handle_vmfunc,
> + exit_handlers[EXIT_REASON_VMCLEAR] = handle_vmclear;
> + exit_handlers[EXIT_REASON_VMLAUNCH] = handle_vmlaunch;
> + exit_handlers[EXIT_REASON_VMPTRLD] = handle_vmptrld;
> + exit_handlers[EXIT_REASON_VMPTRST] = handle_vmptrst;
> + exit_handlers[EXIT_REASON_VMREAD] = handle_vmread;
> + exit_handlers[EXIT_REASON_VMRESUME] = handle_vmresume;
> + exit_handlers[EXIT_REASON_VMWRITE] = handle_vmwrite;
> + exit_handlers[EXIT_REASON_VMOFF] = handle_vmoff;
> + exit_handlers[EXIT_REASON_VMON] = handle_vmon;
> + exit_handlers[EXIT_REASON_INVEPT] = handle_invept;
> + exit_handlers[EXIT_REASON_INVVPID] = handle_invvpid;
> + exit_handlers[EXIT_REASON_VMFUNC] = handle_vmfunc;
>
> kvm_x86_ops->check_nested_events = vmx_check_nested_events;
> kvm_x86_ops->get_nested_state = vmx_get_nested_state;
> kvm_x86_ops->set_nested_state = vmx_set_nested_state;
> - kvm_x86_ops->get_vmcs12_pages = nested_get_vmcs12_pages,
> + kvm_x86_ops->get_vmcs12_pages = nested_get_vmcs12_pages;
> kvm_x86_ops->nested_enable_evmcs = nested_enable_evmcs;
> kvm_x86_ops->nested_get_evmcs_version = nested_get_evmcs_version;
>
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2019-11-18 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 19:11 [PATCH] KVM: nVMX: Use semi-colon instead of comma for exit-handlers initialization Liran Alon
2019-11-18 19:23 ` Jim Mattson
2019-11-18 22:09 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83268078-036f-5cc7-9033-b3ad1f05123c@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=mark.kanda@oracle.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.