From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42397)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1XbqMO-0006Mp-9N
	for qemu-devel@nongnu.org; Wed, 08 Oct 2014 08:28:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1XbqMJ-00023W-6j
	for qemu-devel@nongnu.org; Wed, 08 Oct 2014 08:28:52 -0400
Received: from mx1.redhat.com ([209.132.183.28]:6233)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <imammedo@redhat.com>) id 1XbqMI-00023O-Ud
	for qemu-devel@nongnu.org; Wed, 08 Oct 2014 08:28:47 -0400
Date: Wed, 8 Oct 2014 14:28:41 +0200
From: Igor Mammedov <imammedo@redhat.com>
Message-ID: <20141008142841.71d3ad6d@nial.usersys.redhat.com>
In-Reply-To: <CABYiri_Fs9mNvYRiKzCjNTFFvS_ibLvL41_aKJxiKmNV5KCg3Q@mail.gmail.com>
References: <CABYiri_Fs9mNvYRiKzCjNTFFvS_ibLvL41_aKJxiKmNV5KCg3Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Memory hotplug and ancient kernels
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: Andrey Korolyov <andrey@xdel.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Thu, 2 Oct 2014 18:38:33 +0400
Andrey Korolyov <andrey@xdel.ru> wrote:

> Hi,
> 
> with kernel with an obsolete version (< 3.8) DIMM configuration is not
> working as defined in a boot-up values, though it is possible to add
> dimm during runtime and it will be recognized just well. ACPI tables
> and the of DMI for kernels which are recognizing on-boot modules and
> for ones which are not are the same and I am barely remembering that
> some changes related to memory hotplug mechanism was landed in 3.8.
> 
> Given following configuration, dimm2 is plugged during current boot
> cycle of Centos 2.6.32 kernel:
> 
> '{ "execute": "query-memory-devices"}'
> {"return":[{"type":"dimm","data":{"memdev":"/objects/mem0","hotplugged":false,"addr":4294967296,"hotpluggable":true,"size":134217728,"slot":0,"node":0,"id":"dimm0"}},{"type":"dimm","data":{"memdev":"/objects/mem1","hotplugged":true,"addr":4429185024,"hotpluggable":true,"size":134217728,"slot":1,"node":0,"id":"dimm1"}},{"type":"dimm","data":{"memdev":"/objects/mem2","hotplugged":true,"addr":4563402752,"hotpluggable":true,"size":134217728,"slot":2,"node":0,"id":"dimm2"}}],"id":"libvirt-16"}
> 
> Hotplug Mem Device
> init_memory_mapping: 0000000110000000-0000000118000000
>  0110000000 - 0118000000 page 2M
>  [ffffea0003b80000-ffffea0003d7ffff] PMD ->
> [ffff88001d600000-ffff88001d7fffff] on node 0
> Built 1 zonelists in Node order, mobility grouping on.  Total pages: 160734
> Policy zone: Normal
> 
> ls /sys/devices/system/memory/| grep mem
> memory0
> memory1
> memory2
> memory3
> memory34
Looks like a bug. I've just opened RHBZ 1150510 for tracking it.

> 
> ..Rebooting to 3.10..
> 
> ls /sys/devices/system/memory/| grep mem
> memory0
> memory1
> memory2
> memory3
> memory32
> memory33
> memory34
> 
> The results are based on tag-2.1.2 without any modifications.
>