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>
Showing
- docs/memory.txt 10 additions, 5 deletionsdocs/memory.txt
- hw/display/vga.c 1 addition, 1 deletionhw/display/vga.c
- hw/i386/kvmvapic.c 1 addition, 1 deletionhw/i386/kvmvapic.c
- hw/mips/gt64xxx_pci.c 1 addition, 1 deletionhw/mips/gt64xxx_pci.c
- hw/misc/omap_gpmc.c 1 addition, 1 deletionhw/misc/omap_gpmc.c
- hw/misc/vfio.c 2 additions, 2 deletionshw/misc/vfio.c
- hw/ppc/ppc4xx_devs.c 1 addition, 1 deletionhw/ppc/ppc4xx_devs.c
- ioport.c 1 addition, 1 deletionioport.c
- memory.c 0 additions, 1 deletionmemory.c
Loading
Please register or sign in to comment