From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4B96DC3F68F for ; Fri, 24 Jan 2020 08:35:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1BB7D2071A for ; Fri, 24 Jan 2020 08:35:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729861AbgAXIfd (ORCPT ); Fri, 24 Jan 2020 03:35:33 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:41770 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbgAXIfd (ORCPT ); Fri, 24 Jan 2020 03:35:33 -0500 Received: from [5.158.153.53] (helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iuuQq-0006yO-Sc; Fri, 24 Jan 2020 09:35:13 +0100 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id 680F0103089; Fri, 24 Jan 2020 09:35:12 +0100 (CET) To: Hans de Goede , Andy Shevchenko , vipul kumar Cc: Daniel Lezcano , linux-kernel@vger.kernel.org, Stable , Srikanth Krishnakar , Cedric Hombourger , x86@kernel.org, Len Brown , Vipul Kumar Subject: Re: [v3] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Bay Trail SoC In-Reply-To: References: <1579617717-4098-1-git-send-email-vipulk0511@gmail.com> <87eevs7lfd.fsf@nanos.tec.linutronix.de> <878slzeeim.fsf@nanos.tec.linutronix.de> <20200123144108.GU32742@smile.fi.intel.com> From: Thomas Gleixner Date: Fri, 24 Jan 2020 09:35:12 +0100 Message-ID: <87iml11ccf.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hans, Hans de Goede writes: > Hi, > > Sorry for top posting, but this is a long and almost unreadable thread ... > > So it seems to me that a better fix would be to change the freq_desc_byt struct from: > > static const struct freq_desc freq_desc_byt = { > 1, { 83300, 100000, 133300, 116700, 80000, 0, 0, 0 } > }; > > to: > > static const struct freq_desc freq_desc_byt = { > 1, { 83333, 100000, 133300, 116700, 80000, 0, 0, 0 } > }; > > That should give us the right TSC frequency without needing to mess with > the TSC_KNOWN_FREQ and TSC_RELIABLE flags. Where does that number come from? Just math? Thanks, tglx