From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org, Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
kernel-team@android.com,
Alexandru Elisei <alexandru.elisei@arm.com>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Sumit Garg <sumit.garg@linaro.org>
Subject: Re: [PATCH] Revert "arm64: Enable perf events based hard lockup detector"
Date: Wed, 13 Jan 2021 16:07:51 +0000 [thread overview]
Message-ID: <161055398864.21762.5686527477594676828.b4-ty@arm.com> (raw)
In-Reply-To: <20210112221855.10666-1-will@kernel.org>
On Tue, 12 Jan 2021 22:18:55 +0000, Will Deacon wrote:
> This reverts commit 367c820ef08082e68df8a3bc12e62393af21e4b5.
>
> lockup_detector_init() makes heavy use of per-cpu variables and must be
> called with preemption disabled. Usually, it's handled early during boot
> in kernel_ionit_freeable(), before SMP has been initialised.
>
> Since we do not know whether or not our PMU interrupt can be signalled
> as an NMI until considerably later in the boot process, the Arm PMU
> driver attempts to re-initialise the lockup detector off the back of a
> device_initcall(). Unfortunately, this is called from preemptible
> context and results in the following splat:
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/1] Revert "arm64: Enable perf events based hard lockup detector"
https://git.kernel.org/arm64/c/b90d72a6bfdb
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-01-13 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:18 [PATCH] Revert "arm64: Enable perf events based hard lockup detector" Will Deacon
2021-01-13 6:30 ` Sumit Garg
2021-01-13 10:28 ` Will Deacon
2021-01-13 13:42 ` Sumit Garg
2021-01-13 13:02 ` Mark Rutland
2021-01-28 7:05 ` Sumit Garg
2021-01-13 16:07 ` Catalin Marinas [this message]
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=161055398864.21762.5686527477594676828.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=alexandru.elisei@arm.com \
--cc=kernel-team@android.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=sumit.garg@linaro.org \
--cc=will@kernel.org \
/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.