From: Peter Maydell <peter.maydell@linaro.org>
To: Pan Nengyuan <pannengyuan@huawei.com>
Cc: Euler Robot <euler.robot@huawei.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [PATCH v3 0/6] delay timer_new from init to realize to fix memleaks.
Date: Mon, 2 Mar 2020 13:21:58 +0000 [thread overview]
Message-ID: <CAFEAcA9stgfbRGdn0x2q38vVS9NDyysW656+XkjfyVui3OXXQw@mail.gmail.com> (raw)
In-Reply-To: <20200227025055.14341-1-pannengyuan@huawei.com>
On Thu, 27 Feb 2020 at 02:35, Pan Nengyuan <pannengyuan@huawei.com> wrote:
>
> This series delay timer_new from init into realize to avoid memleaks when we call 'device_list_properties'.
> And do timer_free only in s390x_cpu_finalize because it's hotplugable. However, It's not valid in mos6522
> if we move timer_new from init to realize, because it's never called at all. So we also add calls to mos6522_realize()
> in mac_via_realize to make this move to be valid.
>
> v1:
> - Delay timer_new() from init() to realize() to fix memleaks.
> v2:
> - Similarly to other cleanups, move timer_new into realize in target/s390x/cpu.c (Suggested by Philippe Mathieu-Daudé).
> - Send these two patches as a series instead of send each as a single patch but with wrong subject in v1.
> v3:
> - It's not valid in mos6522 if we move timer_new from init to realize, because it's never called at all.
> Thus, we remove null check in reset, and add calls to mos6522_realize() in mac_via_realize to make this move to be valid.
> - split patch by device to make it more clear.
Hi; I've applied patches 2, 3, 4 and 6 to target-arm.next,
since I think those ones are OK and they're all arm related.
You've already got review comment for patch 1 (s390)
and 5 (m68k mac_via/mos6522).
thanks
-- PMM
next prev parent reply other threads:[~2020-03-02 13:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 2:50 [PATCH v3 0/6] delay timer_new from init to realize to fix memleaks Pan Nengyuan
2020-02-27 2:50 ` [PATCH v3 1/6] s390x: fix memleaks in cpu_finalize Pan Nengyuan
2020-02-27 8:41 ` David Hildenbrand
2020-02-27 8:55 ` Philippe Mathieu-Daudé
2020-02-27 9:06 ` David Hildenbrand
2020-02-27 8:58 ` Pan Nengyuan
2020-02-27 9:04 ` David Hildenbrand
2020-02-27 9:15 ` Pan Nengyuan
2020-02-27 11:06 ` Cornelia Huck
2020-02-27 11:25 ` Pan Nengyuan
2020-03-02 14:34 ` Stefan Hajnoczi
2020-03-03 1:39 ` Pan Nengyuan
2020-02-27 2:50 ` [PATCH v3 2/6] hw/arm/pxa2xx: move timer_new from init() into realize() to avoid memleaks Pan Nengyuan
2020-02-27 2:50 ` [PATCH v3 3/6] hw/arm/spitz: " Pan Nengyuan
2020-02-27 2:50 ` [PATCH v3 4/6] hw/arm/strongarm: " Pan Nengyuan
2020-02-27 2:50 ` [PATCH v3 5/6] hw/misc/mos6522: " Pan Nengyuan
2020-03-02 13:21 ` Peter Maydell
2020-03-02 19:17 ` Mark Cave-Ayland
2020-03-03 1:36 ` Pan Nengyuan
2020-03-04 20:40 ` Mark Cave-Ayland
2020-02-27 2:50 ` [PATCH v3 6/6] hw/timer/cadence_ttc: " Pan Nengyuan
2020-02-27 6:33 ` Alistair Francis
2020-03-02 13:21 ` Peter Maydell [this message]
2020-03-03 1:26 ` [PATCH v3 0/6] delay timer_new from init to realize to fix memleaks Pan Nengyuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFEAcA9stgfbRGdn0x2q38vVS9NDyysW656+XkjfyVui3OXXQw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=euler.robot@huawei.com \
--cc=pannengyuan@huawei.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).