From: Peter Zijlstra <peterz@infradead.org>
To: "Liu, Changcheng" <changcheng.liu@intel.com>
Cc: tglx@linutronix.de, hpa@zytor.com, douly.fnst@cn.fujitsu.com,
linux-kernel@vger.kernel.org, "Stanton,
Kevin B" <kevin.b.stanton@intel.com>
Subject: Re: [PATCH] x86/ioapic: don't use unstable TSC to detect timer IRQ
Date: Tue, 20 Mar 2018 10:09:31 +0100 [thread overview]
Message-ID: <20180320090931.GQ4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180320085835.GA56497@sofia>
On Tue, Mar 20, 2018 at 04:58:35PM +0800, Liu, Changcheng wrote:
> On 09:49 Tue 20 Mar, Peter Zijlstra wrote:
> > On Tue, Mar 20, 2018 at 04:42:55PM +0800, Liu, Changcheng wrote:
> > > In rare case, the TSC is every unstable or can't sync with
> > > real time hardware clock.
> >
> > However did you manage that? Please provide _FAR_ more details.
> [Changcheng] TSC is simulated and HPET is hardware implemented.
> TSC can't sync with HPET. When running linux, the TSC grows too
> fast and HPET can't trigger periodic timer interrupt in time which
> is used to update jiffies.
How is that not utterly broken, and how is that even allowed behaviour
as per the SDM ?
If the TSC is so utterly broken as to not function according to spec,
you should not advertise the TSC, at which point you'll find that it is
_very_ hard to run modern linux on x86 without TSC.
next prev parent reply other threads:[~2018-03-20 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 8:42 [PATCH] x86/ioapic: don't use unstable TSC to detect timer IRQ Liu, Changcheng
2018-03-20 8:49 ` Peter Zijlstra
2018-03-20 8:58 ` Liu, Changcheng
2018-03-20 9:03 ` Thomas Gleixner
2018-03-20 9:09 ` Peter Zijlstra [this message]
2018-03-20 9:00 ` Thomas Gleixner
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=20180320090931.GQ4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=changcheng.liu@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=kevin.b.stanton@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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