aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2024-03-18 14:41:33 -0400
committerPaolo Bonzini <pbonzini@redhat.com>2024-04-23 17:35:25 +0200
commita99c0c66ebe7d8db3af6f16689ade9375247e43e (patch)
treef98b185a2212469c16c1a64fd42831a1e3f74184 /include
parent5c3131c392f84c660033d511ec39872d8beb4b1e (diff)
downloadqemu-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 'include')
-rw-r--r--include/sysemu/kvm.h10
1 files changed, 0 insertions, 10 deletions
diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
index 14b1ddb..bd247f3 100644
--- a/include/sysemu/kvm.h
+++ b/include/sysemu/kvm.h
@@ -525,16 +525,6 @@ int kvm_get_one_reg(CPUState *cs, uint64_t id, void *target);
/* Notify resamplefd for EOI of specific interrupts. */
void kvm_resample_fd_notify(int gsi);
-/**
- * kvm_cpu_check_are_resettable - return whether CPUs can be reset
- *
- * Returns: true: CPUs are resettable
- * false: CPUs are not resettable
- */
-bool kvm_cpu_check_are_resettable(void);
-
-bool kvm_arch_cpu_check_are_resettable(void);
-
bool kvm_dirty_ring_enabled(void);
uint32_t kvm_dirty_ring_size(void);