From: Will Deacon <will@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>, alexandru.elisei@arm.com
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
mark.rutland@arm.com, peterz@infradead.org,
dianders@chromium.org, acme@kernel.org, swboyd@chromium.org,
namhyung@kernel.org, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, julien.thierry.kdev@gmail.com,
daniel.thompson@linaro.org
Subject: Re: [PATCH v4] arm64: Enable perf events based hard lockup detector
Date: Wed, 25 Nov 2020 15:44:08 +0000 [thread overview]
Message-ID: <160631752004.2333389.970698439984795478.b4-ty@kernel.org> (raw)
In-Reply-To: <1602060704-10921-1-git-send-email-sumit.garg@linaro.org>
On Wed, 7 Oct 2020 14:21:43 +0530, Sumit Garg 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.
Applied to will (for-next/perf), thanks!
[1/1] arm64: Enable perf events based hard lockup detector
https://git.kernel.org/will/c/367c820ef080
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>, alexandru.elisei@arm.com
Cc: mark.rutland@arm.com, daniel.thompson@linaro.org,
Will Deacon <will@kernel.org>,
peterz@infradead.org, catalin.marinas@arm.com, jolsa@redhat.com,
linux-kernel@vger.kernel.org, acme@kernel.org,
dianders@chromium.org, alexander.shishkin@linux.intel.com,
mingo@redhat.com, julien.thierry.kdev@gmail.com,
namhyung@kernel.org, tglx@linutronix.de, swboyd@chromium.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4] arm64: Enable perf events based hard lockup detector
Date: Wed, 25 Nov 2020 15:44:08 +0000 [thread overview]
Message-ID: <160631752004.2333389.970698439984795478.b4-ty@kernel.org> (raw)
In-Reply-To: <1602060704-10921-1-git-send-email-sumit.garg@linaro.org>
On Wed, 7 Oct 2020 14:21:43 +0530, Sumit Garg 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.
Applied to will (for-next/perf), thanks!
[1/1] arm64: Enable perf events based hard lockup detector
https://git.kernel.org/will/c/367c820ef080
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
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:[~2020-11-25 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:51 [PATCH v4] arm64: Enable perf events based hard lockup detector Sumit Garg
2020-10-07 8:51 ` Sumit Garg
2020-10-09 10:23 ` Sumit Garg
2020-10-09 10:23 ` Sumit Garg
2020-10-09 10:26 ` Alexandru Elisei
2020-10-09 10:26 ` Alexandru Elisei
2020-10-29 9:22 ` Sumit Garg
2020-10-29 9:22 ` Sumit Garg
2020-11-25 15:44 ` Will Deacon [this message]
2020-11-25 15:44 ` Will Deacon
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=160631752004.2333389.970698439984795478.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandru.elisei@arm.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jolsa@redhat.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sumit.garg@linaro.org \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
/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.