Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2778778ybl; Thu, 29 Aug 2019 12:47:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqxRFaVgWwljdz8dqVG0qwa5F1ZLe0jflMN7NZ/1mb0ObYc284voTrQozYUyBApVjpzijh1U X-Received: by 2002:a17:902:33c1:: with SMTP id b59mr11909581plc.104.1567108069070; Thu, 29 Aug 2019 12:47:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567108069; cv=none; d=google.com; s=arc-20160816; b=XafjQE1CYIoZUNC8lr1rcbJU7SgHgDp0d3xxGmR91vN2lUazQ+1y8cDYigZcHi68z+ 9JhoHObCRqrjBJU34tPcqljCmn+0z6YY1vnh6GrkQFrotuprvzfoYiORfa+O5FUkwsvr 3jdMnCC5YVER74CZVNV3W7Df7qgghnSKR/Uz/tGBfDfc9t0dwe0r1ixD3p9lELFWae1E Et+Gk9mY895ZTe3y562gueolGSEYb90SPXy+PfvlQKDgNtjIMy9HR+eFE6ayFxzHXxHy qa/Df+dCYYJyHhAux080qX7osAArV9iJYPLulMwLDn/TdXcJcCqbYQTVNpAmOrFiG0La pHnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=nMYzwcR2cFPjwQfU8WX1w89iR1BNP+CD4ydOAHrGyLs=; b=ESalHgI24IlwrJVRIKcZqma0eRwCflxKQE7TPdPj9mG2kw7TLKPkUkSj8fbTWjXJji Rty1atQCRorgOMzZjopWPA164GzOhy/F2sHaKkNOyTMw//OFWGgUkRM4yf1qvjxNGme5 QbURehEcEnpxasjpAMYRSaIqDC/ntzr4Bkii+RtMSTJ1fUVUzQygJFDUERtFfgxFJMg8 D4BrlXYbIpYa87EPx/VmPp2r+qpKRp4l2fFxj9+NTijkve3igItBiWRSV8Elo3YHukmf tR1/+Wp83RsaPJde0LrZSA6hrH+5mkSIQ08rceB7WSLJzJgb7dSxP01TKSY8MB9R3SVT y2LA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d23si2974806pjv.24.2019.08.29.12.47.32; Thu, 29 Aug 2019 12:47:49 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728109AbfH2TpK (ORCPT + 99 others); Thu, 29 Aug 2019 15:45:10 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:51658 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727859AbfH2TpK (ORCPT ); Thu, 29 Aug 2019 15:45:10 -0400 Received: from p5de0b6c5.dip0.t-ipconnect.de ([93.224.182.197] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1i3QLt-00062x-9g; Thu, 29 Aug 2019 21:45:01 +0200 Date: Thu, 29 Aug 2019 21:45:00 +0200 (CEST) From: Thomas Gleixner To: Kai-Heng Feng cc: Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , harry.pan@intel.com, x86@kernel.org, LKML , Dave Hansen Subject: Re: [PATCH] x86/hpet: Disable HPET on Intel Coffe Lake In-Reply-To: <793CCD4F-35E0-46B9-B5D4-3D3233BA5D35@canonical.com> Message-ID: References: <20190829091232.15065-1-kai.heng.feng@canonical.com> <793CCD4F-35E0-46B9-B5D4-3D3233BA5D35@canonical.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-342921159-1567107901=:1938" 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 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-342921159-1567107901=:1938 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Thu, 29 Aug 2019, Kai-Heng Feng wrote: > at 20:13, Thomas Gleixner wrote: > > On Thu, 29 Aug 2019, Kai-Heng Feng wrote: > > > > > Some Coffee Lake platforms have skewed HPET timer once the SoCs entered > > > PC10, and marked TSC as unstable clocksource as result. > > > > So here you talk about Coffee Lake and in the patch you use KABYLAKE. > > Coffeelake has the same model number as Kabylake. Yeah, just a bit more text explaining that would be helpful. > > > +static const struct x86_cpu_id hpet_blacklist[] __initconst = { > > > + { X86_VENDOR_INTEL, 6, INTEL_FAM6_KABYLAKE_MOBILE }, > > > + { X86_VENDOR_INTEL, 6, INTEL_FAM6_KABYLAKE_DESKTOP }, > > > > So this disables HPET on all Kaby Lake variants not just on the affected > > Coffee Lakes. I know that I rejected the initial patch with the random > > stepping cutoff... > > > > https://lore.kernel.org/lkml/alpine.DEB.2.21.1904081403220.1748@nanos.tec.linutronix.de > > > > In the other attempt to 'fix' this I asked for clarification, but silence > > from Intel after this: > > > > https://lore.kernel.org/lkml/alpine.DEB.2.21.1905182015320.3019@nanos.tec.linutronix.de > > > > Can Intel please provide some useful information about this finally? > > Hopefully Intel can provide more info. > > I know we should find the root cause rather than stopping at "it’s a firmware > bug”, but users are already affected by this issue [1]. > Is there any better short-term workaround? Not really. And if Intel stays silent, I'm just going to apply it as is along with a stable tag. Thanks, tglx --8323329-342921159-1567107901=:1938--