From: Nicolin Chen <nicolinc@nvidia.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
<jpb@kernel.org>, <praan@google.com>, <miko.lenczewski@arm.com>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: Re: [PATCH v1 2/9] iommu/arm-smmu-v3: Add alloc_id/free_id functions to arm_smmu_invs
Date: Fri, 19 Dec 2025 12:56:17 -0800 [thread overview]
Message-ID: <aUW78ZV2D5aM75yN@Asurada-Nvidia> (raw)
In-Reply-To: <20251219170551.GF254720@nvidia.com>
On Fri, Dec 19, 2025 at 01:05:51PM -0400, Jason Gunthorpe wrote:
> On Thu, Dec 18, 2025 at 12:26:48PM -0800, Nicolin Chen wrote:
> > @@ -720,6 +723,9 @@ struct arm_smmu_invs {
> > rwlock_t rwlock;
> > bool has_ats;
> > struct rcu_head rcu;
> > + struct arm_smmu_domain *smmu_domain;
> > + int (*alloc_id)(struct arm_smmu_inv *inv, void *data);
> > + void (*free_id)(struct arm_smmu_inv *inv, bool flush);
> > struct arm_smmu_inv inv[] __counted_by(max_invs);
> > };
>
> I'm not keen on this at all..
>
> On the allocation side everything should be stored inside the
> invalidation list, we don't need function callbacks, just get the
> information from the list in the first place.
[...]
> @@ -3289,8 +3422,18 @@ static int arm_smmu_attach_prepare_invs(struct arm_smmu_attach_state *state,
> invst->old_invs = rcu_dereference_protected(
> new_smmu_domain->invs,
> lockdep_is_held(&arm_smmu_asid_lock));
> - build_invs = arm_smmu_master_build_invs(
> - master, state->ats_enabled, ssid, new_smmu_domain);
> +
> + /* Re-use or allocate an IOTLB cache tag */
> + ret = arm_smmu_get_tag(new_smmu_domain, master,
> + to_vsmmu(new_domain), &invst->tag,
> + false);
> + if (ret)
> + return ret;
> +
> + build_invs = arm_smmu_master_build_invs(master,
> + state->ats_enabled,
> + ssid, new_smmu_domain,
> + &invst->tag);
> if (!build_invs)
> return -EINVAL;
I had this when I was drafting the series in the beginning, but
later changed to the callback functions :-/
Again, my intention is to avoid iterating the array since merge
and unref functions are already doing that in their first loops.
That being said, if this get-before-build is the preferred way,
let's do that.
Thanks
Nicolin
next prev parent reply other threads:[~2025-12-19 20:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 20:26 [PATCH v1 0/9] iommu/arm-smmu-v3: Share domain across SMMU/vSMMU instances Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 1/9] iommu/arm-smmu-v3: Pass in ssid to arm_smmu_make_s1_cd() Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 2/9] iommu/arm-smmu-v3: Add alloc_id/free_id functions to arm_smmu_invs Nicolin Chen
2025-12-19 17:05 ` Jason Gunthorpe
2025-12-19 20:56 ` Nicolin Chen [this message]
2026-01-02 15:54 ` Jason Gunthorpe
2025-12-30 18:52 ` Nicolin Chen
2025-12-31 19:48 ` Nicolin Chen
2026-01-02 15:57 ` Jason Gunthorpe
2026-01-16 5:13 ` Nicolin Chen
2026-01-16 14:41 ` Jason Gunthorpe
2026-01-16 16:58 ` Nicolin Chen
2026-01-16 17:11 ` Jason Gunthorpe
2026-01-16 18:27 ` Nicolin Chen
2026-01-17 1:11 ` Jason Gunthorpe
2025-12-18 20:26 ` [PATCH v1 3/9] iommu/arm-smmu-v3: Store ASIDs and VMID in arm_smmu_master Nicolin Chen
2025-12-19 15:16 ` Jason Gunthorpe
2025-12-19 19:17 ` Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 4/9] iommu/arm-smmu-v3: Use alloc_id/free_id ops in arm_smmu_invs_merge/unref Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 5/9] iommu/arm-smmu-v3: Install to CD/STE the ASID/VMID stored in the master Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 6/9] iommu/arm-smmu-v3: Use dummy ASID/VMID in arm_smmu_master_build_invs() Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 7/9] iommu/arm-smmu-v3: Remove free_fn argument from arm_smmu_invs_unref() Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 8/9] iommu/arm-smmu-v3: Remove ASID/VMID from arm_smmu_domain Nicolin Chen
2025-12-18 20:26 ` [PATCH v1 9/9] iommu/arm-smmu-v3: Allow sharing domain across SMMUs Nicolin Chen
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=aUW78ZV2D5aM75yN@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miko.lenczewski@arm.com \
--cc=patches@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox