From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "Srivastava, Dheeraj Kumar" <dhsrivas@amd.com>,
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
Subject: Re: [PATCH 0/5] Improve the invalidation path in AMD
Date: Thu, 11 Jun 2026 17:32:27 +0200 [thread overview]
Message-ID: <airU7xpucwkZMAo7@8bytes.org> (raw)
In-Reply-To: <20260611115611.GE1066031@ziepe.ca>
On Thu, Jun 11, 2026 at 08:56:11AM -0300, Jason Gunthorpe wrote:
> Joerg?
This waits for regression test results from Vasant.
next prev parent reply other threads:[~2026-06-11 15:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:23 [PATCH 0/5] Improve the invalidation path in AMD Jason Gunthorpe
2026-03-27 15:23 ` [PATCH 1/5] iommu/amd: Simplify build_inv_address() Jason Gunthorpe
2026-03-30 7:39 ` Wei Wang
2026-03-30 12:05 ` Jason Gunthorpe
2026-03-31 2:01 ` Wei Wang
2026-03-27 15:23 ` [PATCH 2/5] iommu/amd: Pass last in through to build_inv_address() Jason Gunthorpe
2026-03-30 8:03 ` Wei Wang
2026-04-01 19:55 ` Jason Gunthorpe
2026-03-27 15:23 ` [PATCH 3/5] iommu/amd: Have amd_iommu_domain_flush_pages() use last Jason Gunthorpe
2026-04-01 6:33 ` Wei Wang
2026-03-27 15:23 ` [PATCH 4/5] iommu/amd: Make CMD_INV_IOMMU_ALL_PAGES_ADDRESS match the spec Jason Gunthorpe
2026-04-01 6:42 ` Wei Wang
2026-04-01 13:17 ` Jason Gunthorpe
2026-03-27 15:23 ` [PATCH 5/5] iommu/amd: Control INVALIDATE_IOMMU_PAGES PDE from the gather Jason Gunthorpe
2026-04-01 8:51 ` Wei Wang
2026-05-29 9:33 ` [PATCH 0/5] Improve the invalidation path in AMD Vasant Hegde
2026-06-02 7:06 ` Srivastava, Dheeraj Kumar
2026-06-11 11:56 ` Jason Gunthorpe
2026-06-11 15:32 ` Joerg Roedel [this message]
2026-06-11 16:33 ` Jason Gunthorpe
2026-06-12 7:48 ` Joerg Roedel
2026-06-12 12:27 ` Jason Gunthorpe
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=airU7xpucwkZMAo7@8bytes.org \
--to=joro@8bytes.org \
--cc=dhsrivas@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.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