From: Mostafa Saleh <smostafa@google.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, jpb@kernel.org,
will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
nicolinc@nvidia.com, praan@google.com
Subject: Re: [PATCH] iommu/arm-smmu-v3-sva: Relax ASID requirements
Date: Tue, 8 Sep 2026 08:38:58 +0000 [thread overview]
Message-ID: <ap_JokRTsUHtF4dN@google.com> (raw)
In-Reply-To: <20260907184513.GA2543240@ziepe.ca>
On Mon, Sep 07, 2026 at 03:45:13PM -0300, Jason Gunthorpe wrote:
> On Mon, Sep 07, 2026 at 03:49:28PM +0000, Mostafa Saleh wrote:
> > arm_smmu_sva_supported() have some residual checks for ASID from the
> > original commit d744f9e6c222 ("iommu/arm-smmu-v3: Check for SVA features")
> >
> > As DVM was used for TLB invalidation and the ASID of the domain was shared
> > with the CPU process.
> >
> > However, the commit
> > d38c28dbefee ("iommu/arm-smmu-v3: Put the SVA mmu notifier in the smmu_domain")
> > removed that support.
> >
> > So matching the SMMU ASID space to the CPU is unnecessary and can be
> > relaxed.
> >
> > Remove the CPU ASID related code, and update the print for the SMMUv3.
>
> It is OK, but maybe this could also be but under an if
> ARM_SMMU_FEAT_BTM? That is never enabled and is a placeholder to for
> eventual BTM support.
Yes, otherwise SMMUs with BTM would regress in the future.
But I’d assume non-BTM SMMUs will still be supported; falling back
to SW invalidation?
Thanks,
Mostafa
>
> Once we get the last part of the invs code the BTM support can come
> back in.
>
> Jasson
next prev parent reply other threads:[~2026-09-08 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 15:49 [PATCH] iommu/arm-smmu-v3-sva: Relax ASID requirements Mostafa Saleh
2026-09-07 18:45 ` Jason Gunthorpe
2026-09-08 8:38 ` Mostafa Saleh [this message]
2026-09-08 12:42 ` 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=ap_JokRTsUHtF4dN@google.com \
--to=smostafa@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=praan@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.