diff options
| author | Tom Lendacky <thomas.lendacky@amd.com> | 2021-12-02 19:52:05 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-12-05 09:02:04 +0100 |
| commit | ad5b353240c8837109d1bcc6c3a9a501d7f6a960 (patch) | |
| tree | ea5b8abca9f129f4d085108c6538e98a950124f0 /sound/soc/tegra/tegra210_sfc.h | |
| parent | KVM: SEV: Fall back to vmalloc for SEV-ES scratch area if necessary (diff) | |
| download | linux-ad5b353240c8837109d1bcc6c3a9a501d7f6a960.tar.xz linux-ad5b353240c8837109d1bcc6c3a9a501d7f6a960.zip | |
KVM: SVM: Do not terminate SEV-ES guests on GHCB validation failure
Currently, an SEV-ES guest is terminated if the validation of the VMGEXIT
exit code or exit parameters fails.
The VMGEXIT instruction can be issued from userspace, even though
userspace (likely) can't update the GHCB. To prevent userspace from being
able to kill the guest, return an error through the GHCB when validation
fails rather than terminating the guest. For cases where the GHCB can't be
updated (e.g. the GHCB can't be mapped, etc.), just return back to the
guest.
The new error codes are documented in the lasest update to the GHCB
specification.
Fixes: 291bd20d5d88 ("KVM: SVM: Add initial support for a VMGEXIT VMEXIT")
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Message-Id: <b57280b5562893e2616257ac9c2d4525a9aeeb42.1638471124.git.thomas.lendacky@amd.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'sound/soc/tegra/tegra210_sfc.h')
0 files changed, 0 insertions, 0 deletions