Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752720AbcKRIVK (ORCPT ); Fri, 18 Nov 2016 03:21:10 -0500 Received: from mail-wm0-f68.google.com ([74.125.82.68]:34587 "EHLO mail-wm0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752272AbcKRIVH (ORCPT ); Fri, 18 Nov 2016 03:21:07 -0500 Date: Fri, 18 Nov 2016 09:21:03 +0100 From: Ingo Molnar To: Bin Gao Cc: Thomas Gleixner , Ingo Molnar , H Peter Anvin , x86@kernel.org, Peter Zijlstra , linux-kernel@vger.kernel.org, Bin Gao Subject: Re: [PATCH 4/4] x86/tsc: set TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Atom SoCs Message-ID: <20161118082103.GB4425@gmail.com> References: <1479241644-234277-1-git-send-email-bin.gao@linux.intel.com> <1479241644-234277-5-git-send-email-bin.gao@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1479241644-234277-5-git-send-email-bin.gao@linux.intel.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1191 Lines: 33 * Bin Gao wrote: > TSC on Intel Atom SoCs capable of determining TSC frequency by MSR is > reliable and the frequency is known (because it's provided by HW). > On these platforms PIT/HPET is generally not available so > calibration won't work at all and also TSC is the only reliable > clocksource. So we set both X86_FEATURE_TSC_KNOWN_FREQ and > X86_FEATURE_TSC_RELIABLE flags to make sure the calibration is > skipped and no watchdog on TSC. > + /* > + * TSC frequency determined by MSR is always considered "known" > + * because it is reported by HW. > + * Another fact is that on MSR capable platforms, PIT/HPET is > + * generally not available so calibration won't work at all. > + */ > + setup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ); > + > + /* > + * Unfortunately there is no a HW way to report TSC is reliable. > + * We were told by silicon design team that TSC on Atom SoCs are > + * always "reliable". TSC is also the only reliable clocksource > + * on these SoCs (HPET is either not present or not functional) > + * so marke TSC reliable to avoid watchdog on it. minor nit: s/there is no a HW way/ there is no HW way Thanks, Ingo