From: Jason Gunthorpe <jgg@nvidia.com>
To: Weinan Liu <wnliu@google.com>
Cc: iommu@lists.linux.dev, joro@8bytes.org, josef@toxicpanda.com,
kpsingh@kernel.org, patches@lists.linux.dev,
robin.murphy@arm.com, suravee.suthikulpanit@amd.com,
wei.w.wang@hotmail.com, will@kernel.org
Subject: Re: [PATCH v1 1/1] iommu/amd: Don't split flush for amd_iommu_domain_flush_all()
Date: Fri, 17 Apr 2026 08:57:10 -0300 [thread overview]
Message-ID: <20260417115710.GD761338@nvidia.com> (raw)
In-Reply-To: <20260415003046.2275802-1-wnliu@google.com>
On Wed, Apr 15, 2026 at 12:30:46AM +0000, Weinan Liu wrote:
> We have observed multiple full invalidations occurring during device
> detach when we are done using the vfio-device.
>
> blocked_domain_attach_device()
> -> detach_device()
> -> amd_iommu_domain_flush_all()
> -> amd_iommu_domain_flush_pages(..., CMD_INV_IOMMU_ALL_PAGES_ADDRESS)
>
> while (size != 0) {
>
> -> __domain_flush_pages( flush_size /* power of 2 flush_size */)
> -> domain_flush_pages_v1()
> -> build_inv_iommu_pages()
> -> build_inv_address()
>
> }
>
> build_inv_address() will trigger a full invalidation if the chunk
> size > (1 << 51). Consequently, the guest will issue multiple full
> invalidations for a single call to amd_iommu_domain_flush_all()
>
> Without this patch, we will see 10 time instead of 1 time full
> invalidations for every amd_iommu_domain_flush_all().
>
> Fixes: a270be1b3fdf ("iommu/amd: Use only natural aligned flushes in a VM")
>
> Suggested-by: Josef Bacik <josef@toxicpanda.com>
> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Weinan Liu <wnliu@google.com>
> ---
> drivers/iommu/amd/iommu.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2026-04-17 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 21:06 [PATCH v1 0/1] Don't split flush for amd_iommu_domain_flush_all() Weinan Liu
2026-04-14 21:06 ` [PATCH v1 1/1] iommu/amd: " Weinan Liu
2026-04-14 23:36 ` Jason Gunthorpe
2026-04-15 0:30 ` Weinan Liu
2026-04-17 11:57 ` Jason Gunthorpe [this message]
2026-04-14 23:55 ` Samiullah Khawaja
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=20260417115710.GD761338@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=josef@toxicpanda.com \
--cc=kpsingh@kernel.org \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=wei.w.wang@hotmail.com \
--cc=will@kernel.org \
--cc=wnliu@google.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