From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c5DP6-0002aN-Bz for qemu-devel@nongnu.org; Fri, 11 Nov 2016 10:06:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c5DP2-0000uh-Cz for qemu-devel@nongnu.org; Fri, 11 Nov 2016 10:06:08 -0500 Received: from mx1.redhat.com ([209.132.183.28]:58000) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c5DP2-0000uF-2F for qemu-devel@nongnu.org; Fri, 11 Nov 2016 10:06:04 -0500 Date: Fri, 11 Nov 2016 16:05:59 +0100 From: Igor Mammedov Message-ID: <20161111160559.2518326f@nial.brq.redhat.com> In-Reply-To: <20161111144403.GA15857@morn.lan> References: <20161111135717.18eaa6dc@nial.brq.redhat.com> <0404998c-3374-c2df-d960-596f71baac26@redhat.com> <20161111153619.3ef19ccb@nial.brq.redhat.com> <20161111144403.GA15857@morn.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] FW_CFG_NB_CPUS vs fwcfg file 'etc/boot-cpus' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin O'Connor Cc: Eduardo Habkost , mst@redhat.com, Stefan Hajnoczi , qemu-devel@nongnu.org, Gerd Hoffmann , "Jordan Justen (Intel address)" , Laszlo Ersek , Jeff Fan On Fri, 11 Nov 2016 09:44:03 -0500 "Kevin O'Connor" wrote: > On Fri, Nov 11, 2016 at 03:36:19PM +0100, Igor Mammedov wrote: > > On Fri, 11 Nov 2016 15:02:36 +0100 > > Laszlo Ersek wrote: > > > > > adding Jeff Fan and Jordan Justen > > > > > > On 11/11/16 13:57, Igor Mammedov wrote: > > > > While looking at OVMF and how it handles CPUs (ACPI/AP wakeup), > > > > I've noticed that it uses legacy FW_CFG_NB_CPUS(0x05) to get > > > > the number of present at start CPUs. > > > > > > Where exactly do you see this? > > That's the only place in OVMF, but according to google there are > > other firmwares that use FW_CFG_NB_CPUS so we are not free to remove > > it and break guests. > > > > So I'd just drop not yet released 'etc/boot-cpus', > > of cause SeaBIOS should be fixed and its blob in QEMU updated. > > I have no preference between FW_CFG_NB_CPUS and 'etc/boot-cpus'. Note > that SeaBIOS v1.10 was released with the code using 'etc/boot-cpus' > though. If it's to go away, we'll need a SeaBIOS stable branch > release with the change. Yep, we'd need a stable for that. It still probably better then keeping 2 exactly same interfaces when we have a chance to maintain only one. Without supplier of 'etc/boot-cpus' (QEMU) it will behave like it used before, i.e. hang with x2apic configuration. > > -Kevin >