- Original Message -
> From: "Anthony Xu"
> To: "Paolo Bonzini" , "Yang Zhong"
> , qemu-devel@nongnu.org
> Cc: "Chao P Peng"
> Sent: Friday, March 10, 2017 8:30:06 PM
> Subject: RE: [PATCH v1 1/2]
> > Ideally, freeing QOM object should not require a global lock.
> > If you see any other QOM requiring a global lock, please let us know, we
> are willing to fix it.
>
> All of them. When unplugging a device, the device object will be freed
> from an RCU callback.
>
Thanks for your reply,
On 10/03/2017 17:05, Xu, Anthony wrote:
> Ideally, freeing QOM object should not require a global lock.
> If you see any other QOM requiring a global lock, please let us know, we are
> willing to fix it.
All of them. When unplugging a device, the device object will be freed
from an RCU
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Friday, March 10, 2017 12:42 AM
> To: Zhong, Yang ; qemu-devel@nongnu.org
> Cc: Xu, Anthony ; Peng, Chao P
>
> Subject: Re: [PATCH v1 1/2]
On 10/03/2017 16:14, Yang Zhong wrote:
> There are a lot of memory allocation during the qemu bootup, which are
> freed later by RCU thread,which means the heap size becomes biger and
> biger when allocation happens, but the heap may not be shrinked even
> after release happens,because some