Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759368AbcJTKBI (ORCPT ); Thu, 20 Oct 2016 06:01:08 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:47705 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759174AbcJTKBG (ORCPT ); Thu, 20 Oct 2016 06:01:06 -0400 Date: Thu, 20 Oct 2016 11:57:03 +0200 (CEST) From: Thomas Gleixner To: Bin Gao cc: Ingo Molnar , "H. Peter Anvin" , John Stultz , Peter Zijlstra , 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 In-Reply-To: <20161013231619.GA225074@worksta> Message-ID: References: <20160816174240.GA33372@worksta> <20160825164350.GA245186@worksta> <20161011211121.GA15041@worksta> <20161013231619.GA225074@worksta> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 617 Lines: 25 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); > + Right. That's what I wanted to see, but please split this into two patches: #1 Split the TSC flags #2 Set the flag for Goldmont We do not mix design changes with hw support changes. Thanks, tglx