Hi Peter, On 24/8/26 12:28, Peter Maydell wrote:
The GICv5 allocates memory and creates hashtables during realize and as part of its operation. Free those resources in finalize.
Why not in unrealize() path?
Since the GICv5 is created at QEMU startup and remains in existence for the lifetime of the process, this isn't an in-practice leak, only a theoretical one. Signed-off-by: Peter Maydell <[email protected]> --- hw/intc/arm_gicv5.c | 11 +++++++++++ hw/intc/arm_gicv5_common.c | 3 +++ 2 files changed, 14 insertions(+)
