From: Bjorn Helgaas <helgaas@kernel.org>
To: Mengyuan Lou <mengyuanlou@net-swift.com>
Cc: netdev@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Add ACS quirk for Wangxun NICs
Date: Mon, 13 Feb 2023 18:07:10 -0600 [thread overview]
Message-ID: <20230214000710.GA2951479@bhelgaas> (raw)
In-Reply-To: <20230207102419.44326-1-mengyuanlou@net-swift.com>
On Tue, Feb 07, 2023 at 06:24:19PM +0800, Mengyuan Lou wrote:
> Wangxun has verified there is no peer-to-peer between functions for the
> below selection of SFxxx, RP1000 and RP2000 NICS.
> They may be multi-function device, but the hardware does not advertise
> ACS capability.
>
> Add an ACS quirk for these devices so the functions can be in
> independent IOMMU groups.
>
> Signed-off-by: Mengyuan Lou <mengyuanlou@net-swift.com>
Applied to pci/virtualization for v6.3, thanks!
> ---
> drivers/pci/quirks.c | 22 ++++++++++++++++++++++
> include/linux/pci_ids.h | 2 ++
> 2 files changed, 24 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 285acc4aaccc..13290048beda 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4835,6 +4835,26 @@ static int pci_quirk_brcm_acs(struct pci_dev *dev, u16 acs_flags)
> PCI_ACS_SV | PCI_ACS_RR | PCI_ACS_CR | PCI_ACS_UF);
> }
>
> +/*
> + * Wangxun 10G/1G NICs have no ACS capability, and on multi-function
> + * devices, peer-to-peer transactions are not be used between the functions.
> + * So add an ACS quirk for below devices to isolate functions.
> + * SFxxx 1G NICs(em).
> + * RP1000/RP2000 10G NICs(sp).
> + */
> +static int pci_quirk_wangxun_nic_acs(struct pci_dev *dev, u16 acs_flags)
> +{
> + switch (dev->device) {
> + case 0x0100 ... 0x010F:
> + case 0x1001:
> + case 0x2001:
> + return pci_acs_ctrl_enabled(acs_flags,
> + PCI_ACS_SV | PCI_ACS_RR | PCI_ACS_CR | PCI_ACS_UF);
> + }
> +
> + return false;
> +}
> +
> static const struct pci_dev_acs_enabled {
> u16 vendor;
> u16 device;
> @@ -4980,6 +5000,8 @@ static const struct pci_dev_acs_enabled {
> { PCI_VENDOR_ID_NXP, 0x8d9b, pci_quirk_nxp_rp_acs },
> /* Zhaoxin Root/Downstream Ports */
> { PCI_VENDOR_ID_ZHAOXIN, PCI_ANY_ID, pci_quirk_zhaoxin_pcie_ports_acs },
> + /* Wangxun nics */
> + { PCI_VENDOR_ID_WANGXUN, PCI_ANY_ID, pci_quirk_wangxun_nic_acs },
> { 0 }
> };
>
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index b362d90eb9b0..bc8f484cdcf3 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -3012,6 +3012,8 @@
> #define PCI_DEVICE_ID_INTEL_VMD_9A0B 0x9a0b
> #define PCI_DEVICE_ID_INTEL_S21152BB 0xb152
>
> +#define PCI_VENDOR_ID_WANGXUN 0x8088
> +
> #define PCI_VENDOR_ID_SCALEMP 0x8686
> #define PCI_DEVICE_ID_SCALEMP_VSMP_CTL 0x1010
>
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-02-14 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 10:24 [PATCH] PCI: Add ACS quirk for Wangxun NICs Mengyuan Lou
2023-02-07 17:38 ` Simon Horman
2023-02-08 2:16 ` mengyuanlou
2023-02-08 8:20 ` Simon Horman
2023-02-14 0:07 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 10:47 Mengyuan Lou
2023-02-01 15:37 ` Bjorn Helgaas
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=20230214000710.GA2951479@bhelgaas \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).