From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, subhransu.s.prusty@intel.com,
kevin.b.stanton@intel.com, akataria@vmware.com,
john.stultz@linaro.org, christopher.s.hall@intel.com,
Ingo Molnar <mingo@kernel.org>
Subject: Re: x86/tsc: Fix ART for TSC_KNOWN_FREQ
Date: Mon, 13 Mar 2017 21:12:14 +0100 [thread overview]
Message-ID: <20170313201214.GD3328@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1703131951400.3712@nanos>
On Mon, Mar 13, 2017 at 08:04:14PM +0100, Thomas Gleixner wrote:
> On Mon, 13 Mar 2017, Peter Zijlstra wrote:
>
> >
> > Subhransu reported that convert_art_to_tsc() isn't working for him.
> >
> > It turns out that because of commit:
> >
> > 57779dc2b3b7 ("x86, tsc: Skip refined tsc calibration on systems with reliable TSC")
>
> That's the wrong culprit. The problem was introduced with the ART support
> patches. I fixed the changelog up.
Right; thanks for untangling that history.
> > Systems with TSC_KNOWN_FREQ (due to having CPUID.15h) will not run the
> > refined calibration thing, and then forget to set the ART clocksource
> > relation.
> >
> > We cannot set the ART relation prior to running the refined calibration;
> > therefore duplicate the lines.
> >
> > XXX: should we clear this in mark_tsc_unstable() ?
>
> It's already handled. get_device_system_timestamp() which convert ART to
> clock monotonic checks whether the timekeeper clocksource is the same as
> the correlated ART clocksource, i.e. TSC. So when timekeeping switches away
> from TSC get_device_system_timestamp() returns -ENODEV.
Ah right. Couldn't find that in a hurry.
prev parent reply other threads:[~2017-03-13 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 14:57 x86/tsc: Fix ART for TSC_KNOWN_FREQ Peter Zijlstra
2017-03-13 18:55 ` [tip:x86/urgent] " tip-bot for Peter Zijlstra
2017-03-13 19:04 ` Thomas Gleixner
2017-03-13 20:12 ` Peter Zijlstra [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=20170313201214.GD3328@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akataria@vmware.com \
--cc=christopher.s.hall@intel.com \
--cc=john.stultz@linaro.org \
--cc=kevin.b.stanton@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=subhransu.s.prusty@intel.com \
--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