Messages in this thread | | | From | "Reshetova, Elena" <> | Subject | RE: [PATCH 00/11] Provide SEV-SNP support for running under an SVSM | Date | Tue, 27 Feb 2024 14:56:14 +0000 |
| |
> > Kirill already commented on this, and the answer is of course we can, but imo > we > > need to see a bigger picture first. If we go with option 2 above, then coming > with a > > joint protocol is only limitedly useful because likely we wont be able to share > the > > code in the guest kernel. Ideally I think we want a common concept and a > common > > protocol that we can share in both guest kernel and coconut-svsm. > > > > Btw, is continuing discussion here the best/preferred/efficient way forward? > Or should we > > setup a call with anyone who is interested in the topic to form a joint > understanding > > on what can be done here? > > I'm not sure what the best way forward is since I'm not sure what a common > concept / common protocol would look like. If you feel we can effectively > describe it via email, then we should continue that, maybe on a new thread > under linux-coco. If not, then a call might be best.
OK, let us first put some proposal from our side on how this potentially could look like. It might be easier to have a discussion against smth more concrete.
Best Regards, Elena.
> > Thanks, > Tom > > > > > Best Regards, > > Elena. > > > > > >> > >> Thanks, > >> Tom > >> > >>> > >>> 5. Anything else is missing? > >>> > >>> References: > >>> > >>> [1] https://lkml.org/lkml/2023/11/22/1089 > >>> > >>> [2] MSFT hyper-v implementation of AMD SEV-SNP !VMPL0 guest and TDX L2 > >>> partitioning guest: > >>> https://elixir.bootlin.com/linux/latest/source/arch/x86/hyperv/ivm.c#L575 > >>> > >>> [3] https://github.com/coconut-svsm/svsm > >>> > >>> [4] https://www.amd.com/content/dam/amd/en/documents/epyc- > technical- > >> docs/specifications/58019.pdf > >>> > >>>
| |