Messages in this thread | | | Date | Tue, 1 Aug 2023 10:32:28 -0500 | Subject | Re: [PATCH v3 01/14] virt: sev-guest: Use AES GCM crypto library | From | Tom Lendacky <> |
| |
On 7/22/23 06:18, Nikunj A Dadhania wrote: > The sev-guest driver encryption code uses Crypto API for SNP guest > messaging to interact with AMD Security processor. For enabling SecureTSC, > SEV-SNP guests need to send a TSC_INFO request guest message before the > smpboot phase starts. Details from the TSC_INFO response will be used to > program the VMSA before the secondary CPUs are brought up. The Crypto API > is not available this early in the boot phase. > > In preparation of moving the encryption code out of sev-guest driver to > support SecureTSC and make reviewing the diff easier, start using AES GCM > library implementation instead of Crypto API. > > Link: https://lore.kernel.org/all/20221103192259.2229-1-ardb@kernel.org > CC: Ard Biesheuvel <ardb@kernel.org> > Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> --- > drivers/virt/coco/sev-guest/Kconfig | 3 +- > drivers/virt/coco/sev-guest/sev-guest.c | 172 +++++++----------------- > drivers/virt/coco/sev-guest/sev-guest.h | 3 + > 3 files changed, 53 insertions(+), 125 deletions(-) >
| |