Linux IOMMU Development
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, catalin.marinas@arm.com, joro@8bytes.org,
	jpb@kernel.org, iommu@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] iommu/arm-smmu-v3: Add HAFT support for SVA
Date: Tue, 28 Jul 2026 20:14:02 -0300	[thread overview]
Message-ID: <amk3uqotNdGpgc7J@nvidia.com> (raw)
In-Reply-To: <829b1d7eee64869d5c4231e80747367acb41b82b.1785153415.git.robin.murphy@arm.com>

On Mon, Jul 27, 2026 at 01:03:29PM +0100, Robin Murphy wrote:
> Since table access flags cannot be software-managed, if process
> pagetables are using HAFT then SVA must require the SMMU to support and
> enable it too, otherwise page aging is liable to get out of whack.
> 
> For unbinding, we can't disable HAFT atomically with HA as might be
> desired, but luckily we can get away with just not disabling HA either.
> 
> Cc: <stable@vger.kernel.org>
> Fixes: 62df5870ebf7 ("arm64: Enable ARCH_HAS_NONLEAF_PMD_YOUNG")
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> 
> v3: Make all HTTU settings unconditional WRT mm.

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason

  reply	other threads:[~2026-07-28 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 12:03 [PATCH v3 0/2] iommu/arm-smmu-v3: Fix SVA vs. HAFT issues Robin Murphy
2026-07-27 12:03 ` [PATCH v3 1/2] arm64: Add override for MMFR1.HAFDBS Robin Murphy
2026-07-28 10:03   ` Will Deacon
2026-07-28 10:12     ` Robin Murphy
2026-07-27 12:03 ` [PATCH v3 2/2] iommu/arm-smmu-v3: Add HAFT support for SVA Robin Murphy
2026-07-28 23:14   ` Jason Gunthorpe [this message]
2026-08-02 12:12 ` [PATCH v3 0/2] iommu/arm-smmu-v3: Fix SVA vs. HAFT issues Will Deacon

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=amk3uqotNdGpgc7J@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=catalin.marinas@arm.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=jpb@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robin.murphy@arm.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