mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-03 15:53:54 -06:00
memory: convert memory_region_destroy to object_unparent
Explicitly call object_unparent in the few places where we will re-create the memory region. If the memory region is simply being destroyed as part of device teardown, let QOM handle it. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
parent
e3fb0ade83
commit
d8d9581460
9 changed files with 18 additions and 14 deletions
|
@ -74,11 +74,16 @@ Region lifecycle
|
|||
----------------
|
||||
|
||||
A region is created by one of the constructor functions (memory_region_init*())
|
||||
and destroyed by the destructor (memory_region_destroy()). In between,
|
||||
a region can be added to an address space by using memory_region_add_subregion()
|
||||
and removed using memory_region_del_subregion(). Region attributes may be
|
||||
changed at any point; they take effect once the region becomes exposed to the
|
||||
guest.
|
||||
and attached to an object. It is then destroyed by object_unparent() or simply
|
||||
when the parent object dies.
|
||||
|
||||
In between, a region can be added to an address space
|
||||
by using memory_region_add_subregion() and removed using
|
||||
memory_region_del_subregion(). Destroying the region implicitly
|
||||
removes the region from the address space.
|
||||
|
||||
Region attributes may be changed at any point; they take effect once
|
||||
the region becomes exposed to the guest.
|
||||
|
||||
Overlapping regions and priority
|
||||
--------------------------------
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue