From: Leon Romanovsky <leon@kernel.org>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
bhelgaas@google.com, jean-philippe@linaro.org,
darren@os.amperecomputing.com, scott@os.amperecomputing.com
Subject: Re: [PATCH] PCI/ATS: Allow to enable ATS on VFs even if it is not enabled on PF
Date: Sun, 12 Feb 2023 20:14:48 +0200 [thread overview]
Message-ID: <Y+ksmNWJdWNkGAU9@unreal> (raw)
In-Reply-To: <20230208184321.867666-1-gankulkarni@os.amperecomputing.com>
On Wed, Feb 08, 2023 at 10:43:21AM -0800, Ganapatrao Kulkarni wrote:
> As per PCIe specification(section 10.5), If a VF implements an
> ATS capability, its associated PF must implement an ATS capability.
> The ATS Capabilities in VFs and their associated PFs are permitted to
> be enabled independently.
> Also, it states that the Smallest Translation Unit (STU) for VFs must be
> hardwired to Zero and the associated PF's value applies to VFs STU.
>
> The current code allows to enable ATS on VFs only if it is already
> enabled on associated PF, which is not necessary as per the specification.
>
> It is only required to have valid STU programmed on PF to enable
> ATS on VFs. Adding code to write the first VFs STU to a PF's STU
> when PFs ATS is not enabled.
Can you please add here quotes from the spec and its version? I don't see
anything like this in my version of PCIe specification.
Thanks
>
> Signed-off-by: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
> ---
> drivers/pci/ats.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pci/ats.c b/drivers/pci/ats.c
> index f9cc2e10b676..a97ec67201d1 100644
> --- a/drivers/pci/ats.c
> +++ b/drivers/pci/ats.c
> @@ -67,13 +67,20 @@ int pci_enable_ats(struct pci_dev *dev, int ps)
> if (ps < PCI_ATS_MIN_STU)
> return -EINVAL;
>
> - /*
> - * Note that enabling ATS on a VF fails unless it's already enabled
> - * with the same STU on the PF.
> - */
> ctrl = PCI_ATS_CTRL_ENABLE;
> if (dev->is_virtfn) {
> pdev = pci_physfn(dev);
> +
> + if (!pdev->ats_enabled &&
> + (pdev->ats_stu < PCI_ATS_MIN_STU)) {
> + u16 ctrl2;
> +
> + /* Associated PF's STU value applies to VFs. */
> + pdev->ats_stu = ps;
> + ctrl2 = PCI_ATS_CTRL_STU(pdev->ats_stu - PCI_ATS_MIN_STU);
> + pci_write_config_word(pdev, pdev->ats_cap + PCI_ATS_CTRL, ctrl2);
> + }
> +
> if (pdev->ats_stu != ps)
> return -EINVAL;
> } else {
> --
> 2.39.1
>
next prev parent reply other threads:[~2023-02-12 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 18:43 [PATCH] PCI/ATS: Allow to enable ATS on VFs even if it is not enabled on PF Ganapatrao Kulkarni
2023-02-12 18:14 ` Leon Romanovsky [this message]
2023-02-15 20:57 ` Bjorn Helgaas
2023-02-16 7:26 ` Leon Romanovsky
2023-02-16 7:46 ` Leon Romanovsky
2023-02-16 10:47 ` Jean-Philippe Brucker
2023-02-16 10:23 ` Joerg Roedel
2023-02-16 11:12 ` Jean-Philippe Brucker
2023-02-16 11:36 ` Ganapatrao Kulkarni
2023-02-21 9:13 ` Ganapatrao Kulkarni
2023-02-21 15:46 ` Bjorn Helgaas
2023-02-23 15:45 ` Jean-Philippe Brucker
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=Y+ksmNWJdWNkGAU9@unreal \
--to=leon@kernel.org \
--cc=bhelgaas@google.com \
--cc=darren@os.amperecomputing.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=jean-philippe@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=scott@os.amperecomputing.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