From: Hu Tao <hutao@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: Igor Mammedov <imammedo@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] unset RAMBlock idstr when unregistering
Date: Wed, 2 Apr 2014 15:13:25 +0800 [thread overview]
Message-ID: <cover.1396422229.git.hutao@cn.fujitsu.com> (raw)
When hotplug an memdev that was previously plugged and unplugged,
RAMBlock idstr is not cleared and triggers an assert error in
qemu_ram_set_idstr(). This series fixes it.
Hu Tao (2):
exec: introduce qemu_ram_unset_idstr() to unset RAMBlock idstr
unset RAMBlock idstr when unregister MemoryRegion
exec.c | 26 +++++++++++++++++++++-----
include/exec/cpu-common.h | 1 +
savevm.c | 2 +-
3 files changed, 23 insertions(+), 6 deletions(-)
--
1.8.5.2.229.g4448466
next reply other threads:[~2014-04-02 7:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 7:13 Hu Tao [this message]
2014-04-02 7:13 ` [Qemu-devel] [PATCH 1/2] exec: introduce qemu_ram_unset_idstr() to unset RAMBlock idstr Hu Tao
2014-04-02 7:13 ` [Qemu-devel] [PATCH 2/2] unset RAMBlock idstr when unregister MemoryRegion Hu Tao
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=cover.1396422229.git.hutao@cn.fujitsu.com \
--to=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@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).