From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [RFC PATCH 1/1] PCI: Add Extended Tag + MRRS quirk for Xeon 6
Date: Fri, 7 Mar 2025 09:34:43 +0100 [thread overview]
Message-ID: <Z8qvo0_tuSbwwyIY@wunner.de> (raw)
In-Reply-To: <20250304135108.2599-1-ilpo.jarvinen@linux.intel.com>
On Tue, Mar 04, 2025 at 03:51:08PM +0200, Ilpo Järvinen wrote:
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -5564,6 +5564,33 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0144, quirk_no_ext_tags);
> DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0420, quirk_no_ext_tags);
> DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_SERVERWORKS, 0x0422, quirk_no_ext_tags);
>
> +static void quirk_pcie2x_no_tags_no_mrrs(struct pci_dev *pdev)
> +{
> + struct pci_host_bridge *bridge = pci_find_host_bridge(pdev->bus);
> + u32 linkcap;
> +
> + if (!bridge)
> + return;
I note that in a lot of places where pci_find_host_bridge() is called,
no NULL pointer check is performed. So omitting it would appear
to be safe.
The quirk is x86-specific, so compiling it into the kernel on other
arches creates unnecessary bloat. Avoid by moving to arch/x86/pci/fixup.c.
There should definitely be a multi-line code comment above the function
explaining what defect this works around (slower performance apparently),
and also link to the PDF document.
BTW the PDF document says "Intel Confidential", I'm wondering why this
has been made public without stripping the confidentiality marker...
Thanks,
Lukas
next prev parent reply other threads:[~2025-03-07 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:51 [RFC PATCH 1/1] PCI: Add Extended Tag + MRRS quirk for Xeon 6 Ilpo Järvinen
2025-03-04 21:14 ` Bjorn Helgaas
2025-03-05 20:38 ` Dan Williams
2025-03-07 13:06 ` Ilpo Järvinen
2025-03-07 16:39 ` Bjorn Helgaas
2025-03-07 20:50 ` Dan Williams
2025-03-07 8:34 ` Lukas Wunner [this message]
2025-03-07 13:13 ` Ilpo Järvinen
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=Z8qvo0_tuSbwwyIY@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.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