From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37474) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsjE6-0006ap-Vo for qemu-devel@nongnu.org; Tue, 08 Jan 2013 19:09:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TsjE5-0005Xv-MV for qemu-devel@nongnu.org; Tue, 08 Jan 2013 19:09:02 -0500 Received: from cantor2.suse.de ([195.135.220.15]:52008 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TsjE5-0005Xn-Fz for qemu-devel@nongnu.org; Tue, 08 Jan 2013 19:09:01 -0500 Message-ID: <50ECB514.1020508@suse.de> Date: Wed, 09 Jan 2013 01:08:52 +0100 From: =?ISO-8859-15?Q?Andreas_F=E4rber?= 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-15 Content-Transfer-Encoding: quoted-printable 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 , Anthony Liguori , Paolo Bonzini Cc: pingfank@linux.vnet.ibm.com, Eduardo Habkost , gleb@redhat.com, stefanha@gmail.com, jbaron@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, blauwirbel@gmail.com, kevin@koconnor.net, kraxel@redhat.com, Igor Mammedov Am 18.12.2012 13:41, schrieb Vasilis Liaskovitis: > Because dimm layout needs to be configured on machine-boot, all dimm de= vices > need to be specified on startup command line (either with populated=3Do= n or with > populated=3Doff). The dimm information is stored in dimm configuration = structures. >=20 > After machine startup, dimms are hot-added or removed with normal devic= e_add > and device_del operations e.g.: > Hot-add syntax: "device_add dimm,id=3Dmydimm0,bus=3Dmembus.0" > Hot-remove syntax: "device_del dimm,id=3Dmydimm0" This sounds contradictory: Either all devices need to be specified on the command line, or they can be hot-added via monitor. Assuming a fixed layout at startup, I wonder if there is another clever way to model this... For CPU hotplug Anthony had suggested to have a fixed set of link properties that get set to a CPU socket as needed. Might a similar strategy work for memory, i.e. a startup-configured amount of links on /machine/dimm[n] that point to a QOM DIMM object or NULL if unpopulated? Hot(un)plug would then simply work via QMP qom-set command. (CC'ing some people) Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg