From: Nicolin Chen <nicolinc@nvidia.com>
To: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>
Cc: <nicoleotsuka@gmail.com>, <vdumpa@nvidia.com>,
<thierry.reding@gmail.com>, <linux-tegra@vger.kernel.org>,
<nwatterson@nvidia.com>, <Jonathan.Cameron@huawei.com>,
<jean-philippe@linaro.org>, <song.bao.hua@hisilicon.com>,
<eric.auger@redhat.com>, <thunder.leizhen@huawei.com>,
<yuzenghui@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<iommu@lists.linux-foundation.org>
Subject: [RFC][Patch v1 0/2] iommu/arm-smmu-v3: Add NVIDIA implementation
Date: Fri, 23 Jul 2021 12:31:38 -0700 [thread overview]
Message-ID: <20210723193140.9690-1-nicolinc@nvidia.com> (raw)
From: Nicolin Chen <nicoleotsuka@gmail.com>
The SMMUv3 devices implemented in the Grace SoC support NVIDIA's custom
CMDQ-Virtualization (CMDQV) hardware. Like the new ECMDQ feature first
introduced in the ARM SMMUv3.3 specification, CMDQV adds multiple VCMDQ
interfaces to supplement the single architected SMMU_CMDQ in an effort
to reduce contention.
This patch series adds CMDQV support to the arm-smmu-v3 driver by first
borrowing the implementation infrastructure from the arm-smmu driver.
The NVIDIA implementation is then introduced along with hooks allowing
implmentations to specify custom issue_cmdlist methods. Additionally,
the original issue_cmdlist and supporting methods in the arm-smmu-v3
driver are reworked to support alternative CMDQs.
[ nicolinc: this v1 is more of base changes for CMDQV driver; while I
am still integrating incremental features based on VFIO mdev, I sent
these two out in order to collect comments and suggestions to see if
the overall structure is promising. I will add more changes in v2 or
later versions for more detailed implementations. Thank you! ]
Nate Watterson (2):
iommu/arm-smmu-v3: Add implementation infrastructure
iommu/arm-smmu-v3: Add support for NVIDIA CMDQ-Virtualization hw
MAINTAINERS | 2 +
drivers/iommu/arm/arm-smmu-v3/Makefile | 2 +-
.../iommu/arm/arm-smmu-v3/arm-smmu-v3-impl.c | 15 +
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 71 +--
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 15 +
.../iommu/arm/arm-smmu-v3/nvidia-smmu-v3.c | 425 ++++++++++++++++++
6 files changed, 503 insertions(+), 27 deletions(-)
create mode 100644 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-impl.c
create mode 100644 drivers/iommu/arm/arm-smmu-v3/nvidia-smmu-v3.c
--
2.17.1
next reply other threads:[~2021-07-23 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 19:31 Nicolin Chen [this message]
2021-07-23 19:31 ` [RFC][Patch v1 1/2] iommu/arm-smmu-v3: Add implementation infrastructure Nicolin Chen
2021-07-23 19:31 ` [RFC][Patch v1 2/2] iommu/arm-smmu-v3: Add support for NVIDIA CMDQ-Virtualization hw Nicolin Chen
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=20210723193140.9690-1-nicolinc@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=nwatterson@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=song.bao.hua@hisilicon.com \
--cc=thierry.reding@gmail.com \
--cc=thunder.leizhen@huawei.com \
--cc=vdumpa@nvidia.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).