diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2024-03-18 14:41:33 -0400 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-04-23 17:35:25 +0200 |
| commit | a99c0c66ebe7d8db3af6f16689ade9375247e43e (patch) | |
| tree | f98b185a2212469c16c1a64fd42831a1e3f74184 /target/i386 | |
| parent | 5c3131c392f84c660033d511ec39872d8beb4b1e (diff) | |
| download | qemu-a99c0c66ebe7d8db3af6f16689ade9375247e43e.zip qemu-a99c0c66ebe7d8db3af6f16689ade9375247e43e.tar.gz qemu-a99c0c66ebe7d8db3af6f16689ade9375247e43e.tar.bz2 | |
KVM: remove kvm_arch_cpu_check_are_resettable
Board reset requires writing a fresh CPU state. As far as KVM is
concerned, the only thing that blocks reset is that CPU state is
encrypted; therefore, kvm_cpus_are_resettable() can simply check
if that is the case.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'target/i386')
| -rw-r--r-- | target/i386/kvm/kvm.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/target/i386/kvm/kvm.c b/target/i386/kvm/kvm.c index c64b956..c8fdab4 100644 --- a/target/i386/kvm/kvm.c +++ b/target/i386/kvm/kvm.c @@ -5619,11 +5619,6 @@ bool kvm_has_waitpkg(void) return has_msr_umwait; } -bool kvm_arch_cpu_check_are_resettable(void) -{ - return !sev_es_enabled(); -} - #define ARCH_REQ_XCOMP_GUEST_PERM 0x1025 void kvm_request_xsave_components(X86CPU *cpu, uint64_t mask) |