[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221116082221.25243-1-yunying.sun@intel.com>
Date: Wed, 16 Nov 2022 16:22:21 +0800
From: Yunying Sun <yunying.sun@...el.com>
To: tglx@...utronix.de, peterz@...radead.org, paulmck@...nel.org,
longman@...hat.com, x86@...nel.org, linux-kernel@...r.kernel.org
Cc: feng.tang@...el.com, yunying.sun@...el.com
Subject: [PATCH] clocksource: Print clocksource name when clocksource is tested unstable
Some "TSC fall back to HPET" cases are seen on systems that have more
than 2 numa nodes. When this happens, in kernel log it has:
clocksource: timekeeping watchdog on CPU168: hpet read-back delay of 4296200ns, attempt 4, marking unstable
The "hpet" here is misleading since it prints only the name of watchdog,
where actually it's measuring the delay of 3 reads: wd-clocksource-wd.
Signed-off-by: Yunying Sun <yunying.sun@...el.com>
---
kernel/time/clocksource.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
index 8058bec87ace..fac8c0d90e61 100644
--- a/kernel/time/clocksource.c
+++ b/kernel/time/clocksource.c
@@ -257,8 +257,8 @@ static enum wd_read_status cs_watchdog_read(struct clocksource *cs, u64 *csnow,
goto skip_test;
}
- pr_warn("timekeeping watchdog on CPU%d: %s read-back delay of %lldns, attempt %d, marking unstable\n",
- smp_processor_id(), watchdog->name, wd_delay, nretries);
+ pr_warn("timekeeping watchdog on CPU%d: wd-%s-wd read-back delay of %lldns, attempt %d, marking unstable\n",
+ smp_processor_id(), cs->name, wd_delay, nretries);
return WD_READ_UNSTABLE;
skip_test:
--
2.17.0
Powered by blists - more mailing lists