From: Emilio Cota <cota@braap.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 1/4] cpu: free cpu->tb_jmp_cache with RCU
Date: Mon, 9 Jan 2023 16:52:42 -0500 [thread overview]
Message-ID: <Y7yMqvnshw822/01@cota-l14> (raw)
In-Reply-To: <676d74ed-cce8-8b0e-69c7-44ec25a68a4b@linaro.org>
On Sun, Jan 08, 2023 at 11:19:53 -0800, Richard Henderson wrote:
> On 1/8/23 08:39, Emilio Cota wrote:
(snip)
> > diff --git a/accel/tcg/cpu-exec.c b/accel/tcg/cpu-exec.c
> > index 356fe348de..ca95d21528 100644
> > --- a/accel/tcg/cpu-exec.c
> > +++ b/accel/tcg/cpu-exec.c
> > @@ -1070,7 +1070,6 @@ void tcg_exec_unrealizefn(CPUState *cpu)
> > #endif /* !CONFIG_USER_ONLY */
> > tlb_destroy(cpu);
> > - g_free(cpu->tb_jmp_cache);
>
> Can you simply use g_free_rcu here?
Yes, although we must have removed the CPU from the RCU list
before doing so.
> > diff --git a/cpu.c b/cpu.c
> > index 4a7d865427..564200559f 100644
> > --- a/cpu.c
> > +++ b/cpu.c
> > @@ -164,6 +164,12 @@ void cpu_exec_realizefn(CPUState *cpu, Error **errp)
> > #endif /* CONFIG_USER_ONLY */
> > }
> > +static void cpu_free_rcu(CPUState *cpu)
> > +{
> > + /* .tb_jmp_cache is NULL except under TCG */
> > + g_free(cpu->tb_jmp_cache);
> > +}
> > +
> > void cpu_exec_unrealizefn(CPUState *cpu)
> > {
> > #ifndef CONFIG_USER_ONLY
> > @@ -181,6 +187,7 @@ void cpu_exec_unrealizefn(CPUState *cpu)
> > }
> > cpu_list_remove(cpu);
> > + call_rcu(cpu, cpu_free_rcu, rcu);
>
> Certainly this seems wrong, exposing tb_jmp_cache beyond tcg.
I've changed this in v2 to call tcg_exec_unrealizefn after
cpu_list_remove.
An alternative would be to call the whole cpu_exec_unrealizefn
after an RCU grace period, but I think that might be more trouble
than it's worth.
Thanks,
Emilio
next prev parent reply other threads:[~2023-01-09 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 16:39 [PATCH 0/4] tsan fixes Emilio Cota
2023-01-08 16:39 ` [PATCH 1/4] cpu: free cpu->tb_jmp_cache with RCU Emilio Cota
2023-01-08 19:19 ` Richard Henderson
2023-01-09 21:52 ` Emilio Cota [this message]
2023-01-08 16:39 ` [PATCH 2/4] util/qht: add missing atomic_set(hashes[i]) Emilio Cota
2023-01-08 19:20 ` Richard Henderson
2023-01-08 19:54 ` Philippe Mathieu-Daudé
2023-01-08 16:39 ` [PATCH 3/4] util/qht: use striped locks under TSAN Emilio Cota
2023-01-08 19:51 ` Richard Henderson
2023-01-09 22:10 ` Emilio Cota
2023-01-08 16:39 ` [PATCH 4/4] plugins: make qemu_plugin_user_exit's locking order consistent with fork_start's Emilio Cota
2023-01-08 19:31 ` Richard Henderson
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=Y7yMqvnshw822/01@cota-l14 \
--to=cota@braap.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--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).