Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754216AbcJUFrY (ORCPT ); Fri, 21 Oct 2016 01:47:24 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:39574 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750856AbcJUFrW (ORCPT ); Fri, 21 Oct 2016 01:47:22 -0400 Date: Fri, 21 Oct 2016 07:47:17 +0200 From: Peter Zijlstra To: Thomas Gleixner Cc: Bin Gao , Ingo Molnar , "H. Peter Anvin" , John Stultz , x86@kernel.org, linux-kernel@vger.kernel.org, bin.gao@intel.com Subject: Re: [PATCH v3] x86/tsc: add X86_FEATURE_TSC_KNOWN_FREQ flag Message-ID: <20161021054717.GZ3102@twins.programming.kicks-ass.net> References: <20160825164350.GA245186@worksta> <20161011211121.GA15041@worksta> <20161013231619.GA225074@worksta> <20161020101747.GT3102@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 745 Lines: 17 On Thu, Oct 20, 2016 at 09:37:50PM +0200, Thomas Gleixner wrote: > Well, we have the same issue on other platforms/models which set the > reliable flag. I was not aware we had other platforms doing this, git grep tells me intel-mid does this as well.. > So one sanity check we can do is to read the IA32_TSC_ADJUST MSR on all > cores. They should all have the same value (usually 0) or at least have a > very minimal delta. If that's off by more than 1us then something is fishy > especially on single socket systems. We could at least WARN about it. > > We could do this in idle occasionally as well, so we can detect the dreaded > "SMI wants to hide the cycles" crapola. Indeed, that sounds like the best we can; and probably should; do.