From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>, "Christopherson,,
Sean" <seanjc@google.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>
Subject: Re: [PATCH 2/2] KVM: VMX: Inject #GP, not #UD, if SGX2 ENCLS leafs are unsupported
Date: Thu, 6 Apr 2023 09:17:54 +0000 [thread overview]
Message-ID: <03504796e42badbb39d34b9e99c62ac4c2bb9b6f.camel@intel.com> (raw)
In-Reply-To: <20230405234556.696927-3-seanjc@google.com>
On Wed, 2023-04-05 at 16:45 -0700, Sean Christopherson wrote:
> Per Intel's SDM, unsupported ENCLS leafs result in a #GP, not a #UD.
> SGX1 is a special snowflake as the SGX1 flag is used by the CPU as a
> "soft" disable, e.g. if software disables machine check reporting, i.e.
> having SGX but not SGX1 is effectively "SGX completely unsupported" and
> and thus #UDs.
If I recall correctly, this is an erratum which can clear SGX1 in CPUID while
the SGX flag is still in CPUID?
But I am not sure whether this part is relevant to this patch? Because SDM
already says ENCLS causes #UD if SGX1 isn't present. This patch changes
"unsupported leaf" from causing #UD to causing #GP, which is also documented in
SDM.
>
> Fixes: 9798adbc04cf ("KVM: VMX: Frame in ENCLS handler for SGX virtualization")
> Cc: Binbin Wu <binbin.wu@linux.intel.com>
> Cc: Kai Huang <kai.huang@intel.com>
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/vmx/sgx.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/sgx.c b/arch/x86/kvm/vmx/sgx.c
> index f881f6ff6408..1c092ab89c33 100644
> --- a/arch/x86/kvm/vmx/sgx.c
> +++ b/arch/x86/kvm/vmx/sgx.c
> @@ -350,11 +350,12 @@ static int handle_encls_einit(struct kvm_vcpu *vcpu)
>
> static inline bool encls_leaf_enabled_in_guest(struct kvm_vcpu *vcpu, u32 leaf)
> {
> - if (!enable_sgx || !guest_cpuid_has(vcpu, X86_FEATURE_SGX))
> - return false;
> -
> + /*
> + * ENCLS #UDs if SGX1 isn't supported, i.e. this point will be reached
Why #UDs instead of #UD? Is #UD a verb?
> + * if and only if the SGX1 leafs are enabled.
> + */
Is it better to move "ENCLS #UDs if SGX1 isn't supported" part to ...
> if (leaf >= ECREATE && leaf <= ETRACK)
> - return guest_cpuid_has(vcpu, X86_FEATURE_SGX1);
> + return true;
>
> if (leaf >= EAUG && leaf <= EMODT)
> return guest_cpuid_has(vcpu, X86_FEATURE_SGX2);
> @@ -373,9 +374,11 @@ int handle_encls(struct kvm_vcpu *vcpu)
> {
> u32 leaf = (u32)kvm_rax_read(vcpu);
>
> - if (!encls_leaf_enabled_in_guest(vcpu, leaf)) {
> + if (!enable_sgx || !guest_cpuid_has(vcpu, X86_FEATURE_SGX) ||
> + !guest_cpuid_has(vcpu, X86_FEATURE_SGX1)) {
> kvm_queue_exception(vcpu, UD_VECTOR);
... above here, where the actual code reside?
> - } else if (!sgx_enabled_in_guest_bios(vcpu) || !is_paging(vcpu)) {
> + } else if (!encls_leaf_enabled_in_guest(vcpu, leaf) ||
> + !sgx_enabled_in_guest_bios(vcpu) || !is_paging(vcpu)) {
> kvm_inject_gp(vcpu, 0);
> } else {
> if (leaf == ECREATE)
> --
> 2.40.0.348.gf938b09366-goog
>
next prev parent reply other threads:[~2023-04-06 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 23:45 [PATCH 0/2] KVM: VMX: Fixes for faults on ENCLS emulation Sean Christopherson
2023-04-05 23:45 ` [PATCH 1/2] KVM: VMX: Inject #GP on ENCLS if vCPU has paging disabled (CR0.PG==0) Sean Christopherson
2023-04-06 8:54 ` Huang, Kai
2023-04-21 9:18 ` Huang, Kai
2023-04-05 23:45 ` [PATCH 2/2] KVM: VMX: Inject #GP, not #UD, if SGX2 ENCLS leafs are unsupported Sean Christopherson
2023-04-06 9:17 ` Huang, Kai [this message]
2023-04-06 18:00 ` Sean Christopherson
2023-04-12 11:15 ` Huang, Kai
2023-04-12 14:38 ` Sean Christopherson
2023-04-12 22:28 ` Huang, Kai
2023-04-21 9:17 ` Huang, Kai
2023-04-06 9:19 ` [PATCH 0/2] KVM: VMX: Fixes for faults on ENCLS emulation Huang, Kai
2023-06-03 0:55 ` Sean Christopherson
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=03504796e42badbb39d34b9e99c62ac4c2bb9b6f.camel@intel.com \
--to=kai.huang@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®