From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60800) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WX42o-0003Hd-9R for qemu-devel@nongnu.org; Mon, 07 Apr 2014 03:32:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WX42i-0000Pk-5M for qemu-devel@nongnu.org; Mon, 07 Apr 2014 03:32:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WX42h-0000Pc-TQ for qemu-devel@nongnu.org; Mon, 07 Apr 2014 03:32:32 -0400 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s377WUYK011893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 7 Apr 2014 03:32:30 -0400 Date: Mon, 7 Apr 2014 09:32:27 +0200 From: Igor Mammedov Message-ID: <20140407093227.3770eda6@nial.usersys.redhat.com> In-Reply-To: <20140404165727.GB6393@work-vm> References: <1396618620-27823-1-git-send-email-imammedo@redhat.com> <20140404165727.GB6393@work-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 00/35] pc: ACPI memory hotplug List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Dr. David Alan Gilbert" Cc: qemu-devel@nongnu.org On Fri, 4 Apr 2014 17:57:28 +0100 "Dr. David Alan Gilbert" wrote: > * Igor Mammedov (imammedo@redhat.com) wrote: > > > > > This series allows to hotplug 'arbitrary' DIMM devices specifying size, > > NUMA node mapping (guest side), slot and address where to map it, at runtime. > > Some high level questions: > 1) Is the intention that all guest RAM would be hot pluggable like this > (i.e. no memory would be allocated in the normal way) Later, I plan to convert initial memory to DIMM devices as well, but only to not hotpluggable ones so far for simplicity sake. > 2) Does something stop it being invoked during a migration? As far as I know, there is no checks to prevent any hotplug op during migration. Considering how migration currently works, hotplug should be disabled at migration time. > > Dave > -- > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK