From: Jarkko Sakkinen <jarkko@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>, Yang Zhong <yang.zhong@intel.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
x86@kernel.org, linux-sgx@vger.kernel.org,
dave.hansen@linux.intel.com
Subject: Re: [RFC/RFT PATCH 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages
Date: Tue, 14 Sep 2021 19:42:56 +0300 [thread overview]
Message-ID: <fb04eae72ca0b24fdb533585775f2f20de9f5beb.camel@kernel.org> (raw)
In-Reply-To: <8e1c6b6d-6a73-827e-f496-b17b3c0f8c89@redhat.com>
On Tue, 2021-09-14 at 12:19 +0200, Paolo Bonzini wrote:
> On 14/09/21 09:10, Yang Zhong wrote:
> > On Mon, Sep 13, 2021 at 09:11:51AM -0400, Paolo Bonzini wrote:
> > > Based on discussions from the previous week(end), this series implements
> > > a ioctl that performs EREMOVE on all pages mapped by a /dev/sgx_vepc
> > > file descriptor. Other possibilities, such as closing and reopening
> > > the device, are racy.
> > >
> > > The patches are untested, but I am posting them because they are simple
> > > and so that Yang Zhong can try using them in QEMU.
> > >
> >
> > Paolo, i re-implemented one reset patch in the Qemu side to call this ioctl(),
> > and did some tests on Windows and Linux guest, the Windows/Linux guest reboot
> > work well.
> >
> > So, it is time for me to send this reset patch to Qemu community? or wait for
> > this kernel patchset merged? thanks!
>
> Let's wait for this patch to be accepted first. I'll wait a little more
> for Jarkko and Dave to comment on this, and include your "Tested-by".
>
> I will also add cond_resched() on the final submission.
Why these would be conflicting tasks? I.e. why could not QEMU use
what is available now and move forward using better mechanism, when
they are available?
BTW, I do all my SGX testing ATM in QEMU (for some weeks). IMHO, it's
already "good enough" for many tasks, even if this fallback case is
not perfectly sorted out.
/Jarkko
next prev parent reply other threads:[~2021-09-14 16:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 13:11 [RFC/RFT PATCH 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Paolo Bonzini
2021-09-13 13:11 ` [PATCH 1/2] x86: sgx_vepc: extract sgx_vepc_remove_page Paolo Bonzini
2021-09-13 14:05 ` Dave Hansen
2021-09-13 14:24 ` Paolo Bonzini
2021-09-13 14:55 ` Dave Hansen
2021-09-13 15:14 ` Paolo Bonzini
2021-09-13 15:29 ` Dave Hansen
2021-09-13 18:35 ` Paolo Bonzini
2021-09-13 19:25 ` Dave Hansen
2021-09-13 21:16 ` Jarkko Sakkinen
2021-09-13 21:15 ` Jarkko Sakkinen
2021-09-13 21:13 ` Jarkko Sakkinen
2021-09-14 5:36 ` Paolo Bonzini
2021-09-14 16:05 ` Jarkko Sakkinen
2021-09-13 21:12 ` Jarkko Sakkinen
2021-09-13 21:00 ` Jarkko Sakkinen
2021-09-13 20:33 ` Jarkko Sakkinen
2021-09-13 13:11 ` [PATCH 2/2] x86: sgx_vepc: implement SGX_IOC_VEPC_REMOVE ioctl Paolo Bonzini
2021-09-13 19:33 ` Dave Hansen
2021-09-13 21:11 ` Sean Christopherson
2021-09-13 22:43 ` Dave Hansen
2021-09-14 10:55 ` Kai Huang
2021-09-14 7:10 ` [RFC/RFT PATCH 0/2] x86: sgx_vepc: implement ioctl to EREMOVE all pages Yang Zhong
2021-09-14 10:19 ` Paolo Bonzini
2021-09-14 16:42 ` Jarkko Sakkinen [this message]
2021-09-14 17:07 ` Paolo Bonzini
2021-09-14 17:40 ` Jarkko Sakkinen
2021-09-14 17:44 ` Jarkko Sakkinen
2021-09-15 8:28 ` 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=fb04eae72ca0b24fdb533585775f2f20de9f5beb.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox