| commit | 09d98b69804cfd9eccadb97951e8df64ada3bc7a | |
| author | Thomas Huth <thuth@redhat.com> | |
| Thu, 19 Jul 2018 13:02:00 +0000 (19 15:02 +0200) | ||
| committer | Peter Maydell <peter.maydell@linaro.org> | |
| Mon, 6 Aug 2018 18:07:21 +0000 (6 19:07 +0100) | ||
| tree | 69690a7393ffb050644cd79e2bb2e21181d80999 | treesnapshot (tar.gz zip) |
| parent | 341823c172168a6d2765937aaea635f5136c5aa9 | commitdiff |
target/xtensa/cpu: Set owner of memory region in xtensa_cpu_initfn
The instance_init function of the xtensa CPUs creates a memory region,
but does not set an owner, so the memory region is not destroyed
correctly when the CPU object is removed. This can happen when
introspecting the CPU devices, so introspecting the CPU device will
leave a dangling memory region object in the QOM tree. Make sure to
set the right owner here to fix this issue.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Acked-by: Max Filippov <jcmvbkbc@gmail.com>
Message-id: 1532005320-17794-1-git-send-email-thuth@redhat.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
The instance_init function of the xtensa CPUs creates a memory region,
but does not set an owner, so the memory region is not destroyed
correctly when the CPU object is removed. This can happen when
introspecting the CPU devices, so introspecting the CPU device will
leave a dangling memory region object in the QOM tree. Make sure to
set the right owner here to fix this issue.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Acked-by: Max Filippov <jcmvbkbc@gmail.com>
Message-id: 1532005320-17794-1-git-send-email-thuth@redhat.com
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
| target/xtensa/cpu.c | diffblobblamehistory |