summaryrefslogtreecommitdiffstats
path: root/drivers/virt
diff options
context:
space:
mode:
authorBrijesh Singh <brijesh.singh@amd.com>2022-02-24 10:56:21 -0600
committerBorislav Petkov <bp@suse.de>2022-04-07 16:47:12 +0200
commit3a45b3753849c4a12cca2dd176c0192cd2a63e62 (patch)
treea471b432becf85ca50aa99742cfd0630cf033ff0 /drivers/virt
parentd5af44dde5461d125d1602ac913ab5c6bdf09b8b (diff)
downloadlinux-3a45b3753849c4a12cca2dd176c0192cd2a63e62.tar.bz2
x86/sev: Register SEV-SNP guest request platform device
Version 2 of the GHCB specification provides a Non Automatic Exit (NAE) event type that can be used by the SEV-SNP guest to communicate with the PSP without risk from a malicious hypervisor who wishes to read, alter, drop or replay the messages sent. SNP_LAUNCH_UPDATE can insert two special pages into the guest’s memory: the secrets page and the CPUID page. The PSP firmware populates the contents of the secrets page. The secrets page contains encryption keys used by the guest to interact with the firmware. Because the secrets page is encrypted with the guest’s memory encryption key, the hypervisor cannot read the keys. See SEV-SNP firmware spec for further details on the secrets page format. Create a platform device that the SEV-SNP guest driver can bind to get the platform resources such as encryption key and message id to use to communicate with the PSP. The SEV-SNP guest driver provides a userspace interface to get the attestation report, key derivation, extended attestation report etc. Signed-off-by: Brijesh Singh <brijesh.singh@amd.com> Signed-off-by: Borislav Petkov <bp@suse.de> Link: https://lore.kernel.org/r/20220307213356.2797205-43-brijesh.singh@amd.com
Diffstat (limited to 'drivers/virt')
0 files changed, 0 insertions, 0 deletions