From: Andi Kleen <ak@linux.intel.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Ian Rogers <irogers@google.com>,
ravi.v.shankar@intel.com, ricardo.neri@intel.com,
Stephane Eranian <eranian@google.com>,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
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: Sun, 7 May 2023 10:12:29 -0700 [thread overview]
Message-ID: <ZFfb/bTi22RQwaol@tassilo> (raw)
In-Reply-To: <CAD=FV=Xuuefi9XBQA7z7sbe+Qw0=WeZ956gLGCoFGHBg6GBftg@mail.gmail.com>
On Mon, Apr 24, 2023 at 08:23:59AM -0700, Doug Anderson wrote:
> HPET system seems to have a single CPU in charge of processing the
> main NMI and then that single CPU is in charge of checking all the
> others. If that single CPU goes out to lunch then the system couldn't
> detect hard lockups.
>
> In any case, I'm happy to let others debate about the HPET system. For
> now, I'll take my action items to be:
We don't really seem to make any progress on the HPET series, so even
if it is better in some way a series that is never merged is always
worse than one that is.
My experience is that cases where everything locks up are very rare.
I suspect as long as we cover the garden variety single CPU lockup case well
it is likely very diminishing returns to handle more complex cases. So whatever
gets the job done is fine.
Yes freeing the Perfmon resources is big advantage of either.
-Andi
next prev parent reply other threads:[~2023-05-07 17:12 UTC|newest]
Thread overview: 9+ 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 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 [this message]
2023-04-24 12:53 ` Daniel Thompson
2023-04-24 15:41 ` Doug Anderson
2023-04-25 4:58 ` Chen-Yu Tsai
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=ZFfb/bTi22RQwaol@tassilo \
--to=ak@linux.intel.com \
--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=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=elver@google.com \
--cc=eranian@google.com \
--cc=geert+renesas@glider.be \
--cc=glider@google.com \
--cc=groeck@chromium.org \
--cc=irogers@google.com \
--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=ravi.v.shankar@intel.com \
--cc=rdunlap@infradead.org \
--cc=ricardo.neri@intel.com \
--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 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).