qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Korolyov <andrey@xdel.ru>
To: Igor Mammedov <imammedo@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, ehabkost@redhat.com
Subject: Re: [Qemu-devel] Runtime-modified DIMMs and live migration issue
Date: Fri, 19 Jun 2015 19:57:22 +0300	[thread overview]
Message-ID: <CABYiri-LuYsffbf2xGnp2GKc1Ax8+ZDLcPRCtYarJoAvsGPWPg@mail.gmail.com> (raw)
In-Reply-To: <CABYiri8ZmXYsjo6Y8utLAh_BQzOov_1ue6wOjjecwU8zFds5PA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

> I don`t think that it could be ACPI-related in any way, instead, it
> looks like race in vhost or simular mm-touching mechanism. The
> repeated hits you mentioned should be fixed as well indeed, but they
> can be barely the reason for this problem.

Please find a trace from a single dimm plugging in attached. The
configuration is -m 512 + three 512-Mb dimms on start, then a 512-Mb
dimm is plugged in, the NUMA topology is created with a single node0.

[-- Attachment #2: acpi-hp.txt --]
[-- Type: text/plain, Size: 2256 bytes --]

[   94.751646] 
**** Context Switch from TID 4294967295 to TID 496836688 ****

[   94.755180]     utils-0291 evaluate_integer      : Return value [15]
[   94.757146]       bus-0130 bus_get_status        : Device [MP00] status [0000000f]
[   94.760755] acpi PNP0C80:00: Already enumerated
[   94.762478]     utils-0291 evaluate_integer      : Return value [15]
[   94.767924]       bus-0130 bus_get_status        : Device [MP01] status [0000000f]
[   94.770232] acpi PNP0C80:01: Already enumerated
[   94.771766]     utils-0291 evaluate_integer      : Return value [15]
[   94.773867]       bus-0130 bus_get_status        : Device [MP02] status [0000000f]
[   94.776149] acpi PNP0C80:02: Already enumerated
[   94.777678]     utils-0291 evaluate_integer      : Return value [15]
[   94.779669]       bus-0130 bus_get_status        : Device [MP03] status [0000000f]
[   94.782686]      scan-1144 get_device_data       : No context for object [ffff88001d83fe50]
[   94.785908]      scan-1144 get_device_data       : No context for object [ffff88001d83fe28]
[   94.789194]      scan-1144 get_device_data       : No context for object [ffff88001d83fe00]
[   94.792431]      scan-1144 get_device_data       : No context for object [ffff88001d83fdd8]
[   94.795605]      scan-1144 get_device_data       : No context for object [ffff88001d83fdb0]
[   94.798956]      scan-1144 get_device_data       : No context for object [ffff88001d83fd88]
[   94.802337]     utils-0291 evaluate_integer      : Return value [15]
[   94.804961]       bus-0130 bus_get_status        : Device [MP03] status [0000000f]
[   94.807953] device_pm-0128 device_get_power      : Device [MP03] power state is D0
[   94.811318]     utils-0291 evaluate_integer      : Return value [15]
[   94.814056]     utils-0291 evaluate_integer      : Return value [0]
[   94.816629] init_memory_mapping: [mem 0x160000000-0x17fffffff]
[   94.818714]  [mem 0x160000000-0x17fffffff] page 2M
[   94.819539]  [ffffea0004c00000-ffffea0004dfffff] PMD -> [ffff88001b800000-ffff88001b9fffff] on node 0
[   94.823406]  [ffffea0004e00000-ffffea0004ffffff] PMD -> [ffff88001aa00000-ffff88001abfffff] on node 0
[   94.827062]  [ffffea0005000000-ffffea00051fffff] PMD -> [ffff880000400000-ffff8800005fffff] on node 0

  reply	other threads:[~2015-06-19 16:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 17:14 [Qemu-devel] Runtime-modified DIMMs and live migration issue Andrey Korolyov
2015-06-14 13:16 ` Andrey Korolyov
2015-06-15 11:11   ` Andrey Korolyov
2015-06-16 14:41     ` Andrey Korolyov
2015-06-17 14:52       ` Igor Mammedov
2015-06-17 15:32         ` Andrey Korolyov
2015-06-19 16:57           ` Andrey Korolyov [this message]
2015-06-19 20:02             ` Andrey Korolyov
2015-08-18 14:51               ` Andrey Korolyov
2015-09-03 19:22                 ` Andrey Korolyov

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=CABYiri-LuYsffbf2xGnp2GKc1Ax8+ZDLcPRCtYarJoAvsGPWPg@mail.gmail.com \
    --to=andrey@xdel.ru \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --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).