linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: x86@kernel.org, jose.souza@intel.com, hpa@zytor.com,
	bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
	kai.heng.feng@canonical.com, bhelgaas@google.com,
	linux-pci@vger.kernel.org, rudolph@fb.com, xapienz@fb.com,
	bmilton@fb.com, paulmck@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] x86/intel: Disable HPET on another Intel Coffee Lake platform
Date: Wed, 29 Sep 2021 11:05:50 -0500	[thread overview]
Message-ID: <20210929160550.GA773748@bhelgaas> (raw)
In-Reply-To: <20210929061107.243699c2@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

On Wed, Sep 29, 2021 at 06:11:07AM -0700, Jakub Kicinski wrote:
> On Thu, 16 Sep 2021 19:46:48 -0700 Jakub Kicinski wrote:
> > My Lenovo T490s with i7-8665U had been marking TSC as unstable
> > since v5.13, resulting in very sluggish desktop experience...
> 
> Where do we stand? Waiting for tglx to refactor PC10 detection and use
> that, or just review delay?

From my point of view, this is an x86 issue, not a PCI one, so I'll
defer to the x86 folks.

> > +++ b/arch/x86/kernel/early-quirks.c
> > @@ -716,6 +716,8 @@ static struct chipset early_qrk[] __initdata = {
> >  		PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
> >  	{ PCI_VENDOR_ID_INTEL, 0x3e20,
> >  		PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
> > +	{ PCI_VENDOR_ID_INTEL, 0x3e34,
> > +		PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
> >  	{ PCI_VENDOR_ID_INTEL, 0x3ec4,
> >  		PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, force_disable_hpet},
> >  	{ PCI_VENDOR_ID_INTEL, 0x8a12,
> 

  reply	other threads:[~2021-09-29 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  2:46 [PATCH v2] x86/intel: Disable HPET on another Intel Coffee Lake platform Jakub Kicinski
2021-09-27 22:36 ` Krzysztof Wilczyński
2021-09-29 13:11 ` Jakub Kicinski
2021-09-29 16:05   ` Bjorn Helgaas [this message]
2021-09-30  9:08     ` Thomas Gleixner
2021-09-30 11:15       ` [PATCH RFT] x86/hpet: Use another crystalball to evaluate HPET usability Thomas Gleixner
2021-09-30 11:38         ` Rafael J. Wysocki
2021-09-30 17:07           ` Thomas Gleixner
2021-09-30 17:21             ` [PATCH RFT v2] " Thomas Gleixner
2021-09-30 17:50               ` Jakub Kicinski
2021-10-01 11:08               ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210929160550.GA773748@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=bmilton@fb.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jose.souza@intel.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kuba@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=rudolph@fb.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xapienz@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).