[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/5] hw/riscv/riscv_hart: free the harts array when the objec
Re: [PATCH 1/5] hw/riscv/riscv_hart: free the harts array when the object is finalized
Mon, 21 Feb 2022 11:29:11 +0100
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0
On 2/18/22 18:46, Peter Maydell wrote:
On Fri, 18 Feb 2022 at 17:39, Damien Hedde <firstname.lastname@example.org> wrote:
You're right. I was confused when re-writing the message.
This leaks happen on
init -> realize-failure -> finalize
Because the array is allocated, then every cpu is initialized (and an
error failure may happen for any of them).
"Failure during realize" is one of those cases I don't think we
handle very well. I'd like to see a view by one of our QOM experts
on what the best way to handle this is -- should one do the
cleanup in realize itself, or in instance_finalize? Do the
sub-objects that are being initialized and realized need to
be manually cleaned up in the realize-is-failing case, or is
that part automatic?
Which is to say that maybe this patch is the best way to do this,
but it would be nice to be sure about that...
Right now we have only 3 life cycles for coldplug (for hotplug it may be
a bit different, I don't know but that's not the case of devices in this
+ user help: init -> finalize
+ failed creation: init -> realize-failure -> finalize
+ normal cycle: init -> realize-success -> ... (maybe finalize at
I'm not even sure unrealize() is called on the normal cycle, at least it
is not done by DEVICE's finalize() method.
We could try to be clean at the end of realize failure, but anyway it's
better to free memory at the end. So we'll have to do it in finalize()
too (or in a unrealize(), if we have guarantee it will be called).
It look simplier to do it in finalize(), it catches all use cases.
Note that we also have two cases of memory allocation:
+ the allocated space hosts some children objects (like in the
riscv_array of this patch)
+ the allocated space hosts simple C things (other patches of this series)
First case is bit a tricky because obviously we cannot free a child's
memory until the child is also finalized. To answer your last question,
cleaning of a child is automatic when the reference is removed at the
beginning the finalize process of the parent.
Writing the last paragraph makes me realize we have probably no
guarantee this is the last reference (but it should). So if we want to
be sure we don't free a still-in-use memory space: we should use
object_new() instead of object_initialize_child() and let the child free
it's own memory and avoid this specific issue.
PS: Added qom maintainers/reviewers in cc.
[PATCH 2/5] target/riscv: add riscv_cpu_release_claimed_interrupts function, Damien Hedde, 2022/02/18
[PATCH 3/5] hw/intc/sifive_plic: report errors and free allocated memory, Damien Hedde, 2022/02/18
[PATCH 4/5] hw/intc/riscv_aclint: swi: report errors and free allocated memory, Damien Hedde, 2022/02/18
[PATCH 5/5] hw/intc/riscv_aclint: mtimer: report errors and free allocated memory, Damien Hedde, 2022/02/18