KVM: SVM: Create a separate mapping for the GHCB save area
authorTom Lendacky <thomas.lendacky@amd.com>
Mon, 7 Mar 2022 21:33:13 +0000 (15:33 -0600)
committerBorislav Petkov <bp@suse.de>
Wed, 6 Apr 2022 10:13:34 +0000 (12:13 +0200)
commita4690359eaec985a1351786da887df1ba92440a0
tree6c156bc85650356efac115dcda2d330535bbdcc8
parent3dd2775b74c9b1b01d19805877ab45bc47c4a5a5
KVM: SVM: Create a separate mapping for the GHCB save area

The initial implementation of the GHCB spec was based on trying to keep
the register state offsets the same relative to the VM save area. However,
the save area for SEV-ES has changed within the hardware causing the
relation between the SEV-ES save area to change relative to the GHCB save
area.

This is the second step in defining the multiple save areas to keep them
separate and ensuring proper operation amongst the different types of
guests. Create a GHCB save area that matches the GHCB specification.

Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Reviewed-by: Venu Busireddy <venu.busireddy@oracle.com>
Link: https://lore.kernel.org/r/20220307213356.2797205-4-brijesh.singh@amd.com
arch/x86/include/asm/svm.h