From: Peter Zijlstra <peterz@infradead.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
x86@kernel.org, jose.souza@intel.com, hpa@zytor.com,
bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
kai.heng.feng@canonical.com, bhelgaas@google.com,
linux-pci@vger.kernel.org, rudolph@fb.com, xapienz@fb.com,
bmilton@fb.com, stable@vger.kernel.org
Subject: Re: [PATCH] x86/intel: Disable HPET on another Intel Coffee Lake platform
Date: Fri, 17 Sep 2021 11:11:49 +0200 [thread overview]
Message-ID: <YURb1bzc3L4gNI9Q@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210916150707.GA1611532@bjorn-Precision-5520>
On Thu, Sep 16, 2021 at 10:07:07AM -0500, Bjorn Helgaas wrote:
> This seems to be an ongoing issue, not just a point defect in a single
> product, and I really hate the onesy-twosy nature of this. Is there
> really no way to detect this issue automatically or fix whatever Linux
> bug makes us trip over this? I am no clock expert, so I have
> absolutely no idea whether this is possible.
X86 is gifted with the grant total of _0_ reliable clocks. Given no
accurate time, it is impossible to tell which one of them is broken
worst. Although I suppose we could attempt to synchronize against the
PMU or MPERF..
We could possibly disable the tsc watchdog for
X86_FEATURE_TSC_KNOWN_FREQ && X86_FEATURE_TSC_ADJUST I suppose.
And then have people with 'creative' BIOS get to keep the pieces.
next prev parent reply other threads:[~2021-09-17 9:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 13:17 [PATCH] x86/intel: Disable HPET on another Intel Coffee Lake platform Jakub Kicinski
2021-09-16 15:07 ` Bjorn Helgaas
2021-09-16 15:30 ` Jakub Kicinski
2021-09-16 16:35 ` Paul E. McKenney
2021-09-17 2:57 ` Jakub Kicinski
2021-09-17 3:33 ` Paul E. McKenney
2021-09-17 9:11 ` Peter Zijlstra [this message]
2021-09-17 9:34 ` Peter Zijlstra
2021-09-19 0:14 ` Thomas Gleixner
2021-09-21 18:05 ` Rafael J. Wysocki
2021-09-21 20:18 ` Thomas Gleixner
2021-09-22 20:27 ` Rafael J. Wysocki
2021-09-22 22:21 ` Thomas Gleixner
2021-09-23 10:46 ` Rafael J. Wysocki
2021-09-17 14:00 ` Krzysztof Wilczyński
2021-09-17 14:58 ` Jakub Kicinski
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=YURb1bzc3L4gNI9Q@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bhelgaas@google.com \
--cc=bmilton@fb.com \
--cc=bp@alien8.de \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=jose.souza@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rudolph@fb.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xapienz@fb.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