On Fri, Sep 29, 2017 at 07:28:47AM -0500, Brijesh Singh wrote:
> if we are adding a chicken bits then I think we should do it for both
> "smeonly" and "sevonly". We can boot host OS with SME disabled and SEV
> enabled, and still be able to create the SEV guest from the hypervisor.
Sure, but is that a real use case? I mean, who would want to run
encrypted guests on an unencrypted hypervisor?
> How about this ?
>
> mem_encrypt=on both SME and SEV enabled
> mem_encrypt=sev only SEV enabled
> mem_encrypt=sme only SME enabled
> mem_encrypt=off neither SME/SEV are enabled
I like those short mnemonics, ACK. Less typing is always good.
Thx.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)
--
