From: Peter Zijlstra <peterz@infradead.org>
To: Feng Tang <feng.tang@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
paulmck@kernel.org, rui.zhang@intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, bin.gao@intel.com
Subject: Re: [PATCH RFC] x86/tsc: Make recalibration default on for TSC_KNOWN_FREQ cases
Date: Tue, 23 May 2023 10:11:15 +0200 [thread overview]
Message-ID: <20230523081115.GG4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <ZGwUXzGcMgbcZVnf@feng-clx>
On Tue, May 23, 2023 at 09:18:23AM +0800, Feng Tang wrote:
> On Mon, May 22, 2023 at 06:11:58PM +0200, Peter Zijlstra wrote:
> > On Mon, May 22, 2023 at 11:20:15PM +0800, Feng Tang wrote:
> >
> > > And I don't understand the commit log: "On Intel GOLDMONT Atom SoC
> > > TSC is the only reliable clocksource. We mark TSC reliable to avoid
> > > watchdog on it."
> > >
> > > Clearly the Denventon I found today has both HPET and ACPI_PM timer:
> > >
> > > [root@dnv0 ~]# grep . /sys/devices/system/clocksource/clocksource0/*
> > > /sys/devices/system/clocksource/clocksource0/available_clocksource:tsc hpet acpi_pm
> > > /sys/devices/system/clocksource/clocksource0/current_clocksource:tsc
> > >
> > > The lscpu info is:
> > >
> > > Architecture: x86_64
> > > CPU op-mode(s): 32-bit, 64-bit
> > > Address sizes: 39 bits physical, 48 bits virtual
> > > Byte Order: Little Endian
> > > CPU(s): 12
> > > On-line CPU(s) list: 0-11
> > > Vendor ID: GenuineIntel
> > > BIOS Vendor ID: Intel(R) Corporation
> > > Model name: Intel(R) Atom(TM) CPU C3850 @ 2.10GHz
> > > BIOS Model name: Intel(R) Atom(TM) CPU C3850 @ 2.10GHz CPU @ 2.1GHz
> > > BIOS CPU family: 43
> > > CPU family: 6
> > > Model: 95
> > > Thread(s) per core: 1
> > > Core(s) per socket: 12
> > > Socket(s): 1
> > > Stepping: 1
> > >
> > > Maybe this cpu model (0x5F) has been used by some type of platforms
> > > which has met the false alarm watchdog issue.
> >
> > It has them; but they are not *reliable*.
>
> Yes, that's possible. I tried to CC the author Bin in case he can
> provide more background or information for his statement, but his
> email address is unreachable now.
IIRC HPET stops in C10 or something stupid like that, I forgot what the
problem with ACPI_PM is.
next prev parent reply other threads:[~2023-05-23 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 3:30 [PATCH RFC] x86/tsc: Make recalibration default on for TSC_KNOWN_FREQ cases Feng Tang
2023-05-22 8:14 ` Thomas Gleixner
2023-05-22 8:47 ` Feng Tang
2023-05-22 11:49 ` Thomas Gleixner
2023-05-22 13:00 ` Feng Tang
2023-05-22 14:31 ` Thomas Gleixner
2023-05-22 15:20 ` Feng Tang
2023-05-22 16:11 ` Peter Zijlstra
2023-05-23 1:18 ` Feng Tang
2023-05-23 8:11 ` Peter Zijlstra [this message]
2023-05-23 14:31 ` Feng Tang
2023-06-02 18:29 ` Paul E. McKenney
2023-06-02 18:36 ` Dave Hansen
2023-06-02 19:08 ` Paul E. McKenney
2023-06-05 1:04 ` Feng Tang
2023-06-08 16:58 ` Paul E. McKenney
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=20230523081115.GG4253@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bin.gao@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=feng.tang@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox