Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2365637ybl; Thu, 29 Aug 2019 07:17:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqzdi6rIoQh8ihiC/+zUaxey//0lnuYE1V9kHgh2pDnd+5K8r7EvXLjl/cIhVyOvoE0HbWQ7 X-Received: by 2002:a17:90a:c68c:: with SMTP id n12mr10269809pjt.29.1567088272006; Thu, 29 Aug 2019 07:17:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567088271; cv=none; d=google.com; s=arc-20160816; b=ehuSOJeolpQOrEsgTCVDRYoXhfqZnAxQ8SzwzBB9L0rkSJ6m3UpK2cRvWXRjcSv903 qT+sxD/JfvjDAQVbm1D42qkiFSZtX8RbjNd8/EXeDsmPzrEOnsmxR4wIxp2rzBtcVqS+ GfmmaX+lVCUQoKqmLKlj4dPth4z1c02Z7WwIXNwQWA5XmIoou124AOGgCp3l5y11i/u9 gcrpE8aRrGLBy7h1rFZ6z/R7uVTQ4+hkxRhQ5P66sZNjzOlC0d4yFhM79i8cPKS6I+LG QtqSszjbNWOnW7N+pntfgOdsUGmpgaAUIVlgL0V4JLDoEpyBwFx0aHXvmdXFBPzU+oh0 xB7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version; bh=GYvTdCfNIJLEcLEkMMRAs0zx2HzNWruXtOTwWsJt6vs=; b=fUyKvF/0NqAihEju6IStZ2NAvN5THA5DieAD8jAcei0rJVgNgNYcNUipF7f06WaJet /O96KAXB77P6SypBkFedXY9aJ8moylynrLzkOYAKdpgyfSWtLrOMCFspwEMRPmDgqO7m 6zuLO/mHK1+ev6Nmt03Y7znSJx2AR2yzeGmWkZ5rfQTJK1ZRCyTO07L3cNZV7FKXDjsQ CKKIeeB9hHjcw1pKgrwU9JlBeetxqyAjBBsP67Q5caUGZer4U6U/oYj+PJWSMB/dQyAK sQ7ksNf/pf8bN/vdc7ix086cTNXu3ZxbYOTO9a/OVPZoLCeUgBRqNPj6fNZMFi3b7pVh 0EsQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h6si2060771pgc.202.2019.08.29.07.17.33; Thu, 29 Aug 2019 07:17:51 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727684AbfH2OPq (ORCPT + 99 others); Thu, 29 Aug 2019 10:15:46 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:50278 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727046AbfH2OPp (ORCPT ); Thu, 29 Aug 2019 10:15:45 -0400 Received: from mail-pf1-f197.google.com ([209.85.210.197]) by youngberry.canonical.com with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from ) id 1i3LBF-0003Tp-Tp for linux-kernel@vger.kernel.org; Thu, 29 Aug 2019 14:13:42 +0000 Received: by mail-pf1-f197.google.com with SMTP id w30so2604395pfj.4 for ; Thu, 29 Aug 2019 07:13:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=GYvTdCfNIJLEcLEkMMRAs0zx2HzNWruXtOTwWsJt6vs=; b=abwSaSpZqebjwHdPv9/4ps72SU4ZLzImo5DolK+Csax72fiFHLJ8FN/90K1bi9zlRz l46VL2LQ7396aO/LlPuLtx7NHkLnhsF5vcUrVPhPy9dGtS+Rf25Kpz4BjtvZZO0Rva2+ oZk62u0ZLcRzyf9CmcalHXyIGd/QX2qcTuMIR8wR4jts79I140fP9Cvmb15uk1ByCAGp q6gIEVEMb2swwWJLwswkHnUVGgPjTNi9XlPR1Ad0f6sRkrl9ShLYKgTTDBMCRO+/0HrY CAADs8vZsjGvphCWSxRWCkONNEEl8JgUkqREScAQ6ZKTicJ20Wb6O0S09QwxAWqttGiz uLng== X-Gm-Message-State: APjAAAX9tq43/gZVgRFWdmOunFY//dp9M0VxYyB5/RUl7WjvmS82nzhZ F3EmHKA31+q/OsFMZxyIZays6liFrOmtmQbJRzYI13Jy6v2GdjoqXrQE2WKf3ZmNrVZ72IGTj+o U5sVbV1ZdQdXFbKDZm8yV+J72UTKwgAXacHsfax/Aog== X-Received: by 2002:a17:902:d24:: with SMTP id 33mr10186221plu.133.1567088020649; Thu, 29 Aug 2019 07:13:40 -0700 (PDT) X-Received: by 2002:a17:902:d24:: with SMTP id 33mr10186190plu.133.1567088020335; Thu, 29 Aug 2019 07:13:40 -0700 (PDT) Received: from 2001-b011-380f-3c42-c1f6-ed57-34d8-2c76.dynamic-ip6.hinet.net (2001-b011-380f-3c42-c1f6-ed57-34d8-2c76.dynamic-ip6.hinet.net. [2001:b011:380f:3c42:c1f6:ed57:34d8:2c76]) by smtp.gmail.com with ESMTPSA id m125sm3373273pfm.139.2019.08.29.07.13.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Aug 2019 07:13:39 -0700 (PDT) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [PATCH] x86/hpet: Disable HPET on Intel Coffe Lake From: Kai-Heng Feng In-Reply-To: Date: Thu, 29 Aug 2019 22:13:32 +0800 Cc: Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , harry.pan@intel.com, x86@kernel.org, LKML , Dave Hansen Content-Transfer-Encoding: 8bit Message-Id: <793CCD4F-35E0-46B9-B5D4-3D3233BA5D35@canonical.com> References: <20190829091232.15065-1-kai.heng.feng@canonical.com> To: Thomas Gleixner X-Mailer: Apple Mail (2.3445.104.11) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > >> Harry Pan identified it's a firmware bug [1]. >> >> To prevent creating a circular dependency between HPET and TSC, let's >> disable HPET on affected platforms. >> >> [1]: >> https://lore.kernel.org/lkml/20190516090651.1396-1-harry.pan@intel.com/ >> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203183 > > Please use Link:// for reference not [1] and not Bugzilla: Ok. > >> +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? [1] https://bugzilla.kernel.org/show_bug.cgi?id=204537 Kai-Heng > > Thanks, > > tglx