From: Marc Zyngier <maz@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>,
apatel@ventanamicro.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] risc-v: Fix order of IPI enablement vs RCU startup
Date: Mon, 03 Jul 2023 19:58:03 +0100 [thread overview]
Message-ID: <86v8f0x1ok.wl-maz@kernel.org> (raw)
In-Reply-To: <mhng-bb5689ac-5b69-423f-8ea5-42938d5bab85@palmer-ri-x1c9>
On Mon, 03 Jul 2023 19:45:43 +0100,
Palmer Dabbelt <palmer@rivosinc.com> wrote:
>
> On Mon, 03 Jul 2023 11:31:26 PDT (-0700), Marc Zyngier wrote:
> > Conor reports that risc-v tries to enable IPIs before telling the
> > core code to enable RCU. With the introduction of the mapple tree
> > as a backing store for the irq descriptors, this results in
> > a very shouty boot sequence, as RCU is legitimately upset.
> >
> > Restore some sanity by moving the risc_ipi_enable() call after
> > notify_cpu_starting(), which explicitly enables RCU on the calling
> > CPU.
> >
> > Fixes: 832f15f42646 ("RISC-V: Treat IPIs as normal Linux IRQs")
> > Reported-by: Conor Dooley <conor@kernel.org>
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Link: https://lore.kernel.org/r/20230703-dupe-frying-79ae2ccf94eb@spud
> > Cc: Anup Patel <apatel@ventanamicro.com>
> > Cc: Palmer Dabbelt <palmer@rivosinc.com>
> > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > ---
> > arch/riscv/kernel/smpboot.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/riscv/kernel/smpboot.c b/arch/riscv/kernel/smpboot.c
> > index bb0b76e1a6d4..f4d6acb38dd0 100644
> > --- a/arch/riscv/kernel/smpboot.c
> > +++ b/arch/riscv/kernel/smpboot.c
> > @@ -238,10 +238,11 @@ asmlinkage __visible void smp_callin(void)
> > mmgrab(mm);
> > current->active_mm = mm;
> >
> > - riscv_ipi_enable();
> > -
> > store_cpu_topology(curr_cpuid);
> > notify_cpu_starting(curr_cpuid);
> > +
> > + riscv_ipi_enable();
> > +
> > numa_add_cpu(curr_cpuid);
> > set_cpu_online(curr_cpuid, 1);
> > probe_vendor_features(curr_cpuid);
>
> Thanks. I was going to send another PR this week anyway, I can just
> pick this up if you want?
Yes please!
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-07-03 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 18:31 [PATCH] risc-v: Fix order of IPI enablement vs RCU startup Marc Zyngier
2023-07-03 18:45 ` Palmer Dabbelt
2023-07-03 18:58 ` Marc Zyngier [this message]
2023-07-03 20:04 ` Conor Dooley
2023-07-05 23:38 ` Palmer Dabbelt
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=86v8f0x1ok.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=apatel@ventanamicro.com \
--cc=conor@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.