aboutsummaryrefslogtreecommitdiff
path: root/target/ppc
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 /target/ppc
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 'target/ppc')
-rw-r--r--target/ppc/kvm.c5
1 files changed, 0 insertions, 5 deletions
diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
index 8231feb..63930d4 100644
--- a/target/ppc/kvm.c
+++ b/target/ppc/kvm.c
@@ -2956,11 +2956,6 @@ void kvmppc_set_reg_tb_offset(PowerPCCPU *cpu, int64_t tb_offset)
}
}
-bool kvm_arch_cpu_check_are_resettable(void)
-{
- return true;
-}
-
void kvm_arch_accel_class_init(ObjectClass *oc)
{
}