summaryrefslogtreecommitdiffstats
path: root/arch/arm/configs/viper_defconfig
diff options
context:
space:
mode:
authorAlper Gun <alpergun@google.com>2021-06-10 19:46:04 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2021-06-11 17:52:48 +0200
commit934002cd660b035b926438244b4294e647507e13 (patch)
treec778e64331b20b6fc52053468c584c51a0a3378a /arch/arm/configs/viper_defconfig
parentKVM: x86: Immediately reset the MMU context when the SMM flag is cleared (diff)
downloadlinux-934002cd660b035b926438244b4294e647507e13.tar.xz
linux-934002cd660b035b926438244b4294e647507e13.zip
KVM: SVM: Call SEV Guest Decommission if ASID binding fails
Send SEV_CMD_DECOMMISSION command to PSP firmware if ASID binding fails. If a failure happens after a successful LAUNCH_START command, a decommission command should be executed. Otherwise, guest context will be unfreed inside the AMD SP. After the firmware will not have memory to allocate more SEV guest context, LAUNCH_START command will begin to fail with SEV_RET_RESOURCE_LIMIT error. The existing code calls decommission inside sev_unbind_asid, but it is not called if a failure happens before guest activation succeeds. If sev_bind_asid fails, decommission is never called. PSP firmware has a limit for the number of guests. If sev_asid_binding fails many times, PSP firmware will not have resources to create another guest context. Cc: stable@vger.kernel.org Fixes: 59414c989220 ("KVM: SVM: Add support for KVM_SEV_LAUNCH_START command") Reported-by: Peter Gonda <pgonda@google.com> Signed-off-by: Alper Gun <alpergun@google.com> Reviewed-by: Marc Orr <marcorr@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Message-Id: <20210610174604.2554090-1-alpergun@google.com>
Diffstat (limited to 'arch/arm/configs/viper_defconfig')
0 files changed, 0 insertions, 0 deletions