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>,
Laurent Vivier <laurent@vivier.eu>,
QEMU Developers <qemu-devel@nongnu.org>,
zhanghailiang <zhang.zhanghailiang@huawei.com>
Subject: Re: [PATCH v3 5/6] hw/misc/mos6522: move timer_new from init() into realize() to avoid memleaks
Date: Mon, 2 Mar 2020 13:21:32 +0000 [thread overview]
Message-ID: <CAFEAcA8yvrYrBONtW46iswbEvMF-WC-j7fHOOfcoEC_RV66BkQ@mail.gmail.com> (raw)
In-Reply-To: <20200227025055.14341-6-pannengyuan@huawei.com>
On Thu, 27 Feb 2020 at 02:35, Pan Nengyuan <pannengyuan@huawei.com> wrote:
>
> There are some memleaks when we call 'device_list_properties'. This patch move timer_new from init into realize to fix it.
> Meanwhile, add calls to mos6522_realize() in mac_via_realize to make this move to be valid.
>
> Reported-by: Euler Robot <euler.robot@huawei.com>
> Signed-off-by: Pan Nengyuan <pannengyuan@huawei.com>
> ---
> Cc: Laurent Vivier <laurent@vivier.eu>
> ---
> v2->v1:
> - no changes in this patch.
> v3->v2:
> - remove null check in reset, and add calls to mos6522_realize() in mac_via_realize to make this move to be valid.
Hi; this is really fixing two bugs in one patch:
> ---
> hw/misc/mac_via.c | 5 +++++
> hw/misc/mos6522.c | 6 ++++++
> 2 files changed, 11 insertions(+)
>
> diff --git a/hw/misc/mac_via.c b/hw/misc/mac_via.c
> index b7d0012794..1d72d4ef35 100644
> --- a/hw/misc/mac_via.c
> +++ b/hw/misc/mac_via.c
> @@ -879,6 +879,11 @@ static void mac_via_realize(DeviceState *dev, Error **errp)
> sysbus_init_child_obj(OBJECT(dev), "via2", &m->mos6522_via2,
> sizeof(m->mos6522_via2), TYPE_MOS6522_Q800_VIA2);
>
> + object_property_set_bool(OBJECT(&m->mos6522_via1), true, "realized",
> + &error_abort);
> + object_property_set_bool(OBJECT(&m->mos6522_via2), true, "realized",
> + &error_abort);
> +
> /* Pass through mos6522 output IRQs */
> ms = MOS6522(&m->mos6522_via1);
> object_property_add_alias(OBJECT(dev), "irq[0]", OBJECT(ms),
This is fixing a bug in mac_via where it failed to actually
realize devices it was using. That's a dependency for the bug
you're trying to fix, but it's a separate one and should be
in its own patch.
You also want to pass the error back up to the caller, rather
than using error_abort. To do that, at the top of the function:
Error *err = NULL;
and then here you can do:
object_property_set_bool(OBJECT(&m->mos6522_via1), true, "realized", &err);
if (err) {
error_propagate(errp, err);
return;
}
The existing code which inits the mos6522 objects and
calls object_property_add_alias on them which is in
the mac_via realize function should be moved to the init
function. (init should init child objects and set up
properties; realize should realize them.)
This is all fixing the incorrect creation of the mos6522
devices in mac_via (which has been wrong since the mac_via
was first added in commit 6dca62a0000f9), so that can all
be one patch I think.
> +static void mos6522_realize(DeviceState *dev, Error **errp)
> +{
> + MOS6522State *s = MOS6522(dev);
>
> s->timers[0].timer = timer_new_ns(QEMU_CLOCK_VIRTUAL, mos6522_timer1, s);
> s->timers[1].timer = timer_new_ns(QEMU_CLOCK_VIRTUAL, mos6522_timer2, s);
> @@ -502,6 +507,7 @@ static void mos6522_class_init(ObjectClass *oc, void *data)
>
> dc->reset = mos6522_reset;
> dc->vmsd = &vmstate_mos6522;
> + dc->realize = mos6522_realize;
> device_class_set_props(dc, mos6522_properties);
> mdc->parent_reset = dc->reset;
> mdc->set_sr_int = mos6522_set_sr_int;
The changes to hw/misc/mos_6522.c are good, but should be in
their own patch.
thanks
-- PMM
next prev parent reply other threads:[~2020-03-02 13:22 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 [this message]
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 ` [PATCH v3 0/6] delay timer_new from init to realize to fix memleaks Peter Maydell
2020-03-03 1:26 ` 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=CAFEAcA8yvrYrBONtW46iswbEvMF-WC-j7fHOOfcoEC_RV66BkQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=euler.robot@huawei.com \
--cc=laurent@vivier.eu \
--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).