Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759532AbcJTKRw (ORCPT ); Thu, 20 Oct 2016 06:17:52 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:44597 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756792AbcJTKRv (ORCPT ); Thu, 20 Oct 2016 06:17:51 -0400 Date: Thu, 20 Oct 2016 12:17:47 +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: <20161020101747.GT3102@twins.programming.kicks-ass.net> References: <20160816174240.GA33372@worksta> <20160825164350.GA245186@worksta> <20161011211121.GA15041@worksta> <20161013231619.GA225074@worksta> 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: 689 Lines: 21 On Thu, Oct 20, 2016 at 11:57:03AM +0200, Thomas Gleixner wrote: > On Thu, 13 Oct 2016, Bin Gao wrote: > > @@ -702,6 +702,15 @@ unsigned long native_calibrate_tsc(void) > > } > > } > > > > + setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ); > > + > > + /* > > + * For Atom SoCs TSC is the only reliable clocksource. > > + * Mark TSC reliable so no watchdog on it. > > + */ > > + if (boot_cpu_data.x86_model == INTEL_FAM6_ATOM_GOLDMONT) > > + setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); > > + AFAICT setting TSC_RELIABLE also skips the check_tsc_warp() tests in tsc_sync.c. This means that if someone does a Goldmont BIOS with 'features', we'll never detect the wreckage :-/