Re: [RFC PATCH] linux-user: un-parent OBJECT(cpu) when closing thread

2022-06-23 Thread Laurent Vivier
On 21/06/2022 20:17, Laurent Vivier wrote: Le 10/06/2022 à 16:38, Alex Bennée a écrit : While forcing the CPU to unrealize by hand does trigger the clean-up code we never fully free resources because refcount never reaches zero. This is because QOM automatically added objects without an explicit

Re: [RFC PATCH] linux-user: un-parent OBJECT(cpu) when closing thread

2022-06-21 Thread Laurent Vivier
Le 10/06/2022 à 16:38, Alex Bennée a écrit : While forcing the CPU to unrealize by hand does trigger the clean-up code we never fully free resources because refcount never reaches zero. This is because QOM automatically added objects without an explicit parent to /unattached/, incrementing the re

Re: [RFC PATCH] linux-user: un-parent OBJECT(cpu) when closing thread

2022-06-12 Thread Laurent Vivier
Le 10/06/2022 à 16:38, Alex Bennée a écrit : While forcing the CPU to unrealize by hand does trigger the clean-up code we never fully free resources because refcount never reaches zero. This is because QOM automatically added objects without an explicit parent to /unattached/, incrementing the re

[RFC PATCH] linux-user: un-parent OBJECT(cpu) when closing thread

2022-06-10 Thread Alex Bennée
While forcing the CPU to unrealize by hand does trigger the clean-up code we never fully free resources because refcount never reaches zero. This is because QOM automatically added objects without an explicit parent to /unattached/, incrementing the refcount. Instead of manually triggering unreali