From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
joro@8bytes.org, bhelgaas@google.com, robin.murphy@arm.com,
will@kernel.org
Cc: jean-philippe@linaro.org, darren@os.amperecomputing.com,
scott@os.amperecomputing.com
Subject: Re: [PATCH v2 1/2] PCI/ATS: Add a helper function to configure ATS STU of a PF
Date: Tue, 28 Feb 2023 08:30:24 -0800 [thread overview]
Message-ID: <eefaf1bc-586b-aa0f-8899-fcce0460b733@linux.intel.com> (raw)
In-Reply-To: <20230228042137.1941024-2-gankulkarni@os.amperecomputing.com>
On 2/27/23 8:21 PM, Ganapatrao Kulkarni wrote:
> As per PCI specification (PCI Express Base Specification Revision
> 6.0, Section 10.5) both PF and VFs of a PCI EP are permitted to be enabled
> independently for ATS capability, however the STU(Smallest Translation
> Unit) is shared between PF and VFs. For VFs, it is hardwired to Zero and
> the associated PF's value applies to VFs.
>
> In the current code, the STU is being configured while enabling the PF ATS.
> Hence, it is not able to enable ATS for VFs, if it is not enabled on the
> associated PF already.
>
> Adding a function pci_ats_stu_configure(), which can be called to
> configure the STU during PF enumeration.
> Latter enumerations of VFs can successfully enable ATS independently.
>
> Signed-off-by: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
> ---
> drivers/pci/ats.c | 33 +++++++++++++++++++++++++++++++--
> include/linux/pci-ats.h | 3 +++
> 2 files changed, 34 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/ats.c b/drivers/pci/ats.c
> index f9cc2e10b676..1611bfa1d5da 100644
> --- a/drivers/pci/ats.c
> +++ b/drivers/pci/ats.c
> @@ -46,6 +46,35 @@ bool pci_ats_supported(struct pci_dev *dev)
> }
> EXPORT_SYMBOL_GPL(pci_ats_supported);
>
> +/**
> + * pci_ats_stu_configure - Configure STU of a PF.
> + * @dev: the PCI device
> + * @ps: the IOMMU page shift
> + *
> + * Returns 0 on success, or negative on failure.
> + */
> +int pci_ats_stu_configure(struct pci_dev *dev, int ps)
> +{
> + u16 ctrl;
> +
> + if (dev->ats_enabled || dev->is_virtfn)
> + return 0;
Is PF allowed to re-configure STU if there are other active
VF's which uses it?
> +
> + if (!pci_ats_supported(dev))
> + return -EINVAL;
> +
> + if (ps < PCI_ATS_MIN_STU)
> + return -EINVAL;
> +
> + dev->ats_stu = ps;
> + pci_read_config_word(dev, dev->ats_cap + PCI_ATS_CTRL, &ctrl);
> + ctrl |= PCI_ATS_CTRL_STU(dev->ats_stu - PCI_ATS_MIN_STU);
> + pci_write_config_word(dev, dev->ats_cap + PCI_ATS_CTRL, ctrl);
> +
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(pci_ats_stu_configure);
> +
> /**
> * pci_enable_ats - enable the ATS capability
> * @dev: the PCI device
> @@ -68,8 +97,8 @@ int pci_enable_ats(struct pci_dev *dev, int ps)
> return -EINVAL;
>
> /*
> - * Note that enabling ATS on a VF fails unless it's already enabled
> - * with the same STU on the PF.
> + * Note that enabling ATS on a VF fails unless it's already
> + * configured with the same STU on the PF.
> */
> ctrl = PCI_ATS_CTRL_ENABLE;
> if (dev->is_virtfn) {
> diff --git a/include/linux/pci-ats.h b/include/linux/pci-ats.h
> index df54cd5b15db..7d62a92aaf23 100644
> --- a/include/linux/pci-ats.h
> +++ b/include/linux/pci-ats.h
> @@ -8,6 +8,7 @@
> /* Address Translation Service */
> bool pci_ats_supported(struct pci_dev *dev);
> int pci_enable_ats(struct pci_dev *dev, int ps);
> +int pci_ats_stu_configure(struct pci_dev *dev, int ps);
> void pci_disable_ats(struct pci_dev *dev);
> int pci_ats_queue_depth(struct pci_dev *dev);
> int pci_ats_page_aligned(struct pci_dev *dev);
> @@ -16,6 +17,8 @@ static inline bool pci_ats_supported(struct pci_dev *d)
> { return false; }
> static inline int pci_enable_ats(struct pci_dev *d, int ps)
> { return -ENODEV; }
> +static inline int pci_ats_stu_configure(struct pci_dev *d, int ps)
> +{ return -ENODEV; }
> static inline void pci_disable_ats(struct pci_dev *d) { }
> static inline int pci_ats_queue_depth(struct pci_dev *d)
> { return -ENODEV; }
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2023-02-28 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 4:21 [PATCH v2 0/2] Add support to enable ATS on VFs independently Ganapatrao Kulkarni
2023-02-28 4:21 ` [PATCH v2 1/2] PCI/ATS: Add a helper function to configure ATS STU of a PF Ganapatrao Kulkarni
2023-02-28 16:30 ` Sathyanarayanan Kuppuswamy [this message]
2023-03-08 8:54 ` Ganapatrao Kulkarni
2023-03-13 21:12 ` Bjorn Helgaas
2023-03-13 22:30 ` Sathyanarayanan Kuppuswamy
2023-03-13 22:42 ` Bjorn Helgaas
2023-03-14 10:08 ` Ganapatrao Kulkarni
2023-03-14 12:52 ` Sathyanarayanan Kuppuswamy
2023-03-14 14:36 ` Ganapatrao Kulkarni
2023-03-14 16:02 ` Bjorn Helgaas
2023-03-14 16:50 ` Sathyanarayanan Kuppuswamy
2023-03-14 17:10 ` Bjorn Helgaas
2023-03-14 18:01 ` Ganapatrao Kulkarni
2023-03-14 18:12 ` Sathyanarayanan Kuppuswamy
2023-03-14 21:17 ` Bjorn Helgaas
2023-03-15 4:22 ` Sathyanarayanan Kuppuswamy
2023-03-15 14:30 ` Ganapatrao Kulkarni
2023-02-28 4:21 ` [PATCH v2 2/2] iommu/arm-smmu-v3: Configure STU of a PF if ATS is not enabled Ganapatrao Kulkarni
2023-03-13 14:19 ` Ganapatrao Kulkarni
2023-03-02 4:24 ` [PATCH v2 0/2] Add support to enable ATS on VFs independently Sathyanarayanan Kuppuswamy
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=eefaf1bc-586b-aa0f-8899-fcce0460b733@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=darren@os.amperecomputing.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=scott@os.amperecomputing.com \
--cc=will@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).