From: Mostafa Saleh <smostafa@google.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
iommu@lists.linux.dev, "Joerg Roedel (AMD)" <joro@8bytes.org>,
Jean-Philippe Brucker <jpb@kernel.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Randy Dunlap <rdunlap@infradead.org>,
Robin Murphy <robin.murphy@arm.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Will Deacon <will@kernel.org>,
David Matlack <dmatlack@google.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
patches@lists.linux.dev, Pranjal Shrivastava <praan@google.com>,
Samiullah Khawaja <skhawaja@google.com>,
stable@vger.kernel.org,
Vijayanand Jitta <vijayanand.jitta@oss.qualcomm.com>
Subject: Re: [PATCH v5 4/9] iommu/arm-smmu-v3: Optimize range invalidation for latency
Date: Mon, 7 Sep 2026 14:26:16 +0000 [thread overview]
Message-ID: <ap7JiB36YSQOaV9a@google.com> (raw)
In-Reply-To: <4-v5-b810cf379bfc+13d738-smmu_tlbi_jgg@nvidia.com>
On Tue, Sep 01, 2026 at 02:49:53PM -0300, Jason Gunthorpe wrote:
> The server IOMMU drivers focus on invalidation latency by default,
> over-invalidating if necessary, to round the invalidation range up to a
> single command. I think this represents a trade off for DMA non-FQ and SVA
> where stalling the operation is overall worse than re-loading the IOTLB.
>
> For instance AMD and VT-d both round the range up to the largest aligned
> power of two and invalidate that. This causes over-invalidation but that
> is preferred on real HW over trying to issue a number of smaller
> range invalidations.
>
> SMMUv3 on the other hand will try to do up to 512 single invalidations,
> otherwise falls back to full invalidation, or it will try to issue an
> string of RIL invalidations for every 5 bits of IOVA range to perfectly
> cover it.
>
> While the RIL optimization is pretty good we can still do better and
> reduce it to only 2 invalidations at maximum using the idea Robin came up
> with to overlap two RILs in the middle. This preserves the exact coverage
> of the current RIL and still caps the number of RILs at 2.
>
> This works because the RIL can start at any IOVA, so we can place a RIL
> forwards from the start and backwards from the end, overlapping in the
> middle if the scale isn't precise enough.
>
> In the cases where this produces 2 RILS it continues to produce RILs that
> don't overlap, but the exact split point is different than the original
> algorithm due to the new calculation method. In cases where the original
> algorithm would produce 3 or more RILs this will produce 2 RILS with an
> overlap.
>
> The SVA under invalidation errata work around is maintained by "rounding up" to
> generate a single RIL that over-covers the entire range.
>
> Since the normal path is now the only one with a loop, split them into two
> functions and fold a simplified version of arm_smmu_inv_size_too_big()
> directly into the normal flow in a way that directly limits the number of
> single invalidation commands generated, again focusing on controlling
> latency.
>
> The end result is any gather is converted into either:
> - One invalidate all
> - One or two range invalidate ops
> - At most 512 single invalidation ops
>
> arm_smmu_domain_inv() is modified to always pass in the tgsz because the
> new logic relies on it being valid.
>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 354 ++++++++++++--------
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 3 +-
> 2 files changed, 210 insertions(+), 147 deletions(-)
>
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> index 6413eb4021ce22..9b79d7a5389812 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -2460,166 +2460,219 @@ static void arm_smmu_tlb_inv_context(void *cookie)
> arm_smmu_domain_inv(smmu_domain);
> }
>
> -static void arm_smmu_cmdq_batch_add_range(struct arm_smmu_device *smmu,
> +/*
> + * Check address alignment for TTL hint per SMMUv3 H.a Section 4.4.1.
> + * Address bits below the alignment must be zero, otherwise UNPREDICTABLE.
> + */
> +static bool arm_smmu_ttl_addr_aligned(u64 address, unsigned int tg,
> + unsigned int ttl)
> +{
> + unsigned int pgsz_lg2 = (tg - 3) * (3 - ttl) + tg;
> +
> + return !(address & GENMASK_U64(pgsz_lg2 - 1, 0));
> +}
> +
> +struct arm_smmu_ril_range {
> + u64 start_tg;
> + /* Normal integer, not encoded. 0 means 0.*/
> + u64 num;
> + unsigned int scale;
> +};
> +
> +/*
> + * Initialize the smallest RIL covering num_tg and ending at last_tg.
> + */
> +static struct arm_smmu_ril_range arm_smmu_ril_init_end(u64 last_tg, u64 num_tg)
> +{
> + struct arm_smmu_ril_range ril = {};
> +
> + if (!num_tg)
> + return ril;
> +
> + ril.scale = fls64((num_tg - 1) / 32);
> + ril.num = DIV_ROUND_UP_ULL(num_tg, 1ULL << ril.scale);
> + ril.start_tg = last_tg - ((ril.num << ril.scale) - 1);
> + return ril;
> +}
> +
> +static void arm_smmu_cmdq_batch_add_ril(struct arm_smmu_device *smmu,
> + struct arm_smmu_cmdq_batch *cmds,
> + struct arm_smmu_cmd *ref_cmd,
> + bool leaf_only,
> + const struct arm_smmu_ril_range *ril,
> + u8 ttl, u8 tg_enc)
> +{
> + struct arm_smmu_cmd cmd;
> + unsigned int tgsz_lg2 = tg_enc * 2 + 10;
> + u64 iova = ril->start_tg << tgsz_lg2;
> + unsigned int num = ril->num - 1;
> +
> + /* 16K granule TTL=1 is reserved (Section 4.4.1) */
> + if (WARN_ON(tgsz_lg2 == 14 && ttl == 1))
> + ttl = 0;
> +
> + /* Verify address alignment for the TTL hint */
> + if (ttl && !arm_smmu_ttl_addr_aligned(iova, tgsz_lg2, ttl))
> + ttl = 0;
Is that a separate fix? Can this be a separate patch in that case.
Also, in what cases can this happen? io-pgtable-arm should do the
right thing and SVA will use ttl=0
> +
> + /*
> + * SMMUv3 H.a Section 4.4.1: TG!=0, NUM==0, SCALE==0, TTL==0 is Reserved
> + * and causes CERROR_ILL. Single tg uses NUM=0, SCALE=0 with a TTL hint
> + * to target only the exact leaf entry.
> + *
> + * For a single tg invalidation a 0 TTL can come from places like the
> + * SVA path that don't have enough information to get a TTL, or as a
> + * side of effect of the splitting.
> + *
> + * A single-TG invalidation cannot reach this point if it is part of a
> + * CONT group, so it is safe to transform it into a single invalidation.
> + * The ARM_SMMU_OPT_FULL_CONT_RIL errata does not apply.
> + */
> + if (!num && !ril->scale && !ttl)
> + tg_enc = 0;
> +
> + cmd.data[0] = ref_cmd->data[0] | FIELD_PREP(CMDQ_TLBI_0_NUM, num) |
> + FIELD_PREP(CMDQ_TLBI_0_SCALE, ril->scale);
> + cmd.data[1] = ref_cmd->data[1] |
> + FIELD_PREP(CMDQ_TLBI_1_LEAF, leaf_only) |
> + FIELD_PREP(CMDQ_TLBI_1_TTL, ttl) |
> + FIELD_PREP(CMDQ_TLBI_1_TG, tg_enc) | iova;
> + arm_smmu_cmdq_batch_add_cmd_p(smmu, cmds, &cmd);
> +}
> +
> +/*
> + * Issue up to two range TLBI commands covering [iova, iova+size). Returns true
> + * if successful, false if the range is too large to fit into RIL commands.
> + *
> + * Normally the first RIL is the largest representable span which does not
> + * exceed the requested range. If necessary, the second RIL is the smallest
> + * representable range covering the remainder and is anchored at the end. Any
> + * excess coverage from the second RIL overlaps the first instead of exceeding
> + * the requested range.
> + *
> + * If a SVA is being invalidated and the SMMU has the ARM_SMMU_OPT_FULL_CONT_RIL
> + * errata this produces only a single RIL and overinvalidates to ensure any
> + * potential CONT is covered with a single RIL.
> + */
> +static bool arm_smmu_cmdq_batch_add_range(struct arm_smmu_device *smmu,
> struct arm_smmu_cmdq_batch *cmds,
> struct arm_smmu_cmd *cmd,
> struct arm_smmu_tlbi *tlbi)
> {
> - size_t inv_range = tlbi->iopte_size;
> - unsigned long iova = tlbi->iova;
> - unsigned long end = iova + tlbi->size;
> - unsigned long num_pages = 0;
> - u8 tg = tlbi->tgsz_lg2;
> - u64 orig_data0 = cmd->data[0];
> - u8 ttl = 0, tg_enc = 0;
> + u8 tgsz_lg2 = tlbi->tgsz_lg2;
> + struct arm_smmu_ril_range first = { .start_tg = tlbi->iova >>
> + tgsz_lg2 };
> + u64 last_tg = (tlbi->iova + tlbi->size - 1) >> tgsz_lg2;
> + u64 num_tg = last_tg - first.start_tg + 1;
> + u8 tg_enc = (tgsz_lg2 - 10) / 2;
> + struct arm_smmu_ril_range trail;
> + u8 ttl = 0;
>
> - if (WARN_ON_ONCE(!tlbi->size))
> - return;
> -
> - if (smmu->features & ARM_SMMU_FEAT_RANGE_INV) {
> - num_pages = tlbi->size >> tg;
> -
> - /* Convert page size of 12,14,16 (log2) to 1,2,3 */
> - tg_enc = (tg - 10) / 2;
> -
> - /*
> - * Determine what level the granule is at. For non-leaf, both
> - * io-pgtable and SVA pass a nominal last-level granule because
> - * they don't know what level(s) actually apply, so ignore that
> - * and leave TTL=0. However for various errata reasons we still
> - * want to use a range command, so avoid the SVA corner case
> - * where both scale and num could be 0 as well.
> - */
> - if (tlbi->leaf_only)
> - ttl = 4 - ((ilog2(tlbi->iopte_size) - 3) / (tg - 3));
> - else if ((num_pages & CMDQ_TLBI_RANGE_NUM_MAX) == 1)
> - num_pages++;
> - }
> -
> - while (iova < end) {
> - if (smmu->features & ARM_SMMU_FEAT_RANGE_INV) {
> - /*
> - * On each iteration of the loop, the range is 5 bits
> - * worth of the aligned size remaining.
> - * The range in pages is:
> - *
> - * range = (num_pages & (0x1f << __ffs(num_pages)))
> - */
> - unsigned long scale, num;
> -
> - /* Determine the power of 2 multiple number of pages */
> - scale = __ffs(num_pages);
> -
> - /* Determine how many chunks of 2^scale size we have */
> - num = (num_pages >> scale) & CMDQ_TLBI_RANGE_NUM_MAX;
> -
> - /* Keep the pre-DS 5-bit truncation when scale > 31 */
> - cmd->data[0] = orig_data0 |
> - FIELD_PREP(CMDQ_TLBI_0_NUM, num - 1) |
> - FIELD_PREP(CMDQ_TLBI_0_SCALE, scale & 0x1f);
That just deletes the DS code which was recently merged.
I see that is added again in the last patch, but it would make more
sense to do it in the same patch I guess.
Thanks,
Mostafa
> -
> - /* range is num * 2^scale * pgsize */
> - inv_range = num << (scale + tg);
> -
> - /* Clear out the lower order bits for the next iteration */
> - num_pages -= num << scale;
> - }
> -
> - /*
> - * IPA has fewer bits than VA, but they are reserved in the
> - * command and something would be very broken if iova had them
> - * set.
> - */
> - cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF, tlbi->leaf_only) |
> - FIELD_PREP(CMDQ_TLBI_1_TTL, ttl) |
> - FIELD_PREP(CMDQ_TLBI_1_TG, tg_enc) |
> - (iova & ~GENMASK_U64(11, 0));
> -
> - arm_smmu_cmdq_batch_add_cmd_p(smmu, cmds, cmd);
> - iova += inv_range;
> - }
> -}
> -
> -/*
> - * Generate a RIL for ARM_SMMU_OPT_FULL_CONT_RIL by ensuring the entire SVA
> - * requested range is covered with a single RIL command. The scale is adjusted
> - * so that the RIL may extend past the end of the requested range. This ensures
> - * that any CONT the MM is invalidating is covered by a single RIL. TTL and LEAF
> - * are always 0 because this is only used by SVA.
> - */
> -static bool arm_smmu_cmdq_batch_add_ril(struct arm_smmu_device *smmu,
> - struct arm_smmu_cmdq_batch *cmds,
> - struct arm_smmu_cmd *cmd,
> - unsigned long iova, size_t size,
> - u8 tgsz_lg2)
> -{
> - u64 cur_tg = iova >> tgsz_lg2;
> - u64 num_tg = ((iova + size - 1) >> tgsz_lg2) - cur_tg + 1;
> - unsigned int scale = fls64((num_tg - 1) / 32);
> -
> - if (scale > 31)
> - return false;
> -
> - cmd->data[0] |=
> - FIELD_PREP(CMDQ_TLBI_0_NUM,
> - DIV_ROUND_UP_ULL(num_tg, 1ULL << scale) - 1) |
> - FIELD_PREP(CMDQ_TLBI_0_SCALE, scale);
> - cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_TG, (tgsz_lg2 - 10) / 2) |
> - (cur_tg << tgsz_lg2);
> - arm_smmu_cmdq_batch_add_cmd_p(smmu, cmds, cmd);
> - return true;
> -}
> -
> -static bool arm_smmu_inv_size_too_big(struct arm_smmu_device *smmu,
> - struct arm_smmu_tlbi *tlbi)
> -{
> - size_t max_tlbi_ops;
> -
> - /* 0 size means invalidate all */
> - if (!tlbi->size || tlbi->size == SIZE_MAX)
> - return true;
> -
> - if (smmu->features & ARM_SMMU_FEAT_RANGE_INV)
> + if (!tlbi->size)
> return false;
>
> /*
> - * Borrowed from the MAX_TLBI_OPS in arch/arm64/include/asm/tlbflush.h,
> - * this is used as a threshold to replace "size_opcode" commands with a
> - * single "nsize_opcode" command, when SMMU doesn't implement the range
> - * invalidation feature, where there can be too many per-granule TLBIs,
> - * resulting in a soft lockup.
> + * Determine what level the granule is at. For non-leaf, both
> + * io-pgtable and SVA pass a nominal last-level granule because they
> + * don't know what level(s) actually apply, so leave TTL=0.
> */
> - max_tlbi_ops = 1 << (ilog2(tlbi->iopte_size) - 3);
> - return tlbi->size >= max_tlbi_ops * tlbi->iopte_size;
> + if (tlbi->leaf_only)
> + ttl = 4 - ((ilog2(tlbi->iopte_size) - 3) / (tgsz_lg2 - 3));
> +
> + /*
> + * The spec defines the invalidated range as:
> + * Range = ((NUM+1) * 2^SCALE) * Translation_Granule_Size
> + * NUM is 5 bits, so (NUM+1) covers 1..32 granules. Find the smallest
> + * SCALE at which a single command could cover num_tg.
> + *
> + * Unlike other IOMMUs the spec has no alignment requirement on the
> + * address beyond alignment to tg (so long as TTL=0).
> + */
> + first.scale = fls64((num_tg - 1) / 32);
> + if (first.scale > 31) {
> + /* Range too large for a single command do full invalidation */
> + return false;
> + }
> +
> + if (tlbi->has_cont && (smmu->options & ARM_SMMU_OPT_FULL_CONT_RIL)) {
> + /*
> + * Produce a single invalidation by rounding up and disabling
> + * the trailer.
> + */
> + first.num = DIV_ROUND_UP_ULL(num_tg, 1ULL << first.scale);
> + trail.num = 0;
> + } else {
> + /*
> + * Produce two invalidations by rounding down and adding a
> + * second trailing RIL anchored at the end.
> + */
> + first.num = num_tg >> first.scale;
> + trail = arm_smmu_ril_init_end(
> + last_tg, num_tg - ((u64)first.num << first.scale));
> + }
> + arm_smmu_cmdq_batch_add_ril(smmu, cmds, cmd, tlbi->leaf_only, &first,
> + ttl, tg_enc);
> +
> + if (trail.num)
> + arm_smmu_cmdq_batch_add_ril(smmu, cmds, cmd, tlbi->leaf_only,
> + &trail, ttl, tg_enc);
> + return true;
> }
>
> -/* Used by non INV_TYPE_ATS* invalidations */
> -static void arm_smmu_inv_to_cmdq_batch(struct arm_smmu_inv *inv,
> +/*
> + * One TLBI command per IOTLB entry, assuming the entries are all at least
> + * iopte_granule sized. Returns false if too many commands would be needed which
> + * indicates too high a latency. The threshold is similar to MAX_DVM_OPS in
> + * arch/arm64/include/asm/tlbflush.h for the 4k PAGE_SIZE.
> + */
> +static bool arm_smmu_cmdq_batch_add_single(struct arm_smmu_device *smmu,
> + struct arm_smmu_cmdq_batch *cmds,
> + struct arm_smmu_cmd *cmd,
> + struct arm_smmu_tlbi *tlbi)
> +{
> + unsigned long num_ops = tlbi->size / tlbi->iopte_size;
> + unsigned long iova = tlbi->iova;
> + unsigned long i;
> +
> + if (!num_ops || num_ops > 512)
> + return false;
I am guessing "!num_ops" is impossible as both params are passed from
io-pgtable-arm so size must be >= iopte_size. However, in case size
was less than the iopte_size, wouldn’t we need to round up in that case?
> +
> + for (i = 0; i < num_ops; i++) {
> + cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF, tlbi->leaf_only) |
> + (iova & ~GENMASK_U64(11, 0));
> + arm_smmu_cmdq_batch_add_cmd_p(smmu, cmds, cmd);
> + iova += tlbi->iopte_size;
> + }
> + return true;
> +}
> +
> +static void arm_smmu_inv_all_cmd(struct arm_smmu_inv *inv,
> + struct arm_smmu_cmdq_batch *cmds,
> + struct arm_smmu_cmd *cmd)
> +{
> + u64p_replace_bits(&cmd->data[0], inv->nsize_opcode, CMDQ_0_OP);
> + arm_smmu_cmdq_batch_add_cmd_p(inv->smmu, cmds, cmd);
> +}
> +
> +/*
> + * Used by non INV_TYPE_ATS* invalidations. Returns true if it fell back to
> + * full invalidation using nsize_opcode.
> + */
> +static bool arm_smmu_inv_to_cmdq_batch(struct arm_smmu_inv *inv,
> struct arm_smmu_cmdq_batch *cmds,
> struct arm_smmu_cmd *cmd,
> struct arm_smmu_tlbi *tlbi)
> {
> - struct arm_smmu_cmd nsize_cmd;
> -
> - if (arm_smmu_inv_size_too_big(inv->smmu, tlbi))
> - goto full_inv;
> -
> - if (tlbi->has_cont && tlbi->size > tlbi->iopte_size &&
> - (inv->smmu->options & ARM_SMMU_OPT_FULL_CONT_RIL)) {
> - if (!arm_smmu_cmdq_batch_add_ril(inv->smmu, cmds, cmd,
> - tlbi->iova, tlbi->size,
> - tlbi->tgsz_lg2))
> - goto full_inv;
> - return;
> + if (inv->smmu->features & ARM_SMMU_FEAT_RANGE_INV) {
> + if (arm_smmu_cmdq_batch_add_range(inv->smmu, cmds, cmd, tlbi))
> + return false;
> + } else {
> + if (arm_smmu_cmdq_batch_add_single(inv->smmu, cmds, cmd, tlbi))
> + return false;
> }
>
> - arm_smmu_cmdq_batch_add_range(inv->smmu, cmds, cmd, tlbi);
> - return;
> -
> -full_inv:
> - nsize_cmd = *cmd;
> - u64p_replace_bits(&nsize_cmd.data[0], inv->nsize_opcode, CMDQ_0_OP);
> - arm_smmu_cmdq_batch_add_cmd_p(inv->smmu, cmds, &nsize_cmd);
> + arm_smmu_inv_all_cmd(inv, cmds, cmd);
> + return true;
> }
>
> static inline bool arm_smmu_invs_end_batch(struct arm_smmu_inv *cur,
> @@ -2641,6 +2694,7 @@ static inline bool arm_smmu_invs_end_batch(struct arm_smmu_inv *cur,
> static void __arm_smmu_domain_inv_range(struct arm_smmu_tlbi *tlbi,
> struct arm_smmu_invs *invs)
> {
> + struct arm_smmu_inv *used_s12_vmall = NULL;
> struct arm_smmu_cmdq_batch cmds = {};
> struct arm_smmu_inv *cur;
> struct arm_smmu_inv *end;
> @@ -2674,11 +2728,19 @@ static void __arm_smmu_domain_inv_range(struct arm_smmu_tlbi *tlbi,
> case INV_TYPE_S2_VMID:
> cmd = arm_smmu_make_cmd_tlbi(cur->size_opcode,
> 0, cur->id);
> - arm_smmu_inv_to_cmdq_batch(cur, &cmds, &cmd, tlbi);
> + if (arm_smmu_inv_to_cmdq_batch(cur, &cmds, &cmd, tlbi))
> + used_s12_vmall = cur + 1;
> break;
> case INV_TYPE_S2_VMID_S1_CLEAR:
> - /* CMDQ_OP_TLBI_S12_VMALL already flushed S1 entries */
> - if (arm_smmu_inv_size_too_big(cur->smmu, tlbi))
> + /*
> + * S2_VMID used CMDQ_OP_TLBI_S12_VMALL which already
> + * flushed S1 entries. These two types always come in
> + * pairs and arm_smmu_inv_cmp() ensures that they are
> + * consecutive in the list for the same SMMU. There may
> + * be several pairings so check this is paired with the
> + * one that did the full invalidation.
> + */
> + if (used_s12_vmall == cur)
> break;
> arm_smmu_cmdq_batch_add_cmd(
> smmu, &cmds,
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> index 3e7f94339ab60e..8b075e05d900aa 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> @@ -1173,7 +1173,8 @@ void arm_smmu_domain_inv_range(struct arm_smmu_domain *smmu_domain,
>
> static inline void arm_smmu_domain_inv(struct arm_smmu_domain *smmu_domain)
> {
> - arm_smmu_domain_inv_range(smmu_domain, 0, 0, 0, false);
> + arm_smmu_domain_inv_range(smmu_domain, 0, 0, 1 << smmu_domain->tgsz_lg2,
> + false);
> }
>
> void __arm_smmu_cmdq_skip_err(struct arm_smmu_device *smmu,
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-09-07 14:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 17:49 [PATCH v5 0/9] Organize the SMMUv3 invalidation flow so iommupt can use it Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 1/9] iommu/arm-smmu-v3: Handle ARM erratum for CONT under invalidation with SVA Jason Gunthorpe
2026-09-07 14:21 ` Mostafa Saleh
2026-09-07 15:11 ` Jason Gunthorpe
2026-09-07 15:17 ` Mostafa Saleh
2026-09-07 15:18 ` Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 2/9] iommu/arm-smmu-v3: Pass the parameters for the invalidation in a struct Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 3/9] iommu/arm-smmu-v3: Move pgsize out of arm_smmu_inv Jason Gunthorpe
2026-09-07 14:22 ` Mostafa Saleh
2026-09-01 17:49 ` [PATCH v5 4/9] iommu/arm-smmu-v3: Optimize range invalidation for latency Jason Gunthorpe
2026-09-07 14:26 ` Mostafa Saleh [this message]
2026-09-07 15:23 ` Jason Gunthorpe
2026-09-07 19:34 ` Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 5/9] iommu/arm-smmu-v3: Keep track in the arm_smmu_invs if RIL is used Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 6/9] iommu/arm-smmu-v3: Precompute the invalidation commands Jason Gunthorpe
2026-09-07 14:27 ` Mostafa Saleh
2026-09-07 15:19 ` Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 7/9] iommu/arm-smmu-v3: Populate the tlbi at the top of the call chain Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 8/9] iommu/arm-smmu-v3: Change how the tlbi describes the invalidation Jason Gunthorpe
2026-09-07 14:42 ` Mostafa Saleh
2026-09-07 15:34 ` Jason Gunthorpe
2026-09-09 15:57 ` Jason Gunthorpe
2026-09-01 17:49 ` [PATCH v5 9/9] iommu/arm-smmu-v3: Support the DS expansion of RIL's SCALE Jason Gunthorpe
2026-09-07 14:44 ` Mostafa Saleh
2026-09-07 19:39 ` 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=ap7JiB36YSQOaV9a@google.com \
--to=smostafa@google.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolinc@nvidia.com \
--cc=pasha.tatashin@soleen.com \
--cc=patches@lists.linux.dev \
--cc=praan@google.com \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@google.com \
--cc=stable@vger.kernel.org \
--cc=vijayanand.jitta@oss.qualcomm.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