From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42735) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SpJoE-0000xU-GT for qemu-devel@nongnu.org; Thu, 12 Jul 2012 09:52:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SpJo8-0002oD-He for qemu-devel@nongnu.org; Thu, 12 Jul 2012 09:51:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SpJo8-0002o5-A0 for qemu-devel@nongnu.org; Thu, 12 Jul 2012 09:51:52 -0400 Message-ID: <4FFED674.9090601@redhat.com> Date: Thu, 12 Jul 2012 15:51:48 +0200 From: Igor Mammedov MIME-Version: 1.0 References: <1341951743-2285-1-git-send-email-ehabkost@redhat.com> In-Reply-To: <1341951743-2285-1-git-send-email-ehabkost@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 0/7+1] QEMU APIC ID + topology bug + CPU hotplug List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Anthony Liguori , seabios@seabios.org, qemu-devel@nongnu.org, Gleb Natapov 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 not possible). If SMM is supported by qemu/kvm than it will be possible to trigger SMI from APCI method and SMI handler, that are supposed to run on all CPUs (including hot-plugged one) , could fixup APIC ID of added CPU in some memory region used by ACPI. -- ----- Igor