diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2015-10-01 10:59:50 +0200 |
|---|---|---|
| committer | Markus Armbruster <armbru@redhat.com> | 2015-10-09 15:25:56 +0200 |
| commit | 2e2b8eb70fdb7dfbec39f3a19b20f9a73f2f813e (patch) | |
| tree | 96c720cace8560394fffb7e7c9d5d3d30c5c4707 /qmp.c | |
| parent | c6047e9621f77a65993bcda8f58b676996e24bb5 (diff) | |
memory: allow destroying a non-empty MemoryRegion
This is legal; the MemoryRegion will simply unreference all the
existing subregions and possibly bring them down with it as well.
However, it requires a bit of care to avoid an infinite loop.
Finalizing a memory region cannot trigger an address space update,
but memory_region_del_subregion errs on the side of caution and
might trigger a spurious update: avoid that by resetting mr->enabled
first.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-Id: <1443689999-12182-2-git-send-email-armbru@redhat.com>
Diffstat (limited to 'qmp.c')
0 files changed, 0 insertions, 0 deletions