From: Laurent Vivier <laurent@vivier.eu>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] linux-user: un-parent OBJECT(cpu) when closing thread
Date: Wed, 25 Jan 2023 14:20:04 +0100 [thread overview]
Message-ID: <14ec347c-1551-12e9-344c-78442c30e405@vivier.eu> (raw)
In-Reply-To: <20230124201019.3935934-1-richard.henderson@linaro.org>
Le 24/01/2023 à 21:10, Richard Henderson a écrit :
> This reinstates commit 52f0c1607671293afcdb2acc2f83e9bccbfa74bb:
>
> While forcing the CPU to unrealize by hand does trigger the clean-up
> code we never fully free resources because refcount never reaches
> zero. This is because QOM automatically added objects without an
> explicit parent to /unattached/, incrementing the refcount.
>
> Instead of manually triggering unrealization just unparent the object
> and let the device machinery deal with that for us.
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/866
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> Message-Id: <20220811151413.3350684-2-alex.bennee@linaro.org>
>
> The original patch tickled a problem in target/arm, and was reverted.
> But that problem is fixed as of commit 3b07a936d3bf.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> linux-user/syscall.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 1f8c10f8ef..4ca1b59343 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -8642,7 +8642,13 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
> if (CPU_NEXT(first_cpu)) {
> TaskState *ts = cpu->opaque;
>
> - object_property_set_bool(OBJECT(cpu), "realized", false, NULL);
> + if (ts->child_tidptr) {
> + put_user_u32(0, ts->child_tidptr);
> + do_sys_futex(g2h(cpu, ts->child_tidptr),
> + FUTEX_WAKE, INT_MAX, NULL, NULL, 0);
> + }
> +
> + object_unparent(OBJECT(cpu));
> object_unref(OBJECT(cpu));
> /*
> * At this point the CPU should be unrealized and removed
> @@ -8652,11 +8658,6 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
>
> pthread_mutex_unlock(&clone_lock);
>
> - if (ts->child_tidptr) {
> - put_user_u32(0, ts->child_tidptr);
> - do_sys_futex(g2h(cpu, ts->child_tidptr),
> - FUTEX_WAKE, INT_MAX, NULL, NULL, 0);
> - }
> thread_cpu = NULL;
> g_free(ts);
> rcu_unregister_thread();
Applied to my linux-user-for-8.0 branch.
Thanks,
Laurent
prev parent reply other threads:[~2023-01-25 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:10 [PATCH] linux-user: un-parent OBJECT(cpu) when closing thread Richard Henderson
2023-01-25 13:20 ` Laurent Vivier [this message]
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=14ec347c-1551-12e9-344c-78442c30e405@vivier.eu \
--to=laurent@vivier.eu \
--cc=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).