From: Feng Tang <feng.tang@intel.com>
To: "Sun, Yunying" <yunying.sun@intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"peterz@infradead.org" <peterz@infradead.org>,
<dave.hansen@intel.com>
Cc: "paulmck@kernel.org" <paulmck@kernel.org>,
"longman@redhat.com" <longman@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] clocksource: Print clocksource name when clocksource is tested unstable
Date: Thu, 17 Nov 2022 16:35:43 +0800 [thread overview]
Message-ID: <Y3XyX24/kuafuqGH@feng-clx> (raw)
In-Reply-To: <DM6PR11MB4092BD02BEB543EB4A28489FF2069@DM6PR11MB4092.namprd11.prod.outlook.com>
On Thu, Nov 17, 2022 at 04:03:07PM +0800, Sun, Yunying wrote:
> Hi Feng,
>
> For the "tsc fall back to hpet" issue, thanks a lot for pointing me to the fix proposal patch earlier:
> https://lore.kernel.org/lkml/20221021062131.1826810-1-feng.tang@intel.com/ .
>
> I shared this patch set to our customer yesterday.
> Just got feedback that customer has verified the "tsc fall back to hpet" issue does not appear anymore with this patch set, after 24hrs stress test on 8 servers.
Thanks for the testing! So your case is a real case that current
'nr_online_nodes' check cannot cover, which Dave concerned about.
Thanks,
Feng
> -Yunying
>
> -----Original Message-----
> From: Tang, Feng <feng.tang@intel.com>
> Sent: Thursday, 17 November, 2022 14:47
> To: Sun, Yunying <yunying.sun@intel.com>
> Cc: tglx@linutronix.de; peterz@infradead.org; paulmck@kernel.org; longman@redhat.com; x86@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] clocksource: Print clocksource name when clocksource is tested unstable
>
> On Wed, Nov 16, 2022 at 04:22:21PM +0800, Yunying Sun wrote:
> > 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:
>
> Hi Yunying,
>
> If the system's physical sockests number <= 2, I would suggest you to try the patch https://lore.kernel.org/lkml/20221021062131.1826810-1-feng.tang@intel.com/,
> which is still under review and discussion.
>
> Thanks,
> Feng
>
> > 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@intel.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
> >
prev parent reply other threads:[~2022-11-17 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 8:22 [PATCH] clocksource: Print clocksource name when clocksource is tested unstable Yunying Sun
2022-11-16 20:31 ` Paul E. McKenney
2022-11-17 1:12 ` Sun, Yunying
2022-11-17 6:46 ` Feng Tang
2022-11-17 8:03 ` Sun, Yunying
2022-11-17 8:35 ` Feng Tang [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=Y3XyX24/kuafuqGH@feng-clx \
--to=feng.tang@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yunying.sun@intel.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 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.