From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:40635) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TlE4Q-0000oe-Rt for qemu-devel@nongnu.org; Wed, 19 Dec 2012 02:28:03 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TlE4O-0000tS-ED for qemu-devel@nongnu.org; Wed, 19 Dec 2012 02:28:02 -0500 Received: from mx1.redhat.com ([209.132.183.28]:40334) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TlE4O-0000tD-6s for qemu-devel@nongnu.org; Wed, 19 Dec 2012 02:28:00 -0500 Message-ID: <50D16C68.5020800@redhat.com> Date: Wed, 19 Dec 2012 08:27:36 +0100 From: Gerd Hoffmann MIME-Version: 1.0 References: <1355834518-17989-1-git-send-email-vasilis.liaskovitis@profitbricks.com> In-Reply-To: <1355834518-17989-1-git-send-email-vasilis.liaskovitis@profitbricks.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v4 00/30] ACPI memory hotplug List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vasilis Liaskovitis Cc: pingfank@linux.vnet.ibm.com, gleb@redhat.com, stefanha@gmail.com, jbaron@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, blauwirbel@gmail.com, kevin@koconnor.net, anthony@codemonkey.ws Hi, > - multiple memory buses can be registered. Memory buses of the real hw/chipset > or a paravirtual memory bus can be added. IIRC q35 supports memory hotplug natively (picked up in some discussion). Is that correct? What does the code emulate? It doesn't look like it emulates q35 memory hotplug ... I think the paravirtual memory hotplug controller should be a PCI device (which we then can add as function to the chipset). Having some fixed magic addresses is bad. [ btw: same goes for ACPI PCI hotplug, that is hardly fixable without breaking compatibility though, for q35 we should be able to do better ]. cheers, Gerd