From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: pannengyuan@huawei.com, peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, Alistair Francis <alistair@alistair23.me>,
zhang.zhanghailiang@huawei.com,
Euler Robot <euler.robot@huawei.com>
Subject: Re: [PATCH 2/3] stm32f2xx_timer: delay timer_new to avoid memleaks
Date: Wed, 5 Feb 2020 14:17:29 +0100 [thread overview]
Message-ID: <80b6d1cb-f711-1fac-c6b4-7a60b7c9e0a0@redhat.com> (raw)
In-Reply-To: <20200205070659.22488-3-pannengyuan@huawei.com>
On 2/5/20 8:06 AM, pannengyuan@huawei.com wrote:
> From: Pan Nengyuan <pannengyuan@huawei.com>
>
> There is a memory leak when we call 'device_list_properties' with typename = stm32f2xx_timer. It's easy to reproduce as follow:
>
> virsh qemu-monitor-command vm1 --pretty '{"execute": "device-list-properties", "arguments": {"typename": "stm32f2xx_timer"}}'
>
> This patch delay timer_new to fix this memleaks.
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
> Cc: Alistair Francis <alistair@alistair23.me>
> ---
> hw/timer/stm32f2xx_timer.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/timer/stm32f2xx_timer.c b/hw/timer/stm32f2xx_timer.c
> index fb370ce0f0..06ec8a02c2 100644
> --- a/hw/timer/stm32f2xx_timer.c
> +++ b/hw/timer/stm32f2xx_timer.c
> @@ -314,7 +314,11 @@ static void stm32f2xx_timer_init(Object *obj)
> memory_region_init_io(&s->iomem, obj, &stm32f2xx_timer_ops, s,
> "stm32f2xx_timer", 0x400);
> sysbus_init_mmio(SYS_BUS_DEVICE(obj), &s->iomem);
> +}
>
> +static void stm32f2xx_timer_realize(DeviceState *dev, Error **errp)
> +{
> + STM32F2XXTimerState *s = STM32F2XXTIMER(dev);
> s->timer = timer_new_ns(QEMU_CLOCK_VIRTUAL, stm32f2xx_timer_interrupt, s);
> }
>
> @@ -325,6 +329,7 @@ static void stm32f2xx_timer_class_init(ObjectClass *klass, void *data)
> dc->reset = stm32f2xx_timer_reset;
> device_class_set_props(dc, stm32f2xx_timer_properties);
> dc->vmsd = &vmstate_stm32f2xx_timer;
> + dc->realize = stm32f2xx_timer_realize;
> }
>
> static const TypeInfo stm32f2xx_timer_info = {
>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-02-05 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 7:06 [PATCH 0/3] delay timer_new to avoid memleaks pannengyuan
2020-02-05 7:06 ` [PATCH 1/3] armv7m_systick: " pannengyuan
2020-02-05 7:06 ` [PATCH 2/3] stm32f2xx_timer: " pannengyuan
2020-02-05 13:17 ` Philippe Mathieu-Daudé [this message]
2020-02-05 18:49 ` Alistair Francis
2020-02-05 7:06 ` [PATCH 3/3] stellaris: " pannengyuan
2020-02-05 13:10 ` Philippe Mathieu-Daudé
2020-02-05 13:16 ` [PATCH 0/3] " Philippe Mathieu-Daudé
2020-02-06 1:14 ` Pan Nengyuan
2020-02-07 13:42 ` Peter Maydell
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=80b6d1cb-f711-1fac-c6b4-7a60b7c9e0a0@redhat.com \
--to=philmd@redhat.com \
--cc=alistair@alistair23.me \
--cc=euler.robot@huawei.com \
--cc=pannengyuan@huawei.com \
--cc=peter.maydell@linaro.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).