diff options
author | Jan Kiszka <jan.kiszka@siemens.com> | 2013-07-02 16:51:15 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-02-02 16:55:10 +0100 |
commit | b476c99d01519277e3494a10dc0329d07157ae02 (patch) | |
tree | b4ee6cc166ae5231acf5a979288e11191f82888d /memory.c | |
parent | 26387f86c9d6ac3a7a93b76108c502646afb6c25 (diff) | |
download | qemu-b476c99d01519277e3494a10dc0329d07157ae02.zip qemu-b476c99d01519277e3494a10dc0329d07157ae02.tar.gz qemu-b476c99d01519277e3494a10dc0329d07157ae02.tar.bz2 |
memory: remove assertion on memory_region_destroy
Now that memory_region_destroy can be called from an RCU callback,
checking the BQL-protected global memory_region_transaction_depth
does not make much sense.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'memory.c')
-rw-r--r-- | memory.c | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -1263,7 +1263,6 @@ static void memory_region_finalize(Object *obj) MemoryRegion *mr = MEMORY_REGION(obj); assert(QTAILQ_EMPTY(&mr->subregions)); - assert(memory_region_transaction_depth == 0); mr->destructor(mr); memory_region_clear_coalescing(mr); g_free((char *)mr->name); |