Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933064AbbKMUno (ORCPT ); Fri, 13 Nov 2015 15:43:44 -0500 Received: from casper.infradead.org ([85.118.1.10]:47564 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932859AbbKMUnn (ORCPT ); Fri, 13 Nov 2015 15:43:43 -0500 Date: Fri, 13 Nov 2015 21:43:38 +0100 From: Peter Zijlstra To: Gratian Crisan Cc: Josh Hunt , Thomas Gleixner , LKML , Ingo Molnar , "H . Peter Anvin" , x86@kernel.org, Borislav Petkov , Josh Cartwright , gratian@gmail.com Subject: Re: [RFC PATCH] tsc: synchronize TSCs on buggy Intel Xeon E5 CPUs with offset error Message-ID: <20151113204338.GA9928@worktop.ger.corp.intel.com> References: <1447099142-10220-1-git-send-email-gratian.crisan@ni.com> <20151109220232.GO17308@twins.programming.kicks-ass.net> <87mvultz5f.fsf@spline.amer.corp.natinst.com> <87io58tufu.fsf@spline.amer.corp.natinst.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87io58tufu.fsf@spline.amer.corp.natinst.com> User-Agent: Mutt/1.5.22.1 (2013-10-16) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 828 Lines: 16 On Wed, Nov 11, 2015 at 09:41:25AM -0600, Gratian Crisan wrote: > I also wrote a small C utility[1], with a bit of code borrowed from the > kernel, for reading the TSC on all CPUs. It starts a high priority > thread per CPU, tries to synchronize them and prints out the TSC values > and their offset with regards to CPU0. > It can be called from a SysV init shell script[2] at the beginning of > the boot process and right before a reboot to save the values in a file. Could you also read and print TSC_ADJUST (msr 0x3b) ? This would tell us if for example your BIOS messed it up. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/