From: Paolo Bonzini <pbonzini@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: dave.hansen@linux.intel.com, seanjc@google.com, x86@kernel.org,
yang.zhong@intel.com, bp@suse.de
Subject: Re: [PATCH v3 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages
Date: Mon, 18 Oct 2021 15:03:05 +0200 [thread overview]
Message-ID: <337bafa9-a627-f50a-f73c-0e36c2282d55@redhat.com> (raw)
In-Reply-To: <5f816a61bb95c5d3ea4c26251bb0a4b044aba0e6.camel@kernel.org>
On 18/10/21 14:51, Jarkko Sakkinen wrote:
> BTW, do you already have patch for QEMU somewhere, which uses
> this new functionality? Would like to peek at it just to see
> the usage pattern.
Yang was going to post them this week; the way to trigger them is just
to do a reboot from within a Linux guest.
Paolo
> Also, can you provide some way to stress test QEMU so that this
> code path gets executed? I'm already using QEMU as my main test
> platform for SGX, so it's not a huge stretch for me to test it.
>
> This way I can also provide tested-by for the corresponding QEMU
> path.
next prev parent reply other threads:[~2021-10-18 13:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 7:14 [PATCH v3 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Paolo Bonzini
2021-10-16 7:14 ` [PATCH v3 1/2] x86: sgx_vepc: extract sgx_vepc_remove_page Paolo Bonzini
2021-10-16 7:14 ` [PATCH v3 2/2] x86: sgx_vepc: implement SGX_IOC_VEPC_REMOVE ioctl Paolo Bonzini
2021-10-18 17:17 ` Sean Christopherson
2021-10-18 17:45 ` Paolo Bonzini
2021-10-18 17:47 ` Sean Christopherson
2021-10-18 12:51 ` [PATCH v3 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Jarkko Sakkinen
2021-10-18 13:03 ` Paolo Bonzini [this message]
2021-10-18 13:28 ` Jarkko Sakkinen
2021-10-18 12:58 ` Borislav Petkov
2021-10-19 10:17 ` Yang Zhong
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=337bafa9-a627-f50a-f73c-0e36c2282d55@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=jarkko@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=x86@kernel.org \
--cc=yang.zhong@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.