On Sun, 25 Jan 2026 at 18:36, BALATON Zoltan <[email protected]> wrote: > > Our documentation says that memory regions are automatically freed > when the owner dies and the reference counting to do this is also > implemented. However this relies on the QOM free funtion that can only > be set by creating objects with object_new but memory API only > provides constructors that call object_initialize which clears the > free function that prevents QOM to manage the memory region lifetime. > Implement corresponding memory_region_new_* functions that do the same > as the memory_region_init_* functions but create the memory region > with object_new so the lifetime can be automatically managed by QOM as > documented. The memory_region_init functions are kept because they are > useful for memory regions embedded in other object or managed > externally and not by QOM for some reason.
If we have a problem with embedded MemoryRegions being leaked, we need to fix that. I'm very reluctant to create a whole new set of APIs which handles MRs in a non-standard way (i.e. "QOM object has a pointer to MR rather than embedding it") and leaves the existing ones alone. QEMU already has way too many situations where we have multiple different APIs that can be used to do something and incomplete transitions from the old one to the new one. thanks -- PMM
