Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Bjorn Helgaas" <helgaas@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Lukas Wunner <lukas@wunner.de>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] PCI: Add Extended Tag + MRRS quirk for Xeon 6
Date: Tue, 22 Apr 2025 15:24:16 -0700	[thread overview]
Message-ID: <6808171089b0f_71fe294d0@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <20250422200857.GA381276@bhelgaas>

Bjorn Helgaas wrote:
[..]
> v1/rfc: https://lore.kernel.org/all/20250304135108.2599-1-ilpo.jarvinen@linux.intel.com/
> 
> I suppose it's quixotic to hope for anything better than quirks that
> have to be added or updated for every new processor that comes along.
> 
> ACPI _HPX might be a possible way for the platform to tell us what to
> do here.  ACPI r6.5, sec 6.2.9 says it's for hot-added devices and
> "Functions not configured by the platform firmware during initial
> system boot" (how are we supposed to determine that?)  In any case,
> Linux does evaluate _HPX for every device in pci_configure_device().
> 
> I'm not sure _HPX really works; it's very general, and I would expect
> to see reports of problems if firmware really tried to use it.
> 
> Or, I guess a _DSM function would be a possible way to communicate
> this.

Ok, I am reading this as "Maintainer asserts the quirk is unsavory,
please make this be something that Linux can ask the platform firmware
if it needs to apply, or make existing _HPX just work. Either of those
is preferable to a new entry in the quirk table."

  reply	other threads:[~2025-04-22 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 13:02 [PATCH v2 1/1] PCI: Add Extended Tag + MRRS quirk for Xeon 6 Ilpo Järvinen
2025-04-22 20:08 ` Bjorn Helgaas
2025-04-22 22:24   ` Dan Williams [this message]
2025-04-22 20:15 ` Ingo Molnar
2025-05-01  8:57 ` Lukas Wunner
2025-06-01 17:22 ` Manivannan Sadhasivam
2025-06-02  5:10   ` Ilpo Järvinen
2025-06-02  6:29     ` Manivannan Sadhasivam

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=6808171089b0f_71fe294d0@dwillia2-xfh.jf.intel.com.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=hpa@zytor.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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