From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Alex Shi <alex.shi@intel.com>,
tglx@linutronix.de, hpa@linux.intel.com,
tim.c.chen@linux.intel.com, linux-kernel@vger.kernel.org,
andi.kleen@intel.com, mingo@elte.hu
Subject: Re: [URGENT rfc patch 0/3] tsc clocksource bug fix
Date: Fri, 5 Jul 2013 16:38:33 +0200 [thread overview]
Message-ID: <20130705143833.GT23916@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAFTL4hy24+=2++CN5rBhn9v+pvxR+tTja9Z-wRLSS__LGQBWaQ@mail.gmail.com>
On Fri, Jul 05, 2013 at 04:23:33PM +0200, Frederic Weisbecker wrote:
> Nope, I haven't touched that. I prefer not to fiddle with unstable
> clocksource for now :)
>
> As for unstable TSCs, if sched_clock_tick() needs to be fed, we simply
> don't stop the tick.
Not entirely the same thing; I thought the clocksource watchdog was ran
even when we have a 'stable' TSC, just to make sure it stays stable.
There's known cases where the BIOS f*cks us over and wrecks TSC sync.
next prev parent reply other threads:[~2013-07-05 14:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 5:34 Alex Shi
2013-07-04 5:34 ` [PATCH 1/3] clocksource: clean up clocksource_select Alex Shi
2013-07-04 9:57 ` Thomas Gleixner
2013-07-04 10:21 ` Alex Shi
2013-07-04 10:27 ` Thomas Gleixner
2013-07-05 1:22 ` Alex Shi
2013-07-04 5:34 ` [PATCH 2/3] clockesource: set override clocksource Alex Shi
2013-07-04 10:23 ` Thomas Gleixner
2013-07-04 5:34 ` [PATCH 3/3] clocksource: fix can not set tsc as clocksource bug Alex Shi
2013-07-04 10:55 ` Thomas Gleixner
2013-07-04 13:04 ` Thomas Gleixner
2013-07-04 20:46 ` [PATCH] clocksource: Reselect clocksource when watchdog validated Thomas Gleixner
2013-07-05 1:38 ` Alex Shi
2013-07-05 9:13 ` [tip:timers/core] clocksource: Reselect clocksource when watchdog validated high-res capability tip-bot for Thomas Gleixner
2013-07-05 2:48 ` [PATCH 3/3] clocksource: fix can not set tsc as clocksource bug Alex Shi
2013-07-05 5:41 ` Thomas Gleixner
2013-07-05 6:44 ` Alex Shi
2013-07-04 7:58 ` [URGENT rfc patch 0/3] tsc clocksource bug fix Peter Zijlstra
2013-07-04 8:13 ` Alex Shi
2013-07-05 14:23 ` Frederic Weisbecker
2013-07-05 14:38 ` Peter Zijlstra [this message]
2013-07-05 15:24 ` Thomas Gleixner
2013-07-05 21:22 ` Peter Zijlstra
2013-07-05 21:50 ` Thomas Gleixner
2013-07-05 21:58 ` Borislav Petkov
2013-07-05 22:17 ` Thomas Gleixner
2013-07-06 8:37 ` Borislav Petkov
2013-07-06 10:50 ` Peter Zijlstra
2013-07-04 11:00 ` Thomas Gleixner
2013-07-04 18:11 ` Davidlohr Bueso
2013-07-04 20:27 ` Thomas Gleixner
2013-07-05 1:12 ` Alex Shi
2013-07-05 5:58 ` Thomas Gleixner
2013-07-05 6:28 ` Alex Shi
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=20130705143833.GT23916@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alex.shi@intel.com \
--cc=andi.kleen@intel.com \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®