From: David Hildenbrand <david@redhat.com>
To: Bandan Das <bsd@redhat.com>, kvm@vger.kernel.org
Cc: pbonzini@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3 v2] KVM: vmx: Enable VMFUNCs
Date: Mon, 10 Jul 2017 10:54:00 +0200 [thread overview]
Message-ID: <71bb73d6-c64c-3fee-ea7d-4fa0f2d4682e@redhat.com> (raw)
In-Reply-To: <20170706230323.29952-2-bsd@redhat.com>
> /*
> * 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
next prev parent reply other threads:[~2017-07-10 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 23:03 [PATCH 0/3 v2] Expose VMFUNC to the nested hypervisor Bandan Das
2017-07-06 23:03 ` [PATCH 1/3 v2] KVM: vmx: Enable VMFUNCs Bandan Das
2017-07-10 8:54 ` David Hildenbrand [this message]
2017-07-10 9:17 ` Paolo Bonzini
2017-07-10 9:20 ` David Hildenbrand
2017-07-10 9:21 ` Paolo Bonzini
2017-07-06 23:03 ` [PATCH 2/3 v2] KVM: nVMX: Enable VMFUNC for the L1 hypervisor Bandan Das
2017-07-10 9:17 ` David Hildenbrand
2017-07-10 11:03 ` Paolo Bonzini
2017-07-10 12:15 ` David Hildenbrand
2017-07-06 23:03 ` [PATCH 3/3 v2] KVM: nVMX: Emulate EPTP switching " Bandan Das
2017-07-07 8:30 ` Paolo Bonzini
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=71bb73d6-c64c-3fee-ea7d-4fa0f2d4682e@redhat.com \
--to=david@redhat.com \
--cc=bsd@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox