From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>, Vasant Hegde <vasant.hegde@amd.com>
Cc: iommu@lists.linux.dev, Robin Murphy <robin.murphy@arm.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
patches@lists.linux.dev, Wei Wang <wei.w.wang@hotmail.com>
Subject: Re: [PATCH v3 0/5] Improve the invalidation path in AMD
Date: Thu, 28 May 2026 09:42:47 +0200 [thread overview]
Message-ID: <ahfx0OEnEEcYAxjc@8bytes.org> (raw)
In-Reply-To: <0-v3-233e3af938b7+f1-iommupt_inv_amd_jgg@nvidia.com>
On Wed, May 13, 2026 at 09:11:15PM -0300, Jason Gunthorpe wrote:
> Jason Gunthorpe (5):
> iommu/amd: Simplify build_inv_address()
> iommu/amd: Pass last in through to build_inv_address()
> iommu/amd: Have amd_iommu_domain_flush_pages() use last
> iommu/amd: Make CMD_INV_IOMMU_ALL_PAGES_ADDRESS match the spec
> iommu/amd: Control INVALIDATE_IOMMU_PAGES PDE from the gather
>
> drivers/iommu/amd/amd_iommu.h | 4 +-
> drivers/iommu/amd/amd_iommu_types.h | 2 +-
> drivers/iommu/amd/iommu.c | 176 +++++++++++++---------------
> drivers/iommu/amd/pasid.c | 2 +-
> 4 files changed, 87 insertions(+), 97 deletions(-)
Vasant, can you please help reviewing these changes?
Thanks,
Joerg
prev parent reply other threads:[~2026-05-28 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 0:11 [PATCH v3 0/5] Improve the invalidation path in AMD Jason Gunthorpe
2026-05-14 0:11 ` [PATCH v3 1/5] iommu/amd: Simplify build_inv_address() Jason Gunthorpe
2026-05-14 0:11 ` [PATCH v3 2/5] iommu/amd: Pass last in through to build_inv_address() Jason Gunthorpe
2026-05-14 0:11 ` [PATCH v3 3/5] iommu/amd: Have amd_iommu_domain_flush_pages() use last Jason Gunthorpe
2026-05-14 0:11 ` [PATCH v3 4/5] iommu/amd: Make CMD_INV_IOMMU_ALL_PAGES_ADDRESS match the spec Jason Gunthorpe
2026-05-14 0:11 ` [PATCH v3 5/5] iommu/amd: Control INVALIDATE_IOMMU_PAGES PDE from the gather Jason Gunthorpe
2026-05-28 7:42 ` Joerg Roedel [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=ahfx0OEnEEcYAxjc@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=wei.w.wang@hotmail.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