diff options
| author | Tom Lendacky <thomas.lendacky@amd.com> | 2020-12-10 11:10:08 -0600 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2020-12-15 05:20:59 -0500 |
| commit | 16809ecdc1e8ab7278f1d60021ac809edd17d060 (patch) | |
| tree | ac996579409605ab784a82b13839c39226ac8664 /kernel/sched/cpufreq.c | |
| parent | 861377730aa9db4cbaa0f3bd3f4d295c152732c4 (diff) | |
| download | linux-16809ecdc1e8ab7278f1d60021ac809edd17d060.tar.bz2 | |
KVM: SVM: Provide an updated VMRUN invocation for SEV-ES guests
The run sequence is different for an SEV-ES guest compared to a legacy or
even an SEV guest. The guest vCPU register state of an SEV-ES guest will
be restored on VMRUN and saved on VMEXIT. There is no need to restore the
guest registers directly and through VMLOAD before VMRUN and no need to
save the guest registers directly and through VMSAVE on VMEXIT.
Update the svm_vcpu_run() function to skip register state saving and
restoring and provide an alternative function for running an SEV-ES guest
in vmenter.S
Additionally, certain host state is restored across an SEV-ES VMRUN. As
a result certain register states are not required to be restored upon
VMEXIT (e.g. FS, GS, etc.), so only do that if the guest is not an SEV-ES
guest.
Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Message-Id: <fb1c66d32f2194e171b95fc1a8affd6d326e10c1.1607620209.git.thomas.lendacky@amd.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'kernel/sched/cpufreq.c')
0 files changed, 0 insertions, 0 deletions