From 4c055ab54fae39b6329c57bcb5334d59b920463e Mon Sep 17 00:00:00 2001 From: Gu Zheng Date: Thu, 12 May 2016 09:18:13 +0530 Subject: cpu: Reclaim vCPU objects In order to deal well with the kvm vcpus (which can not be removed without any protection), we do not close KVM vcpu fd, just record and mark it as stopped into a list, so that we can reuse it for the appending cpu hot-add request if possible. It is also the approach that kvm guys suggested: https://www.mail-archive.com/kvm@vger.kernel.org/msg102839.html Signed-off-by: Chen Fan Signed-off-by: Gu Zheng Signed-off-by: Zhu Guihua Signed-off-by: Bharata B Rao [- Explicit CPU_REMOVE() from qemu_kvm/tcg_destroy_vcpu() isn't needed as it is done from cpu_exec_exit() - Use iothread mutex instead of global mutex during destroy - Don't cleanup vCPU object from vCPU thread context but leave it to the callers (device_add/device_del)] Reviewed-by: Thomas Huth Reviewed-by: David Gibson Signed-off-by: David Gibson --- kvm-stub.c | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'kvm-stub.c') diff --git a/kvm-stub.c b/kvm-stub.c index 63735a872a..07c09d1141 100644 --- a/kvm-stub.c +++ b/kvm-stub.c @@ -32,6 +32,11 @@ bool kvm_allowed; bool kvm_readonly_mem_allowed; bool kvm_ioeventfd_any_length_allowed; +int kvm_destroy_vcpu(CPUState *cpu) +{ + return -ENOSYS; +} + int kvm_init_vcpu(CPUState *cpu) { return -ENOSYS; -- cgit v1.2.3-55-g7522