From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1437530AbdDZMbF (ORCPT ); Wed, 26 Apr 2017 08:31:05 -0400 Received: from mout.gmx.net ([212.227.15.19]:65375 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1432644AbdDZMa4 (ORCPT ); Wed, 26 Apr 2017 08:30:56 -0400 Message-ID: <1493209836.21594.29.camel@gmx.de> Subject: Re: x86-tip tsc/tick gripage From: Mike Galbraith To: Peter Zijlstra Cc: Ingo Molnar , "Paul E. McKenney" , LKML , Ingo Molnar , Thomas Gleixner , Frederic Weisbecker Date: Wed, 26 Apr 2017 14:30:36 +0200 In-Reply-To: <1493206789.21594.25.camel@gmx.de> 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> <1493206789.21594.25.camel@gmx.de> 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:Xx5PLc9ud2qRfCusLRnyeHslJSfGKF+Pkhlg+CBV+BJX1XgjVkC eBHUcLlYwH+bo2TQbUDMAQOsqVonFVTDmzAEE903HYcRxBEweesiVGlKFVgNpyeu4JwAvrw bByllmGKf7aI7oLzAQq6HD4blVlbAKoIhe8tRLHA5hBgimkmZ3j0vojxZNUSkghd3BBI+q3 u8JdZTc8/424t8A3RWwKg== X-UI-Out-Filterresults: notjunk:1;V01:K0:I0od3KFsAAc=:X0LN3S7q+xM0tQ6c6jh46q mCIl7+xuV5+a4RDauLKGVLqUYvv/8JhyJCh0zUHbVFk/X8Y11m87oXIuMI4lP0B3qcbMESoj5 o0yls6IlvO1NOqvce7+woSJ4YJ/8tOI62vafmOwx5cVkhy07iu6p1PgRGK7YSLmOB215C71V2 AWu/b4oW3GanpAhyJZv0baL8mn6LEQCSW+PkrZtjF1WbkQn4wLf4yK+4VHPQmzE6vX5NKgW2X /07bz4IwCFxt57S0jWoXiNf5gWyJg/rzwLyfse53lBVC+RKcfB9euQyO6kAAoSON3Cz6qXJqw v3IFMIy3fNxPdqm2Exgw/lMr9EzLt897jImblD49cWuEIKjo2Z/amrWI9oWh37dEViK83DSlY zH5+NPrFIRzUc+WYSAD18pY1PfAcrou3tolAm9MSin7ieYxFTRfqtoYkwaaHiKzQO0H18GkyQ 9JIf12zqEes630UFhItP8uMjGzq9dZzXt3OnsdWi9TmI6rgD8/CSRT9sQrJzCiGhBL/RnvzQg TlOEaqLCiwuXqsPn+Y1AdFM2NeJnI01xRfcB10UfxOj3LYVI18cBO1VgmGfHdUjJjuwHC+nH4 jV9pXK1w1mvuORrOlP6J+8G1wrSnWpSTxA8Lcn7IhO5rw8menQ3DOcXSFSIqjjwIpN6LfH8c2 i5fnlEHkql/ElGaL6WPda5pxX+78TA5jxrtw1uHisTTfJo155E+r50gZW/nnnatC88tTbj6bY WRPG3SxzrgZ/Lz4ufX0vGfUznBPKe0HlrmnppN0ywTTY9fPGct5WtTQPNUuTdHplsORALg6u1 xs+4qNe Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2017-04-26 at 13:39 +0200, Mike Galbraith wrote: > 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. DL980 seems perfectly happy with master.today.. so off we go.