From: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
To: 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, gankulkarni@os.amperecomputing.com
Subject: [PATCH 0/2] Add support to enable ATS on VFs independently.
Date: Mon, 27 Feb 2023 05:21:49 -0800 [thread overview]
Message-ID: <20230227132151.1907480-1-gankulkarni@os.amperecomputing.com> (raw)
As discussed in [1], adding a helper function to configure the STU of an
ATS capability. Function pci_ats_stu_configure() can be called to program
the STU while enumerating the PF, to support scenarios like PF is not
enabled with ATS, whereas VFs can enable it.
In SMMU-V3 driver, calling pci_ats_stu_configure() to confgiure the STU
while enumerating a PF in passthrough mode.
[1] https://lore.kernel.org/linux-arm-kernel/20230221154624.GA3701506@bhelgaas/T/
Ganapatrao Kulkarni (2):
PCI/ATS: Add a helper function to configure ATS STU of a PF.
iommu/arm-smmu-v3: Configure STU of a PF if ATS is not enabled.
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 25 +++++++++++++++-
drivers/pci/ats.c | 32 +++++++++++++++++++--
include/linux/pci-ats.h | 1 +
3 files changed, 55 insertions(+), 3 deletions(-)
--
2.38.1
next reply other threads:[~2023-02-27 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 13:21 Ganapatrao Kulkarni [this message]
2023-02-27 13:21 ` [PATCH 1/2] PCI/ATS: Add a helper function to configure ATS STU of a PF Ganapatrao Kulkarni
2023-02-27 19:29 ` Sathyanarayanan Kuppuswamy
2023-02-28 2:53 ` Ganapatrao Kulkarni
2023-02-28 3:08 ` Sathyanarayanan Kuppuswamy
2023-02-28 3:25 ` Ganapatrao Kulkarni
2023-02-27 13:21 ` [PATCH 2/2] iommu/arm-smmu-v3: Configure STU of a PF if ATS is not enabled Ganapatrao Kulkarni
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=20230227132151.1907480-1-gankulkarni@os.amperecomputing.com \
--to=gankulkarni@os.amperecomputing.com \
--cc=bhelgaas@google.com \
--cc=darren@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
all inboxes | Powered by JetHome®