KVM: SVM: Create a separate mapping for the SEV-ES save area

Browse source

The save area for SEV-ES/SEV-SNP guests, as used by the hardware, is
different from the save area of a non SEV-ES/SEV-SNP guest.

This is the first step in defining the multiple save areas to keep them
separate and ensuring proper operation amongst the different types of
guests. Create an SEV-ES/SEV-SNP save area and adjust usage to the new
save area definition where needed.

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/20220405182743.308853-1-brijesh.singh@amd.com

...

This commit is contained in:

Tom Lendacky 2022-04-05 13:27:43 -05:00 • committed by Borislav Petkov

parent 046f773be1

commit 3dd2775b74

4 changed files with 82 additions and 35 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

89

arch/x86/include/asm/svm.h

View file

22

arch/x86/kvm/svm/sev.c

View file

4

arch/x86/kvm/svm/svm.c

View file

4

arch/x86/kvm/svm/svm.h

View file