From: Song Liu <song@kernel.org>
To: <linux-kernel@vger.kernel.org>
Cc: <kernel-team@meta.com>, Song Liu <song@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: [PATCH v2] watchdog: Prefer use "ref-cycles" for NMI watchdog
Date: Tue, 16 May 2023 16:58:17 -0700 [thread overview]
Message-ID: <20230516235817.2323062-1-song@kernel.org> (raw)
NMI watchdog permanently consumes one hardware counters per CPU on the
system. For systems that use many hardware counters, this causes more
aggressive time multiplexing of perf events.
OTOH, some CPUs (mostly Intel) support "ref-cycles" event, which is rarely
used. Try use "ref-cycles" for the watchdog, so that one more hardware
counter is available to the user. If the CPU doesn't support "ref-cycles",
fall back to "cycles".
The downside of this change is that users of "ref-cycles" need to disable
nmi_watchdog.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Song Liu <song@kernel.org>
---
Changes in v2:
1. Do not send warning when failed to create ref-cycles event.
---
kernel/watchdog_hld.c | 20 ++++++++++++++------
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/kernel/watchdog_hld.c b/kernel/watchdog_hld.c
index 247bf0b1582c..a1d2a43ea31f 100644
--- a/kernel/watchdog_hld.c
+++ b/kernel/watchdog_hld.c
@@ -100,7 +100,7 @@ static inline bool watchdog_check_timestamp(void)
static struct perf_event_attr wd_hw_attr = {
.type = PERF_TYPE_HARDWARE,
- .config = PERF_COUNT_HW_CPU_CYCLES,
+ .config = PERF_COUNT_HW_REF_CPU_CYCLES,
.size = sizeof(struct perf_event_attr),
.pinned = 1,
.disabled = 1,
@@ -163,7 +163,7 @@ static void watchdog_overflow_callback(struct perf_event *event,
return;
}
-static int hardlockup_detector_event_create(void)
+static int hardlockup_detector_event_create(bool send_warning)
{
unsigned int cpu = smp_processor_id();
struct perf_event_attr *wd_attr;
@@ -176,8 +176,10 @@ static int hardlockup_detector_event_create(void)
evt = perf_event_create_kernel_counter(wd_attr, cpu, NULL,
watchdog_overflow_callback, NULL);
if (IS_ERR(evt)) {
- pr_debug("Perf event create on CPU %d failed with %ld\n", cpu,
- PTR_ERR(evt));
+ if (send_warning) {
+ pr_debug("Perf event create on CPU %d failed with %ld\n", cpu,
+ PTR_ERR(evt));
+ }
return PTR_ERR(evt);
}
this_cpu_write(watchdog_ev, evt);
@@ -189,7 +191,7 @@ static int hardlockup_detector_event_create(void)
*/
void hardlockup_detector_perf_enable(void)
{
- if (hardlockup_detector_event_create())
+ if (hardlockup_detector_event_create(true))
return;
/* use original value for check */
@@ -284,7 +286,13 @@ void __init hardlockup_detector_perf_restart(void)
*/
int __init hardlockup_detector_perf_init(void)
{
- int ret = hardlockup_detector_event_create();
+ int ret = hardlockup_detector_event_create(false);
+
+ if (ret) {
+ /* Failed to create "ref-cycles", try "cycles" instead */
+ wd_hw_attr.config = PERF_COUNT_HW_CPU_CYCLES;
+ ret = hardlockup_detector_event_create(true);
+ }
if (ret) {
pr_info("Perf NMI watchdog permanently disabled\n");
--
2.34.1
next reply other threads:[~2023-05-16 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 23:58 Song Liu [this message]
2023-05-17 1:23 ` [PATCH v2] watchdog: Prefer use "ref-cycles" for NMI watchdog Li, Xin3
2023-05-17 4:38 ` Song Liu
2023-05-17 7:31 ` Peter Zijlstra
2023-05-17 17:51 ` Song Liu
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=20230516235817.2323062-1-song@kernel.org \
--to=song@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox