Re: [PATCH 1/2] util: import GTree as QTree

2023-01-29 Thread Emilio Cota
On Wed, Jan 11, 2023 at 12:08:26 +, Daniel P. Berrangé wrote: > First, I find the test to be a little unreliable the first few > times it is ran. I ran it in a loop 20 times and it got more > stable results. Looking at just the QTree lines I get something > typically like: Agreed, this is a pr

Re: [PATCH 1/2] util: import GTree as QTree

2023-01-11 Thread Daniel P . Berrangé
On Tue, Jan 10, 2023 at 10:55:35PM -0500, Emilio Cota wrote: > The only reason to add this tree is to control the memory allocator > used. Some users (e.g. TCG) cannot work reliably in multi-threaded > environments (e.g. forking in user-mode) with GTree's allocator, GSlice. > See https://gitlab.com

[PATCH 1/2] util: import GTree as QTree

2023-01-10 Thread Emilio Cota
The only reason to add this tree is to control the memory allocator used. Some users (e.g. TCG) cannot work reliably in multi-threaded environments (e.g. forking in user-mode) with GTree's allocator, GSlice. See https://gitlab.com/qemu-project/qemu/-/issues/285 for details. Importing GTree is a te