[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE-0n51weSj5thSdTdpKmQsycsQgc2MovsTanSUmQ4GEtYBcxw@mail.gmail.com>
Date: Tue, 22 Aug 2023 16:41:35 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Catalin Marinas <catalin.marinas@....com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Douglas Anderson <dianders@...omium.org>,
Marc Zyngier <maz@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Sumit Garg <sumit.garg@...aro.org>,
Will Deacon <will@...nel.org>
Cc: Lecopzer Chen <lecopzer.chen@...iatek.com>,
linux-arm-kernel@...ts.infradead.org,
linux-perf-users@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
kgdb-bugreport@...ts.sourceforge.net, ito-yuichi@...itsu.com,
Thomas Gleixner <tglx@...utronix.de>,
Chen-Yu Tsai <wens@...e.org>, Ard Biesheuvel <ardb@...nel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Masayoshi Mizuma <msys.mizuma@...il.com>,
D Scott Phillips <scott@...amperecomputing.com>,
Ingo Molnar <mingo@...nel.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Valentin Schneider <vschneid@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v10 5/6] arm64: smp: IPI_CPU_STOP and IPI_CPU_CRASH_STOP
should try for NMI
Quoting Douglas Anderson (2023-08-22 14:27:00)
> There's no reason why IPI_CPU_STOP and IPI_CPU_CRASH_STOP can't be
> handled as NMI. They are very simple and everything in them is
> NMI-safe. Mark them as things to use NMI for if NMI is available.
>
> Suggested-by: Mark Rutland <mark.rutland@....com>
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
> ---
Reviewed-by: Stephen Boyd <swboyd@...omium.org>
Powered by blists - more mailing lists