Re: [Qemu-devel] [RFC 0/7+1] QEMU APIC ID + topology bug + CPU hotplug

2012-07-12 Thread Gleb Natapov
On Thu, Jul 12, 2012 at 03:51:48PM +0200, Igor Mammedov wrote: > On 07/10/2012 10:22 PM, Eduardo Habkost wrote: > >The hotplug case is a bit more complex: we need to either: > > - have a mechanism to let the ACPI SSDT code know what's the APIC ID of > >hotplugged CPUs; or > > - make Seabios r

Re: [Qemu-devel] [RFC 0/7+1] QEMU APIC ID + topology bug + CPU hotplug

2012-07-12 Thread Igor Mammedov
On 07/10/2012 10:22 PM, Eduardo Habkost wrote: The hotplug case is a bit more complex: we need to either: - have a mechanism to let the ACPI SSDT code know what's the APIC ID of hotplugged CPUs; or - make Seabios run some code in the hotplugged CPU (I am assuming that this is simply n

[Qemu-devel] [RFC 0/7+1] QEMU APIC ID + topology bug + CPU hotplug

2012-07-10 Thread Eduardo Habkost
Hi, This is more a call for discussion than a request for comments in the actual code. Our problem today is: - Lots of QEMU and Seabios code have the assumption that Initial APIC ID == CPU "index" (in other words, that APIC IDs are always contiguous and start at 0); - However, the Initia