summaryrefslogtreecommitdiffstats
path: root/drivers/virt/Kconfig
diff options
context:
space:
mode:
authorDov Murik <dovmurik@linux.ibm.com>2022-04-12 21:21:24 +0000
committerArd Biesheuvel <ardb@kernel.org>2022-04-13 19:11:18 +0200
commit1227418989346af3af179742cf42ce842e0ad484 (patch)
tree36f02d45fc9b95f624bf93d59d45cb515daeecd5 /drivers/virt/Kconfig
parenta031651ff2144a3d81d4916856c093bc1ea0a413 (diff)
downloadlinux-1227418989346af3af179742cf42ce842e0ad484.tar.gz
linux-1227418989346af3af179742cf42ce842e0ad484.tar.bz2
linux-1227418989346af3af179742cf42ce842e0ad484.zip
efi: Save location of EFI confidential computing area
Confidential computing (coco) hardware such as AMD SEV (Secure Encrypted Virtualization) allows a guest owner to inject secrets into the VMs memory without the host/hypervisor being able to read them. Firmware support for secret injection is available in OVMF, which reserves a memory area for secret injection and includes a pointer to it the in EFI config table entry LINUX_EFI_COCO_SECRET_TABLE_GUID. If EFI exposes such a table entry, uefi_init() will keep a pointer to the EFI config table entry in efi.coco_secret, so it can be used later by the kernel (specifically drivers/virt/coco/efi_secret). It will also appear in the kernel log as "CocoSecret=ADDRESS"; for example: [ 0.000000] efi: EFI v2.70 by EDK II [ 0.000000] efi: CocoSecret=0x7f22e680 SMBIOS=0x7f541000 ACPI=0x7f77e000 ACPI 2.0=0x7f77e014 MEMATTR=0x7ea0c018 The new functionality can be enabled with CONFIG_EFI_COCO_SECRET=y. Signed-off-by: Dov Murik <dovmurik@linux.ibm.com> Reviewed-by: Gerd Hoffmann <kraxel@redhat.com> Link: https://lore.kernel.org/r/20220412212127.154182-2-dovmurik@linux.ibm.com Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/virt/Kconfig')
0 files changed, 0 insertions, 0 deletions