From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53077)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1VkwTl-0000Jc-G8
	for qemu-devel@nongnu.org; Mon, 25 Nov 2013 08:45:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1VkwTa-0002wT-PL
	for qemu-devel@nongnu.org; Mon, 25 Nov 2013 08:45:33 -0500
Received: from mail-yh0-x230.google.com ([2607:f8b0:4002:c01::230]:54356)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1VkwTa-0002vy-KG
	for qemu-devel@nongnu.org; Mon, 25 Nov 2013 08:45:22 -0500
Received: by mail-yh0-f48.google.com with SMTP id f73so2750808yha.35
	for <qemu-devel@nongnu.org>; Mon, 25 Nov 2013 05:45:22 -0800 (PST)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <5293546B.1060900@redhat.com>
Date: Mon, 25 Nov 2013 14:45:15 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1385001528-12003-1-git-send-email-imammedo@redhat.com>
	<1385001528-12003-14-git-send-email-imammedo@redhat.com>
	<20131121094202.GB3140@redhat.com>
	<20131121152137.6348e9b2@nial.usersys.redhat.com>
	<20131121143847.GA11741@redhat.com>
	<20131122181446.4891e953@nial.usersys.redhat.com>
	<20131124105857.GA864@redhat.com>
	<87txf1kkjo.fsf@blackfin.pond.sub.org>
In-Reply-To: <87txf1kkjo.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 13/27] acpi: memory hotplug ACPI hardware
	implementation
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: peter.maydell@linaro.org, stefanha@redhat.com, marcel.a@redhat.com, hutao@cn.fujitsu.com, stefanb@linux.vnet.ibm.com, mjt@tls.msk.ru, qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com, vasilis.liaskovitis@profitbricks.com, quintela@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>, kraxel@redhat.com, aliguori@amazon.com, Igor Mammedov <imammedo@redhat.com>, lcapitulino@redhat.com, chegu_vinod@hp.com, afaerber@suse.de

Il 25/11/2013 08:27, Markus Armbruster ha scritto:
> "Michael S. Tsirkin" <mst@redhat.com> writes:
> 
> [...]
>> Here this made me think of the following question:
>> should not memory available on boot be listed in CMOS?
>> Let's assume new BIOS gets interrupt telling it there's new memory.
>> It clears the interrupt and then system is reset.
>>
>> Will system after reset detect the new hotplugged memory?

Can it just scan all slots from MHPD._INI?

For example on reset all slots could be disabled by the
ACPIHotpluggableDimmBus (even coldplugged ones), and scanned + enabled
by ASL.

>> How?
> 
> Do physical systems with hot-pluggable memory exist?  How do they
> behave?

I guess they assume BIOS is updated in lockstep with the introduction of
the feature.

Paolo