From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVFOQ-0008Jw-Oj for qemu-devel@nongnu.org; Wed, 02 Apr 2014 03:15:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVFOK-0003Z4-Cl for qemu-devel@nongnu.org; Wed, 02 Apr 2014 03:15:26 -0400 Received: from [59.151.112.132] (port=63399 helo=heian.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVFOJ-0003D9-VS for qemu-devel@nongnu.org; Wed, 02 Apr 2014 03:15:20 -0400 From: Hu Tao Date: Wed, 2 Apr 2014 15:13:25 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain Subject: [Qemu-devel] [PATCH 0/2] unset RAMBlock idstr when unregistering List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Igor Mammedov , Paolo Bonzini 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