From: Daniel Thompson <daniel.thompson@linaro.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Stephen Boyd <swboyd@chromium.org>, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org,
kgdb-bugreport@lists.sourceforge.net,
Marc Zyngier <maz@kernel.org>,
linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Masayoshi Mizuma <msys.mizuma@gmail.com>,
Will Deacon <will@kernel.org>,
ito-yuichi@fujitsu.com, Sumit Garg <sumit.garg@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Colin Cross <ccross@android.com>,
Matthias Kaehlcke <mka@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Tzung-Bi Shih <tzungbi@chromium.org>,
Alexander Potapenko <glider@google.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Dan Williams <dan.j.williams@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Ingo Molnar <mingo@kernel.org>,
John Ogness <john.ogness@linutronix.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Juergen Gross <jgross@suse.com>,
Kees Cook <keescook@chromium.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Liam Howlett <liam.howlett@oracle.com>,
Marco Elver <elver@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sami Tolvanen <samitolvanen@google.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Zhaoyang Huang <zhaoyang.huang@unisoc.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] hardlockup: detect hard lockups using secondary (buddy) cpus
Date: Mon, 24 Apr 2023 13:53:55 +0100 [thread overview]
Message-ID: <20230424125355.GA4054@aspen.lan> (raw)
In-Reply-To: <20230421155255.1.I6bf789d21d0c3d75d382e7e51a804a7a51315f2c@changeid>
On Fri, Apr 21, 2023 at 03:53:30PM -0700, Douglas Anderson wrote:
> From: Colin Cross <ccross@android.com>
>
> Implement a hardlockup detector that can be enabled on SMP systems
> that don't have an arch provided one or one implemented atop perf by
> using interrupts on other cpus. Each cpu will use its softlockup
> hrtimer to check that the next cpu is processing hrtimer interrupts by
> verifying that a counter is increasing.
>
> NOTE: unlike the other hard lockup detectors, the buddy one can't
> easily provide a backtrace on the CPU that locked up. It relies on
> some other mechanism in the system to get information about the locked
> up CPUs. This could be support for NMI backtraces like [1], it could
> be a mechanism for printing the PC of locked CPUs like [2], or it
> could be something else.
>
> This style of hardlockup detector originated in some downstream
> Android trees and has been rebased on / carried in ChromeOS trees for
> quite a long time for use on arm and arm64 boards. Historically on
> these boards we've leveraged mechanism [2] to get information about
> hung CPUs, but we could move to [1].
On the Arm platforms is this code able to leverage the existing
infrastructure to extract status from stuck CPUs:
https://docs.kernel.org/trace/coresight/coresight-cpu-debug.html
Daniel.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Stephen Boyd <swboyd@chromium.org>, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org,
kgdb-bugreport@lists.sourceforge.net,
Marc Zyngier <maz@kernel.org>,
linux-perf-users@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Masayoshi Mizuma <msys.mizuma@gmail.com>,
Will Deacon <will@kernel.org>,
ito-yuichi@fujitsu.com, Sumit Garg <sumit.garg@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Colin Cross <ccross@android.com>,
Matthias Kaehlcke <mka@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Tzung-Bi Shih <tzungbi@chromium.org>,
Alexander Potapenko <glider@google.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Dan Williams <dan.j.williams@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Ingo Molnar <mingo@kernel.org>,
John Ogness <john.ogness@linutronix.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Juergen Gross <jgross@suse.com>,
Kees Cook <keescook@chromium.org>,
Laurent Dufour <ldufour@linux.ibm.com>,
Liam Howlett <liam.howlett@oracle.com>,
Marco Elver <elver@google.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sami Tolvanen <samitolvanen@google.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
Zhaoyang Huang <zhaoyang.huang@unisoc.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] hardlockup: detect hard lockups using secondary (buddy) cpus
Date: Mon, 24 Apr 2023 13:53:55 +0100 [thread overview]
Message-ID: <20230424125355.GA4054@aspen.lan> (raw)
In-Reply-To: <20230421155255.1.I6bf789d21d0c3d75d382e7e51a804a7a51315f2c@changeid>
On Fri, Apr 21, 2023 at 03:53:30PM -0700, Douglas Anderson wrote:
> From: Colin Cross <ccross@android.com>
>
> Implement a hardlockup detector that can be enabled on SMP systems
> that don't have an arch provided one or one implemented atop perf by
> using interrupts on other cpus. Each cpu will use its softlockup
> hrtimer to check that the next cpu is processing hrtimer interrupts by
> verifying that a counter is increasing.
>
> NOTE: unlike the other hard lockup detectors, the buddy one can't
> easily provide a backtrace on the CPU that locked up. It relies on
> some other mechanism in the system to get information about the locked
> up CPUs. This could be support for NMI backtraces like [1], it could
> be a mechanism for printing the PC of locked CPUs like [2], or it
> could be something else.
>
> This style of hardlockup detector originated in some downstream
> Android trees and has been rebased on / carried in ChromeOS trees for
> quite a long time for use on arm and arm64 boards. Historically on
> these boards we've leveraged mechanism [2] to get information about
> hung CPUs, but we could move to [1].
On the Arm platforms is this code able to leverage the existing
infrastructure to extract status from stuck CPUs:
https://docs.kernel.org/trace/coresight/coresight-cpu-debug.html
Daniel.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-24 12:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:53 [PATCH] hardlockup: detect hard lockups using secondary (buddy) cpus Douglas Anderson
2023-04-21 22:53 ` Douglas Anderson
2023-04-21 23:59 ` Randy Dunlap
2023-04-21 23:59 ` Randy Dunlap
2023-04-22 1:19 ` Ian Rogers
2023-04-24 15:23 ` Doug Anderson
2023-05-07 17:12 ` Andi Kleen
2023-04-24 12:53 ` Daniel Thompson [this message]
2023-04-24 12:53 ` Daniel Thompson
2023-04-24 15:41 ` Doug Anderson
2023-04-24 15:41 ` Doug Anderson
2023-04-25 4:58 ` Chen-Yu Tsai
2023-04-25 4:58 ` Chen-Yu Tsai
2023-04-25 15:26 ` Doug Anderson
2023-04-25 15:26 ` Doug Anderson
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=20230424125355.GA4054@aspen.lan \
--to=daniel.thompson@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=catalin.marinas@arm.com \
--cc=ccross@android.com \
--cc=dan.j.williams@intel.com \
--cc=dianders@chromium.org \
--cc=elver@google.com \
--cc=geert+renesas@glider.be \
--cc=glider@google.com \
--cc=groeck@chromium.org \
--cc=ito-yuichi@fujitsu.com \
--cc=jgross@suse.com \
--cc=john.ogness@linutronix.de \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=ldufour@linux.ibm.com \
--cc=lecopzer.chen@mediatek.com \
--cc=liam.howlett@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=mka@chromium.org \
--cc=mpe@ellerman.id.au \
--cc=msys.mizuma@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=samitolvanen@google.com \
--cc=sstabellini@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=swboyd@chromium.org \
--cc=thunder.leizhen@huawei.com \
--cc=tzungbi@chromium.org \
--cc=vbabka@suse.cz \
--cc=wens@csie.org \
--cc=will@kernel.org \
--cc=zhaoyang.huang@unisoc.com \
/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.