From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S2999506AbdDZLkw (ORCPT <rfc822;w@1wt.eu>);
        Wed, 26 Apr 2017 07:40:52 -0400
Received: from mout.gmx.net ([212.227.17.21]:59095 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1954174AbdDZLkp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 26 Apr 2017 07:40:45 -0400
Message-ID: <1493206789.21594.25.camel@gmx.de>
Subject: Re: x86-tip tsc/tick gripage
From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
        "Paul E. McKenney" <paulmck@us.ibm.com>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
        Thomas Gleixner <tglx@linutronix.de>,
        Frederic Weisbecker <fweisbec@gmail.com>
Date: Wed, 26 Apr 2017 13:39:49 +0200
In-Reply-To: <20170426102617.l62cdn4gs4h5i4fw@hirez.programming.kicks-ass.net>
References: <1493193739.4412.30.camel@gmx.de>
         <1493194602.21594.4.camel@gmx.de>
         <20170426082137.koj7q3ftfqw3o22u@gmail.com>
         <1493195514.21594.5.camel@gmx.de> <1493197062.21594.8.camel@gmx.de>
         <20170426102617.l62cdn4gs4h5i4fw@hirez.programming.kicks-ass.net>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.16.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:sLoC2VDUkpdrXc3m3oYh91umPGBoy9BYeXmxQtwibD//Hxw3eoy
 mIRst1fRp0H7sSI7hggnmTNdG9kvve066tOh6HLySYiM3UZwdVeH+oO3swS4xX9DQ/5Dy3g
 KRdqi5mgflM6+lOsNQ9P13T6Mxit8AUD3M61z2Sf2FVbfnzpLezwsKxydrRnZGuoCTBetY9
 JsMhuh41P2RDZZA2fkOww==
X-UI-Out-Filterresults: notjunk:1;V01:K0:e7U2V2aRdho=:U0hqOvpJNY2Nd9xm1dcC2t
 nULTYKWqSrHcw9sgtZXOADcrxN6cuQqLvwPOywcTEIDlNbSq4r4XUmM1guhNb/nINN57x535k
 Rzxq8m1Hotp16n7dq+t/EqjrcsMXDEHCfBcuJAZdmQ2NxmCN7AGE16WerAvkX+A9SYIeIVkFt
 Q5ep5emHZz6mup0ogdHL3HpZPmaOV0/M26uLEixvFGKXaeuIJOthFtxKJTZ1f+HjrVZkj8I49
 xNjnHv2xwHrxGcticymTITmJlxBumuHHVNZmCM4ODfCJR2NQ6a92SVEJEx4QNmFxFwUKtWUPC
 LUYPmvuTF4O/gnjOxUQ6/16++gO0BoYjG1evc24sd/h/lU3ZHN4YzfvQZ+4upTVWx8wU7oZs6
 Op/IU2qn8B9sOUTe0RAsnZ0N0f/wjl19hwt/EbVN1WYSnOSN3w2qU6BU7qEV6vvhrPtpGN874
 5vSFnS976xcbuqKbHuXr06RDMoAgzhYC0J9YO93uf2aqAULigb1HkFTPRwpImLZOTsTi54Cbs
 mDZ76ZNlZaTg8o4iPJXXLXMVRdflPP2dnDkr8SLI1nv+rPKT12yJ8XIG8J9X/gHuJcg4kOBft
 cj18Sas7VxGZqLPrpf7I2nUNB5QXQ37roxIWw7iexRna7m7qmcncF747hUGWxhfnyMvVTwkv4
 HAzZbn1TYEAXB4spFjghen7uOUGxxIwa94iAlP5yuaonfHFshpJk3Ej09hi0bX9h5IySn5DJ3
 ciXqEo1Ej/ZCTuyf56uGja6d1ylH2jkDhR0Ntm+ovEjdupO9THz/epxbSTiHzVlngBX4CkV5W
 dFefJ8y
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 2017-04-26 at 12:26 +0200, Peter Zijlstra wrote:
> On Wed, Apr 26, 2017 at 10:57:42AM +0200, Mike Galbraith wrote:
> 
> > Both still lose their TSC.
> > 
> > [   11.982468] tsc: Refined TSC clocksource calibration: 2260.999 MHz
> > [   11.994275] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x20974a4d8bb, max_idle_ns: 440795246623 ns
> > [   13.064172] clocksource: Switched to clocksource tsc
> > [  240.247851] clocksource: timekeeping watchdog on CPU23: Marking clocksource 'tsc' as unstable because the skew is too large:
> > [  240.462501] clocksource:                       'tsc' cs_now: 108fe5be09f cs_last: b90a6a0676 mask: ffffffffffffffff
> > [  240.675057] tsc: Marking TSC unstable due to clocksource watchdog
> 
> 
> And they didn't use to? We don't typically write to TSC or TSC_ADJUST
> and thus would not cause such behaviour.

Nope.  The DL980 is my RT jitter test box, which I use all the time. 
 The other makes very spiffy jitter numbers when TSCs get synched up
(crap bios).. well used to before suse maintenance elves got around to
doing the BIOS replacement ;-/  (poor box, say hi to the goldfish)

	-Mike