[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D4ECF8D3-C483-4E75-AD41-2CEFDF56B12D@alien8.de>
Date: Wed, 31 Mar 2021 08:44:23 +0200
From: Boris Petkov <bp@...en8.de>
To: Kai Huang <kai.huang@...el.com>
CC: seanjc@...gle.com, kvm@...r.kernel.org, x86@...nel.org,
linux-sgx@...r.kernel.org, linux-kernel@...r.kernel.org,
jarkko@...nel.org, luto@...nel.org, dave.hansen@...el.com,
rick.p.edgecombe@...el.com, haitao.huang@...el.com,
pbonzini@...hat.com, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com
Subject: Re: [PATCH v3 05/25] x86/sgx: Introduce virtual EPC for use by KVM guests
On March 31, 2021 3:10:32 AM GMT+02:00, Kai Huang <kai.huang@...el.com> wrote:
> The admin will be aware of
>such EPC
>allocation disjoint situation, and deploy host enclaves/KVM SGX guests
>accordingly.
The admin will be aware because...
1) he's following our discussion?
2) he'll read the commit messages and hopefully understand?
3) we *actually* have documentation somewhere explaining how we envision that stuff to be used?
Or none of the above and he'll end up doing whatever and then he'll eventually figure out that we don't support that use case but he's doing it already anyway and we don't break userspace so we have to support it now and we're stuck somewhere between a rock and a hard place?
Hmm, I think we have enough misguided use cases as it is - don't need another one.
--
Sent from a small device: formatting sux and brevity is inevitable.
Powered by blists - more mailing lists