From: Yang Zhong <yang.zhong@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
dave.hansen@linux.intel.com, seanjc@google.com, x86@kernel.org,
yang.zhong@intel.com, jarkko@kernel.org
Subject: Re: [PATCH v2 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages
Date: Thu, 14 Oct 2021 20:21:02 +0800 [thread overview]
Message-ID: <20211014122102.GA22574@yangzhon-Virtual> (raw)
In-Reply-To: <20211012105708.2070480-1-pbonzini@redhat.com>
On Tue, Oct 12, 2021 at 06:57:06AM -0400, Paolo Bonzini wrote:
> Add to /dev/sgx_vepc a ioctl that brings vEPC pages back to uninitialized
> state with EREMOVE. This is useful in order to match the expectations
> of guests after reboot, and to match the behavior of real hardware.
>
> The ioctl is a cleaner alternative to closing and reopening the
> /dev/sgx_vepc device; reopening /dev/sgx_vepc could be problematic in
> case userspace has sandboxed itself since the time it first opened the
> device, and has thus lost permissions to do so.
>
> If possible, I would like these patches to be included in 5.15 through
> either the x86 or the KVM tree.
>
Paolo, i did the below tests to verify those two patches on ICX server
(1). Windows2019 and Linux guest reboot
(2). One 10G vepc, and started 500 enclaves(each 2G) in guest, and then reset
the guest with 'system_reset' command in monitor.
(3). One 100K vepc, and start one 2M enclave in guest, then reset the guest
with 'system_reset' command in the monitor.
All those tests are successful, and the kernel changes work well. Thanks for
the great support!
Yang
> Thanks,
>
> Paolo
>
> Changes from RFC:
> - improved commit messages, added documentation
> - renamed ioctl from SGX_IOC_VEPC_REMOVE to SGX_IOC_VEPC_REMOVE_ALL
>
> Change from v1:
> - fixed documentation and code to cover SGX_ENCLAVE_ACT errors
> - removed Tested-by since the code is quite different now
>
> Paolo Bonzini (2):
> x86: sgx_vepc: extract sgx_vepc_remove_page
> x86: sgx_vepc: implement SGX_IOC_VEPC_REMOVE_ALL ioctl
>
> Documentation/x86/sgx.rst | 26 +++++++++++++
> arch/x86/include/asm/sgx.h | 3 ++
> arch/x86/include/uapi/asm/sgx.h | 2 +
> arch/x86/kernel/cpu/sgx/virt.c | 69 ++++++++++++++++++++++++++++++---
> 4 files changed, 95 insertions(+), 5 deletions(-)
>
> --
> 2.27.0
prev parent reply other threads:[~2021-10-14 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 10:57 [PATCH v2 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Paolo Bonzini
2021-10-12 10:57 ` [PATCH v2 1/2] x86: sgx_vepc: extract sgx_vepc_remove_page Paolo Bonzini
2021-10-12 16:53 ` Jarkko Sakkinen
2021-10-14 22:10 ` Dave Hansen
2021-10-12 10:57 ` [PATCH v2 2/2] x86: sgx_vepc: implement SGX_IOC_VEPC_REMOVE ioctl Paolo Bonzini
2021-10-12 16:57 ` Jarkko Sakkinen
2021-10-12 17:03 ` Paolo Bonzini
2021-10-12 17:43 ` Jarkko Sakkinen
2021-10-14 22:14 ` Dave Hansen
2021-10-15 22:29 ` Sean Christopherson
2021-10-16 7:14 ` Paolo Bonzini
2021-10-13 6:54 ` [PATCH v2 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Borislav Petkov
2021-10-13 7:15 ` Paolo Bonzini
2021-10-13 7:38 ` Borislav Petkov
2021-10-14 12:21 ` Yang Zhong [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=20211014122102.GA22574@yangzhon-Virtual \
--to=yang.zhong@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
/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