qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Andrey Korolyov <andrey@xdel.ru>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Memory hotplug and ancient kernels
Date: Wed, 8 Oct 2014 14:28:41 +0200	[thread overview]
Message-ID: <20141008142841.71d3ad6d@nial.usersys.redhat.com> (raw)
In-Reply-To: <CABYiri_Fs9mNvYRiKzCjNTFFvS_ibLvL41_aKJxiKmNV5KCg3Q@mail.gmail.com>

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.
> 

      reply	other threads:[~2014-10-08 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-02 14:38 [Qemu-devel] Memory hotplug and ancient kernels Andrey Korolyov
2014-10-08 12:28 ` Igor Mammedov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141008142841.71d3ad6d@nial.usersys.redhat.com \
    --to=imammedo@redhat.com \
    --cc=andrey@xdel.ru \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).