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=-3.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, 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 AE392C43603 for ; Wed, 18 Dec 2019 16:26:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7655424650 for ; Wed, 18 Dec 2019 16:26:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576686371; bh=UvJV5+V5GLxfdacULy68GLBFVz/DGrDdaw3cACZWHcQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=FA+K7GZVzVIVI51LC9wxkpUMGGNkZD76MpSH6vXri8k9QZP1dn6fSFt5gdUCb26Dp cgGtnMnHBPXDkdGS/BEmrW5FvGylHuHNKtk9ULi5UV6udq8yfMmmqy1zjGKks5xppf tEB2Y3QBmX+JkWKeLtHqrq1mzghwKf2rV0cpvlSI= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727737AbfLRQ0K (ORCPT ); Wed, 18 Dec 2019 11:26:10 -0500 Received: from mail.kernel.org ([198.145.29.99]:60460 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727397AbfLRQ0I (ORCPT ); Wed, 18 Dec 2019 11:26:08 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DD28B227BF; Wed, 18 Dec 2019 16:26:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576686368; bh=UvJV5+V5GLxfdacULy68GLBFVz/DGrDdaw3cACZWHcQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=1wxC876a3n7CpULPIipSeOs97JkwwYdJEYVfc4Zku80A7YWvdkiP2ebrQZjvkVqF2 kFPmjEoYlMyCUZ/il8b7C0zGilgDyHoY56/Egirz2+3hEGDAUzZepUk5H/E8OX3BLW /Oz0m25SbUjJaVmp8EKwOszq4Vii1bymymw8YOEs= Date: Wed, 18 Dec 2019 17:26:06 +0100 From: Greg KH To: Vipul Kumar Cc: Daniel Lezcano , Thomas Gleixner , linux-kernel@vger.kernel.org, Stable , Srikanth Krishnakar , Cedric Hombourger , Vipul Kumar Subject: Re: [PATCH] x86/tsc: Unset TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Bay Trail SoC Message-ID: <20191218162606.GC482612@kroah.com> References: <1576683039-5311-1-git-send-email-vipulk0511@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1576683039-5311-1-git-send-email-vipulk0511@gmail.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 18, 2019 at 09:00:39PM +0530, Vipul Kumar wrote: > From: Vipul Kumar > > 'commit f3a02ecebed7 ("x86/tsc: Set TSC_KNOWN_FREQ and TSC_RELIABLE > flags on Intel Atom SoCs")', causing time drift for Bay trail SoC. > These flags are set for SoCs having cpuid_level 0x15 or more. > Bay trail is having cpuid_level 0xb. > > So, unset both flags to make sure the clocksource calibration can > be done. > > Signed-off-by: Vipul Kumar > --- > arch/x86/kernel/tsc_msr.c | 3 +++ > 1 file changed, 3 insertions(+) This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly.