On Thu, Feb 15, 2024 at 05:01:13PM +0530, 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.
>
> Drop __enc_payload() and dec_payload() helpers as both are pretty small and
> can be moved to the respective callers.
>
> CC: Ard Biesheuvel <ardb@xxxxxxxxxx>
> Signed-off-by: Nikunj A Dadhania <nikunj@xxxxxxx>
> Reviewed-by: Tom Lendacky <thomas.lendacky@xxxxxxx>
> Tested-by: Peter Gonda <pgonda@xxxxxxxxxx>
> ---
> drivers/virt/coco/sev-guest/Kconfig | 4 +-
> drivers/virt/coco/sev-guest/sev-guest.c | 175 ++++++------------------
> drivers/virt/coco/sev-guest/sev-guest.h | 3 +
> 3 files changed, 43 insertions(+), 139 deletions(-)
Acked-by: Borislav Petkov (AMD) <bp@xxxxxxxxx>
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
