[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e9af2f2e-a0cf-1916-c960-2a663e6f4596@redhat.com>
Date: Mon, 18 Oct 2021 19:45:36 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
dave.hansen@...ux.intel.com, x86@...nel.org, yang.zhong@...el.com,
jarkko@...nel.org, bp@...e.de
Subject: Re: [PATCH v3 2/2] x86: sgx_vepc: implement SGX_IOC_VEPC_REMOVE ioctl
On 18/10/21 19:17, Sean Christopherson wrote:
> /*
> * Report errors due to #GP or SGX_ENCLAVE_ACT, but do
> * not WARN as userspace can induce said failures by
> * calling the ioctl concurrently on multiple vEPCs or
> * while one or more CPUs is running the enclave. Only
> * a #PF on EREMOVE indicates a kernel/hardware issue.
> */
> WARN_ON_ONCE(encls_faulted(ret) &&
> ENCLS_TRAPNR(ret) == X86_TRAP_PF);
or != X86_TRAP_GP, just to avoid having a v5? :)
Paolo
Powered by blists - more mailing lists