On Fri, Mar 10, 2017 at 04:41:56PM -0600, Brijesh Singh wrote:
> I can take a look at fixing those warning. In my initial attempt was to create
> a new function to clear encryption bit but it ended up looking very similar to
> __change_page_attr_set_clr() hence decided to extend the exiting function to
> use memblock_alloc().
... except that having all that SEV-specific code in main code paths is
yucky and I'd like to avoid it, if possible.
> Early in boot process, guest kernel allocates some structure (its either
> statically allocated or dynamic allocated via memblock_alloc). And shares the
> physical
> address of these structure with hypervisor. Since entire guest memory area is
> mapped
> as encrypted hence those structure's are mapped as encrypted memory range. We
> need
> a method to clear the encryption bit. Sometime these structure maybe part of
> 2M pages
> and need to split into smaller pages.
So how hard would it be if the hypervisor allocated that memory for the
guest instead? It would allocate it decrypted and guest would need to
access it decrypted too. All in preparation for SEV-ES which will need a
block of unencrypted memory for the guest anyway...
> In most cases, guest and hypervisor communication starts as soon as guest
> provides
> the physical address to hypervisor. So we must map the pages as decrypted
> before
> sharing the physical address to hypervisor.
See above: so purely theoretically speaking, the hypervisor could prep
that decrypted range for the guest. I'd look in Paolo's direction,
though, for the feasibility of something like that.
Thanks.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284
(AG Nürnberg)
--
