From: Lecopzer Chen <lecopzer.chen@mediatek.com>
To: <linux-kernel@vger.kernel.org>, <pmladek@suse.com>
Cc: <lecopzer.chen@mediatek.com>, <acme@kernel.org>,
<akpm@linux-foundation.org>, <alexander.shishkin@linux.intel.com>,
<catalin.marinas@arm.com>, <davem@davemloft.net>,
<jolsa@redhat.com>, <jthierry@redhat.com>,
<keescook@chromium.org>, <kernelfans@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>, <mark.rutland@arm.com>,
<masahiroy@kernel.org>, <matthias.bgg@gmail.com>,
<maz@kernel.org>, <mcgrof@kernel.org>, <mingo@redhat.com>,
<namhyung@kernel.org>, <nixiaoming@huawei.com>,
<peterz@infradead.org>, <sparclinux@vger.kernel.org>,
<sumit.garg@linaro.org>, <wangqing@vivo.com>, <will@kernel.org>,
<yj.chiang@mediatek.com>
Subject: [PATCH v4 0/6] Support hld delayed init based on Pseudo-NMI for arm64
Date: Thu, 28 Apr 2022 00:13:34 +0800 [thread overview]
Message-ID: <20220427161340.8518-1-lecopzer.chen@mediatek.com> (raw)
As we already used hld internally for arm64 since 2020, there still
doesn't have a proper commit on the upstream and we badly need it.
This serise rework on 5.17 from [1] and the origin author is
Pingfan Liu <kernelfans@gmail.com>
Sumit Garg <sumit.garg@linaro.org>
Qoute from [1]:
> Hard lockup detector is helpful to diagnose unpaired irq enable/disable.
> But the current watchdog framework can not cope with arm64 hw perf event
> easily.
> On arm64, when lockup_detector_init()->watchdog_nmi_probe(), PMU is not
> ready until device_initcall(armv8_pmu_driver_init). And it is deeply
> integrated with the driver model and cpuhp. Hence it is hard to push the
> initialization of armv8_pmu_driver_init() before smp_init().
> But it is easy to take an opposite approach by enabling watchdog_hld to
> get the capability of PMU async.
> The async model is achieved by expanding watchdog_nmi_probe() with
> -EBUSY, and a re-initializing work_struct which waits on a
> wait_queue_head.
Provide an API - retry_lockup_detector_init() for anyone who needs
to delayed init lockup detector.
The original assumption is: nobody should use delayed probe after
lockup_detector_check() (which has __init attribute).
That is, anyone uses this API must call between lockup_detector_init()
and lockup_detector_check(), and the caller must have __init attribute
The delayed init flow is:
1. lockup_detector_init() -> watchdog_nmi_probe() get non-zero retun,
then set allow_lockup_detector_init_retry to true which means it's
able to do delayed probe later.
2. PMU arch code init done, call retry_lockup_detector_init().
3. retry_lockup_detector_init() queue the work only when
allow_lockup_detector_init_retry is true which means nobody should call
this before lockup_detector_init().
4. the work lockup_detector_delay_init() is doing without wait event.
if probe success, set allow_lockup_detector_init_retry to false.
5. at late_initcall_sync(), lockup_detector_check() set
allow_lockup_detector_init_retry to false first to avoid any later retry,
and then flush_work() to make sure the __init section won't be freed
before the work done.
[1] https://lore.kernel.org/lkml/20211014024155.15253-1-kernelfans@gmail.com/
v4:
1. remove -EBUSY protocal, let all the non-zero value from
watchdog_nmi_probe() be able to retry.
2. separate arm64 part patch into hw_nmi_get_sample_period and retry
delayed init
3. tweak commit msg that we don't have to limit to -EBUSY
4. rebase on v5.18-rc4
v3:
1. Tweak commit message in patch 04
2. Remove wait event
3. s/lockup_detector_pending_init/allow_lockup_detector_init_retry/
4. provide api retry_lockup_detector_init()
https://lore.kernel.org/lkml/20220324141405.10835-1-lecopzer.chen@mediatek.com/
v2:
1. Tweak commit message in patch 01/02/04/05
2. Remove vobose WARN in patch 04 within watchdog core.
3. Change from three states variable: detector_delay_init_state to
two states variable: allow_lockup_detector_init_retry
Thanks Petr Mladek <pmladek@suse.com> for the idea.
> 1. lockup_detector_work() called before lockup_detector_check().
> In this case, wait_event() will wait until lockup_detector_check()
> clears detector_delay_pending_init and calls wake_up().
> 2. lockup_detector_check() called before lockup_detector_work().
> In this case, wait_even() will immediately continue because
> it will see cleared detector_delay_pending_init.
4. Add comment in code in patch 04/05 for two states variable changing.
https://lore.kernel.org/lkml/20220307154729.13477-1-lecopzer.chen@mediatek.com/
Lecopzer Chen (5):
kernel/watchdog: remove WATCHDOG_DEFAULT
kernel/watchdog: change watchdog_nmi_enable() to void
kernel/watchdog: Adapt the watchdog_hld interface for async model
arm64: add hw_nmi_get_sample_period for preparation of lockup detector
arm64: Enable perf events based hard lockup detector
Pingfan Liu (1):
kernel/watchdog_hld: Ensure CPU-bound context when creating hardlockup
detector event
arch/arm64/Kconfig | 2 +
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/perf_event.c | 10 ++++-
arch/arm64/kernel/watchdog_hld.c | 39 +++++++++++++++++
arch/sparc/kernel/nmi.c | 8 ++--
drivers/perf/arm_pmu.c | 5 +++
include/linux/nmi.h | 4 +-
include/linux/perf/arm_pmu.h | 2 +
kernel/watchdog.c | 72 +++++++++++++++++++++++++++++---
kernel/watchdog_hld.c | 8 +++-
10 files changed, 137 insertions(+), 14 deletions(-)
create mode 100644 arch/arm64/kernel/watchdog_hld.c
--
2.25.1
next reply other threads:[~2022-04-27 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:13 Lecopzer Chen [this message]
2022-04-27 16:13 ` [PATCH v4 1/6] kernel/watchdog: remove WATCHDOG_DEFAULT Lecopzer Chen
2022-04-27 16:13 ` [PATCH v4 2/6] kernel/watchdog: change watchdog_nmi_enable() to void Lecopzer Chen
2022-04-27 16:13 ` [PATCH v4 3/6] kernel/watchdog_hld: Ensure CPU-bound context when creating hardlockup detector event Lecopzer Chen
2022-04-27 16:13 ` [PATCH v4 4/6] kernel/watchdog: Adapt the watchdog_hld interface for async model Lecopzer Chen
2022-05-20 9:38 ` Petr Mladek
2022-05-26 9:39 ` Lecopzer Chen
2022-04-27 16:13 ` [PATCH v4 5/6] arm64: add hw_nmi_get_sample_period for preparation of lockup detector Lecopzer Chen
2022-04-27 16:13 ` [PATCH v4 6/6] arm64: Enable perf events based hard " Lecopzer Chen
2022-05-20 9:47 ` Petr Mladek
2022-05-26 9:35 ` Lecopzer Chen
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=20220427161340.8518-1-lecopzer.chen@mediatek.com \
--to=lecopzer.chen@mediatek.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=jolsa@redhat.com \
--cc=jthierry@redhat.com \
--cc=keescook@chromium.org \
--cc=kernelfans@gmail.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=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=maz@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nixiaoming@huawei.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sparclinux@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--cc=wangqing@vivo.com \
--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).