aboutsummaryrefslogtreecommitdiff
path: root/default-configs/or32-linux-user.mak
diff options
context:
space:
mode:
authorIgor Mammedov <imammedo@redhat.com>2013-04-05 16:36:54 +0200
committerAndreas Färber <afaerber@suse.de>2013-04-16 01:19:46 +0200
commitd3c64d6a1874f94246af91963927fb4d924332f1 (patch)
tree8d96b8839dcfa2eb87375b4b41f1e4fa1090c64b /default-configs/or32-linux-user.mak
parent4dc1f449ab22bb79ea3894bd90b154c30d73573e (diff)
target-i386: Split APIC creation from initialization in x86_cpu_realizefn()
When APIC is hotplugged during CPU hotplug, device_set_realized() calls device_reset() on it. And if QEMU runs in KVM mode, following call chain will fail: apic_reset_common() -> kvm_apic_vapic_base_update() -> kvm_vcpu_ioctl(cpu->kvm_fd,...) due to cpu->kvm_fd not being initialized yet. cpu->kvm_fd is initialized during qemu_init_vcpu() but x86_cpu_apic_init() can't be moved after it because kvm_init_vcpu() -> kvm_arch_reset_vcpu() relies on APIC to determine if CPU is BSP for setting initial env->mp_state. So split APIC device creation from its initialization and realize APIC after CPU is created, when it's safe to call APIC's reset method. Signed-off-by: Igor Mammedov <imammedo@redhat.com> Reviewed-by: liguang <lig.fnst@cn.fujitsu.com> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com> Signed-off-by: Andreas Färber <afaerber@suse.de>
Diffstat (limited to 'default-configs/or32-linux-user.mak')
0 files changed, 0 insertions, 0 deletions