From: Mark Rutland <mark.rutland@arm.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Sumit Garg <sumit.garg@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Marc Zyngier <maz@kernel.org>,
linux-perf-users@vger.kernel.org, ito-yuichi@fujitsu.com,
Chen-Yu Tsai <wens@csie.org>, Ard Biesheuvel <ardb@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org,
kgdb-bugreport@lists.sourceforge.net,
Masayoshi Mizuma <msys.mizuma@gmail.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 3/7] arm64: Add framework for a debug IPI
Date: Tue, 22 Aug 2023 07:42:47 +0100 [thread overview]
Message-ID: <ZORY51mF4alI41G1@FVFF77S0Q05N> (raw)
In-Reply-To: <CAD=FV=VVJsJSc=uQWad4x0EV2-iROFcueW_=4VbM+0N0+aD96g@mail.gmail.com>
On Mon, Aug 21, 2023 at 03:16:56PM -0700, Doug Anderson wrote:
> Hi,
>
> On Mon, Aug 7, 2023 at 3:12 AM Mark Rutland <mark.rutland@arm.com> wrote:
> >
> > On Thu, Jun 01, 2023 at 02:31:47PM -0700, Douglas Anderson wrote:
> > > From: Sumit Garg <sumit.garg@linaro.org>
> > >
> > > Introduce a framework for an IPI that will be used for debug
> > > purposes. The primary use case of this IPI will be to generate stack
> > > crawls on other CPUs, but it will also be used to round up CPUs for
> > > kgdb.
> > >
> > > When possible, we try to allocate this debug IPI as an NMI (or a
> > > pseudo NMI). If that fails (due to CONFIG, an incompatible interrupt
> > > controller, a quirk, missing the "irqchip.gicv3_pseudo_nmi=1" kernel
> > > parameter, etc) we fall back to a normal IPI.
> > >
> > > NOTE: hooking this up for CPU backtrace / kgdb will happen in a future
> > > patch, this just adds the framework.
> > >
> > > Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> > > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> >
> > I think that we shouldn't add a framework in a separate file for this:
> >
> > * This is very similar to our existing IPI management in smp.c, so it feels
> > like duplication, or at least another thing we'd like to keep in-sync.
> >
> > * We're going to want an NMI backtrace regardless of KGDB
> >
> > * We're going to want the IPI_CPU_STOP and IPI_CRASH_CPU_STOP IPIs to be NMIs
> > too.
> >
> > I reckon it'd be better to extend the existing IPI logic in smp.c to allow IPIs
> > to be requested as NMIs, e.g.
> >
> > ----
> > diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> > index edd63894d61e8..48e6aa62c473e 100644
> > --- a/arch/arm64/kernel/smp.c
> > +++ b/arch/arm64/kernel/smp.c
> > @@ -33,6 +33,7 @@
> > #include <linux/kernel_stat.h>
> > #include <linux/kexec.h>
> > #include <linux/kvm_host.h>
> > +#include <linux/nmi.h>
> >
> > #include <asm/alternative.h>
> > #include <asm/atomic.h>
> > @@ -926,6 +927,21 @@ static void smp_cross_call(const struct cpumask *target, unsigned int ipinr)
> > __ipi_send_mask(ipi_desc[ipinr], target);
> > }
> >
> > +static bool ipi_should_be_nmi(enum ipi_msg_type ipi)
> > +{
> > + if (!system_uses_irq_prio_masking())
> > + return false;
> > +
> > + switch (ipi) {
> > + /*
> > + * TODO: select NMI IPIs here
> > + */
> > + return true;
> > + default:
> > + return false;
> > + }
> > +}
> > +
> > static void ipi_setup(int cpu)
> > {
> > int i;
> > @@ -933,8 +949,14 @@ static void ipi_setup(int cpu)
> > if (WARN_ON_ONCE(!ipi_irq_base))
> > return;
> >
> > - for (i = 0; i < nr_ipi; i++)
> > - enable_percpu_irq(ipi_irq_base + i, 0);
> > + for (i = 0; i < nr_ipi; i++) {
> > + if (ipi_should_be_nmi(i)) {
> > + prepare_percpu_nmi(ipi_irq_base + i);
> > + enable_percpu_nmi(ipi_irq_base + i, 0);
> > + } else {
> > + enable_percpu_irq(ipi_irq_base + i, 0);
> > + }
> > + }
> > }
> >
> > #ifdef CONFIG_HOTPLUG_CPU
> > @@ -945,8 +967,14 @@ static void ipi_teardown(int cpu)
> > if (WARN_ON_ONCE(!ipi_irq_base))
> > return;
> >
> > - for (i = 0; i < nr_ipi; i++)
> > - disable_percpu_irq(ipi_irq_base + i);
> > + for (i = 0; i < nr_ipi; i++) {
> > + if (ipi_should_be_nmi(i)) {
> > + disable_percpu_nmi(ipi_irq_base + i);
> > + teardown_percpu_nmi(ipi_irq_base + i);
> > + } else {
> > + disable_percpu_irq(ipi_irq_base + i);
> > + }
> > + }
> > }
> > #endif
> >
> > @@ -958,11 +986,19 @@ void __init set_smp_ipi_range(int ipi_base, int n)
> > nr_ipi = min(n, NR_IPI);
> >
> > for (i = 0; i < nr_ipi; i++) {
> > - int err;
> > -
> > - err = request_percpu_irq(ipi_base + i, ipi_handler,
> > - "IPI", &cpu_number);
> > - WARN_ON(err);
> > + int err = -EINVAL;
> > +
> > + if (ipi_should_be_nmi(i)) {
> > + err = request_percpu_nmi(ipi_base + i, ipi_handler,
> > + "IPI", &cpu_number);
> > + WARN(err, "Could not request IPI %d as NMI, err=%d\n",
> > + i, err);
> > + } else {
> > + err = request_percpu_irq(ipi_base + i, ipi_handler,
> > + "IPI", &cpu_number);
> > + WARN(err, "Could not request IPI %d as IRQ, err=%d\n",
> > + i, err);
> > + }
> >
> > ipi_desc[i] = irq_to_desc(ipi_base + i);
> > irq_set_status_flags(ipi_base + i, IRQ_HIDDEN);
> > ----
> >
> > ... and then if we need an IPI for KGDB, we can add that to the existing list
> > of IPIs, and have it requested/enabled/disabled as usual.
>
> Sounds good. I'm starting to work on v10 incorporating your feedback.
> A few quick questions:
>
> 1. If I mostly take your patch above verbatim, do you have any
> suggested tags for Author/Signed-off-by? I'd tend to set you as the
> author but I can't do that because you didn't provide a
> Signed-off-by...
Sorry about that. For the above:
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
If squashed into another patch, then feel free to use:
Co-developed-by: Mark Rutland <mark.rutland@arm.com>
> 2. Would you prefer this patch on its own, or would you rather it be
> squashed with the first user ("backtrace")? On its own, I think I have
> to get rid of the "switch" statement in ipi_should_be_nmi() and just
> return false;
I reckon it makes sense to squash it with the first user.
Thanks,
Mark.
next prev parent reply other threads:[~2023-08-22 6:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 21:31 [PATCH v9 0/7] arm64: Add debug IPI for backtraces / kgdb; try to use NMI for it Douglas Anderson
2023-06-01 21:31 ` [PATCH v9 1/7] irqchip/gic-v3: Enable support for SGIs to act as NMIs Douglas Anderson
2023-08-07 9:50 ` Mark Rutland
2023-08-07 11:22 ` Sumit Garg
2023-08-07 13:25 ` Mark Rutland
2023-06-01 21:31 ` [PATCH v9 2/7] arm64: idle: Tag the arm64 idle functions as __cpuidle Douglas Anderson
2023-08-07 9:52 ` Mark Rutland
2023-06-01 21:31 ` [PATCH v9 3/7] arm64: Add framework for a debug IPI Douglas Anderson
2023-08-07 10:12 ` Mark Rutland
2023-08-21 22:16 ` Doug Anderson
2023-08-22 6:42 ` Mark Rutland [this message]
2023-06-01 21:31 ` [PATCH v9 4/7] arm64: smp: Assign and setup the " Douglas Anderson
2023-08-07 10:17 ` Mark Rutland
2023-06-01 21:31 ` [PATCH v9 5/7] arm64: ipi_debug: Add support for backtrace using " Douglas Anderson
2023-08-07 10:23 ` Mark Rutland
2023-08-22 0:06 ` Doug Anderson
2023-08-22 6:35 ` Mark Rutland
2023-06-01 21:31 ` [PATCH v9 6/7] kgdb: Provide a stub kgdb_nmicallback() if !CONFIG_KGDB Douglas Anderson
2023-06-15 18:14 ` Doug Anderson
2023-06-26 14:30 ` Daniel Thompson
2023-08-07 10:27 ` Mark Rutland
2023-08-07 10:29 ` Mark Rutland
2023-06-01 21:31 ` [PATCH v9 7/7] arm64: kgdb: Roundup cpus using the debug IPI Douglas Anderson
2023-08-07 10:28 ` Mark Rutland
2023-08-07 10:47 ` Marc Zyngier
2023-08-07 10:54 ` Mark Rutland
2023-08-07 11:08 ` Marc Zyngier
2023-08-07 11:13 ` Mark Rutland
2023-08-07 15:24 ` Daniel Thompson
2023-08-07 16:04 ` Mark Rutland
2023-08-08 11:17 ` Daniel Thompson
2023-06-02 5:19 ` [PATCH v9 0/7] arm64: Add debug IPI for backtraces / kgdb; try to use NMI for it Sumit Garg
2023-07-24 15:55 ` Doug Anderson
2023-08-07 10:41 ` Mark Rutland
2023-08-07 12:46 ` Sumit Garg
2023-08-07 14:43 ` Mark Rutland
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=ZORY51mF4alI41G1@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=ito-yuichi@fujitsu.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maz@kernel.org \
--cc=msys.mizuma@gmail.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sumit.garg@linaro.org \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=wens@csie.org \
--cc=will@kernel.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