[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71bb73d6-c64c-3fee-ea7d-4fa0f2d4682e@redhat.com>
Date: Mon, 10 Jul 2017 10:54:00 +0200
From: David Hildenbrand <david@...hat.com>
To: Bandan Das <bsd@...hat.com>, kvm@...r.kernel.org
Cc: pbonzini@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3 v2] KVM: vmx: Enable VMFUNCs
> /*
> * The exit handlers return 1 if the exit was handled fully and guest execution
> * may resume. Otherwise they set the kvm_run parameter to indicate what needs
> @@ -7790,6 +7806,7 @@ static int (*const kvm_vmx_exit_handlers[])(struct kvm_vcpu *vcpu) = {
> [EXIT_REASON_XSAVES] = handle_xsaves,
> [EXIT_REASON_XRSTORS] = handle_xrstors,
> [EXIT_REASON_PML_FULL] = handle_pml_full,
> + [EXIT_REASON_VMFUNC] = handle_vmfunc,
> [EXIT_REASON_PREEMPTION_TIMER] = handle_preemption_timer,
> };
>
> @@ -8111,6 +8128,9 @@ static bool nested_vmx_exit_handled(struct kvm_vcpu *vcpu)
> case EXIT_REASON_PML_FULL:
> /* We emulate PML support to L1. */
> return false;
> + case EXIT_REASON_VMFUNC:
> + /* VM functions are emulated through L2->L0 vmexits. */
> + return false;
This would fit better into the second patch.
> default:
> return true;
> }
>
Looks good to me.
--
Thanks,
David
Powered by blists - more mailing lists