From: Will Deacon <will@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
iommu@lists.linux.dev, "Joerg Roedel (AMD)" <joro@8bytes.org>,
Jean-Philippe Brucker <jpb@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
David Matlack <dmatlack@google.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
patches@lists.linux.dev, Pranjal Shrivastava <peaan@google.com>,
Pranjal Shrivastava <praan@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
Mostafa Saleh <smostafa@google.com>,
Vijayanand Jitta <vijayanand.jitta@oss.qualcomm.com>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH v8 0/9] Organize the SMMUv3 invalidation flow so iommupt can use it
Date: Sun, 4 Oct 2026 17:50:41 +0100 [thread overview]
Message-ID: <179112946237.2363163.15333874894190883676.b4-ty@kernel.org> (raw)
In-Reply-To: <0-v8-1eaaed5e0433+3d3d2d-smmu_tlbi_jgg@nvidia.com>
On Fri, 02 Oct 2026 22:23:19 -0300, Jason Gunthorpe wrote:
> [ This is part of the patch pile to move SMMUv3 over to the generic page
> table, the precursor patches have been merged now. What's left:
> 1) Organize the SMMUv3 invalidation flow so iommupt can use it
> 2) Use the generic iommu page table for SMMUv3
>
> The first patch should ideally go to -rc
>
> [...]
Applied first seven to iommu (arm/smmu/updates), thanks!
[1/9] iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA
https://git.kernel.org/iommu/c/84c6089a365f
[2/9] iommu/arm-smmu-v3: Pass the parameters for the invalidation in a struct
https://git.kernel.org/iommu/c/0a6cd4ac9252
[3/9] iommu/arm-smmu-v3: Move pgsize out of arm_smmu_inv
https://git.kernel.org/iommu/c/a9573c2847e9
[4/9] iommu/arm-smmu-v3: Optimize range invalidation for latency
https://git.kernel.org/iommu/c/5a158b29766c
[5/9] iommu/arm-smmu-v3: Keep track in arm_smmu_invs if range invalidation is used
https://git.kernel.org/iommu/c/fc62cd069cf7
[6/9] iommu/arm-smmu-v3: Precompute the invalidation commands
https://git.kernel.org/iommu/c/bc5c3475d63c
[7/9] iommu/arm-smmu-v3: Populate the tlbi at the top of the call chain
https://git.kernel.org/iommu/c/d587faf66828
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2026-10-04 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 1:23 [PATCH v8 0/9] Organize the SMMUv3 invalidation flow so iommupt can use it Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 1/9] iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 2/9] iommu/arm-smmu-v3: Pass the parameters for the invalidation in a struct Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 3/9] iommu/arm-smmu-v3: Move pgsize out of arm_smmu_inv Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 4/9] iommu/arm-smmu-v3: Optimize range invalidation for latency Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 5/9] iommu/arm-smmu-v3: Keep track in arm_smmu_invs if range invalidation is used Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 6/9] iommu/arm-smmu-v3: Precompute the invalidation commands Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 7/9] iommu/arm-smmu-v3: Populate the tlbi at the top of the call chain Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 8/9] iommu/arm-smmu-v3: Change how the tlbi describes the invalidation Jason Gunthorpe
2026-10-04 13:43 ` Will Deacon
2026-10-04 17:00 ` Jason Gunthorpe
2026-10-03 1:23 ` [PATCH v8 9/9] iommu/arm-smmu-v3: Support the DS expansion of range invalidation SCALE Jason Gunthorpe
2026-10-04 16:50 ` Will Deacon [this message]
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=179112946237.2363163.15333874894190883676.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jic23@kernel.org \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolinc@nvidia.com \
--cc=pasha.tatashin@soleen.com \
--cc=patches@lists.linux.dev \
--cc=peaan@google.com \
--cc=praan@google.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@google.com \
--cc=smostafa@google.com \
--cc=vijayanand.jitta@oss.qualcomm.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