From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <lecopzer.chen@mediatek.com>
Cc: <alexandru.elisei@arm.com>, <catalin.marinas@arm.com>,
<daniel.thompson@linaro.org>, <dianders@chromium.org>,
<lecopzer@gmail.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <mark.rutland@arm.com>,
<sumit.garg@linaro.org>, <swboyd@chromium.org>, <will@kernel.org>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH v5] arm64: Enable perf events based hard lockup detector
Date: Tue, 30 Mar 2021 16:32:18 +0800 [thread overview]
Message-ID: <20210330083218.22285-1-lecopzer.chen@mediatek.com> (raw)
In-Reply-To: <20210330080615.21938-1-lecopzer.chen@mediatek.com>
> > Hi Will, Mark,
> >
> > On Fri, 15 Jan 2021 at 17:32, Sumit Garg <sumit.garg@linaro.org> wrote:
> > >
> > > With the recent feature added to enable perf events to use pseudo NMIs
> > > as interrupts on platforms which support GICv3 or later, its now been
> > > possible to enable hard lockup detector (or NMI watchdog) on arm64
> > > platforms. So enable corresponding support.
> > >
> > > One thing to note here is that normally lockup detector is initialized
> > > just after the early initcalls but PMU on arm64 comes up much later as
> > > device_initcall(). So we need to re-initialize lockup detection once
> > > PMU has been initialized.
> > >
> > > Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> > > ---
> > >
> > > Changes in v5:
> > > - Fix lockup_detector_init() invocation to be rather invoked from CPU
> > > binded context as it makes heavy use of per-cpu variables and shouldn't
> > > be invoked from preemptible context.
> > >
> >
> > Do you have any further comments on this?
> >
> > Lecopzer,
> >
> > Does this feature work fine for you now?
>
> This really fixes the warning, I have a real hardware for testing this now.
> but do we need to call lockup_detector_init() for each cpu?
>
> In init/main.c, it's only called by cpu 0 for once.
Oh sorry, I just misread the code, please ignore previous mail.
BRs,
Lecopzer
_______________________________________________
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:[~2021-03-30 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 12:01 [PATCH v5] arm64: Enable perf events based hard lockup detector Sumit Garg
2021-01-26 14:18 ` Will Deacon
2021-01-28 7:07 ` Sumit Garg
2021-02-19 9:37 ` Sumit Garg
2021-03-30 8:06 ` Lecopzer Chen
2021-03-30 8:32 ` Lecopzer Chen [this message]
2021-03-30 12:30 ` Sumit Garg
2021-04-12 12:01 ` Sumit Garg
2021-04-19 17:03 ` Will Deacon
[not found] ` <CAFA6WYOygwhhH4fuB8DFPHWF5KkxORH0E0AKL8Xp0y1jNuQr-w@mail.gmail.com>
2021-07-19 6:35 ` Fwd: " Huang Shijie
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=20210330083218.22285-1-lecopzer.chen@mediatek.com \
--to=lecopzer.chen@mediatek.com \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=lecopzer@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sumit.garg@linaro.org \
--cc=swboyd@chromium.org \
--cc=will@kernel.org \
--cc=yj.chiang@mediatek.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).