Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 8/9] iommu/arm-smmu-v3: Change how the tlbi describes the invalidation
Date: Mon, 7 Sep 2026 14:42:57 +0000	[thread overview]
Message-ID: <ap7NcebXzWC38VVo@google.com> (raw)
In-Reply-To: <8-v5-b810cf379bfc+13d738-smmu_tlbi_jgg@nvidia.com>

On Tue, Sep 01, 2026 at 02:49:57PM -0300, Jason Gunthorpe wrote:
> The RIL logic has long had a FIXME that there is not enough
> information to properly compute the RIL. There is also subtly not
> enough information to properly compute the single stride either.
> 
> Change tlbi to use the information format that iommupt is going to
> use for ARM. This prepares the invalidation code to support iommupt
> and fixes two small limitations with the current code.
> 
> iommupt is designed to accumulate all invalidation into a single
> gather, then the iommu driver should issue a small number of commands
> to execute the gather to control invalidation latency. This is in
> contrast to io-pgtable-arm.c which generates many gather flushes and
> direct walk cache flushes as it progresses.
> 
> To accommodate this the gather will accumulate "damage" in bitmaps,
> one for leaf changes and one for table changes. This is enough
> information for SMMUv3 to compute the proper stride for single
> invalidation and to generate ideal hints for range invalidation.

I am not sure I understand that, in what situation the leaf_bitmap
would be used instead of a single page size?
Would iommupt combine different page sizes in a single invalidation?

And then I see in this patch it has:
if (!is_power_of_2(leaf_bitmap))
	return 0;

Would that actually be better for performance than using 2 sets of
RILs, one for each page size?
As I'd imagine the HW will spend more effort on the TTL=0 case
otherwise it wouldn't require it.

> 
> Change the inner workings of the tlbi process to directly use this
> new-style gather description with the idea that the iommupt
> conversion will just direct assign the gather fields to the tlbi.
> 
> Rework the three places creating the tlbi to express their needs in
> terms of the new bitmaps.
> 
> 1) Simple iotlb invalidation always gets a single range of leaf
>    levels, so it can set a single leaf bit
> 
> 2) Walk invalidation is expected to clear the table and all the leaves it
>    could contain. Set a single table bit and all the leaf bits.
> 
>    There is a weakness in the existing io-pgtable where it double
>    invalidates the leaves, once through the arm_smmu_tlb_inv_walk() then
>    again through the gather. Since these are separate operations they are
>    not capped by the invalidation count limits and a single unmap may end
>    up doing thousands of tlbi commands. Eventually converting to iommupt's
>    gather only approach will correct this.
> 
> 3) SVA invalidation has no idea what the MM did, so it will set all
>    the bits in the bitmaps.
> 
>    This corrects another weakness where the RIL invalidation logic
>    was generating hints assuming the #2 rules which isn't correct
>    for SVA.
> 
> Reviewed-by: Nicolin Chen <nicolinc@nvidia.com>
> Tested-by: Nicolin Chen <nicolinc@nvidia.com>
> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
>  .../iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c   |  29 ++-
>  drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c   | 176 +++++++++++++-----
>  drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h   |  24 ++-
>  3 files changed, 177 insertions(+), 52 deletions(-)
> 
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> index 47eba08bd1161f..07ba4e7910ab84 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3-sva.c
> @@ -140,17 +140,34 @@ static void arm_smmu_mm_arch_invalidate_secondary_tlbs(struct mmu_notifier *mn,
>  {
>  	struct arm_smmu_domain *smmu_domain =
>  		container_of(mn, struct arm_smmu_domain, mmu_notifier);
> +	u8 tgsz_lg2 = smmu_domain->tgsz_lg2;
>  	struct arm_smmu_tlbi tlbi = {
>  		.tgsz_lg2 = smmu_domain->tgsz_lg2,
> -		.iova = start,
> +		.start = start,
> +		.last = end - 1,
>  		/*
> -		 * The mm_types defines vm_end as the first byte after the end
> -		 * address, different from IOMMU subsystem using the last
> -		 * address of an address range.
> +		 * No information comes from the mm, assume the worst case that
> +		 * it changed every table level. The way this is hooked into the
> +		 * mm is tricky, the range won't be expanded to include an
> +		 * entire table level if one was removed like the iommu gather
> +		 * does. Thus even if this is a 4k invalidation it may be
> +		 * including any table level too.
>  		 */
> -		.size = end - start,
> -		.iopte_size = PAGE_SIZE,
> +		.table_levels_bitmap = 0xfe,

What does that mean, won't arm have a max of 4 levels?

>  	};
> +	u8 pmd_lg2sz = (tgsz_lg2 - 3) * 1 + tgsz_lg2;
> +
> +	/*
> +	 * If the size is small then we can infer the invalidation is PTE only
> +	 * and set the PTE level only. Otherwise it could be some other
> +	 * combination so just set them all. This allows RIL to use TTL=3 in
> +	 * cases of PTE only changes. The mm must not try to partially
> +	 * invalidate pmd/etc.
> +	 */

How does that work with splitting blocks?  I imagine that might be
ossible with userspace.

> +	if (end - start < BIT_U64(pmd_lg2sz))
> +		tlbi.leaf_levels_bitmap = 1;
> +	else
> +		tlbi.leaf_levels_bitmap = 0xff;
>  
>  	arm_smmu_domain_tlbi(&tlbi, smmu_domain);
>  }
> 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 b9efba3404c68b..b99229a5bbacca 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -2397,8 +2397,8 @@ static struct arm_smmu_cmd arm_smmu_atc_inv_to_cmd(u32 sid, int ssid,
>  	 * This has the unpleasant side-effect of invalidating all PASID-tagged
>  	 * ATC entries within the address range.
>  	 */
> -	page_start = tlbi->iova >> inval_grain_shift;
> -	page_end = (tlbi->iova + tlbi->size - 1) >> inval_grain_shift;
> +	page_start = tlbi->start >> inval_grain_shift;
> +	page_end = tlbi->last >> inval_grain_shift;
>  
>  	/*
>  	 * In an ATS Invalidate Request, the address must be aligned on the
> @@ -2512,16 +2512,11 @@ static void arm_smmu_tlbi_add_range_cmd(struct arm_smmu_tlbi *tlbi,
>  {
>  	struct arm_smmu_cmd *cmd =
>  		&tlbi->range.cmds[tlbi->range.num_cmds++];
> -	unsigned int tgsz_lg2 = tg_enc * 2 + 10;
> -	u64 iova = ril->start_tg << tgsz_lg2;
> +	u64 iova = ril->start_tg << tlbi->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))
> +	if (ttl && !arm_smmu_ttl_addr_aligned(iova, tlbi->tgsz_lg2, ttl))
>  		ttl = 0;
>  
>  	/*
> @@ -2529,9 +2524,8 @@ static void arm_smmu_tlbi_add_range_cmd(struct arm_smmu_tlbi *tlbi,
>  	 * 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.
> +	 * For a single tg invalidation a 0 TTL can come 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.
> @@ -2542,14 +2536,83 @@ static void arm_smmu_tlbi_add_range_cmd(struct arm_smmu_tlbi *tlbi,
>  
>  	cmd->data[0] = FIELD_PREP(CMDQ_TLBI_0_NUM, num) |
>  		       FIELD_PREP(CMDQ_TLBI_0_SCALE, ril->scale);
> -	cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF, tlbi->leaf_only) |
> +	cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF,
> +				  !tlbi->table_levels_bitmap) |
>  		       FIELD_PREP(CMDQ_TLBI_1_TTL, ttl) |
>  		       FIELD_PREP(CMDQ_TLBI_1_TG, tg_enc) | iova;
>  }
>  
> +static int arm_smmu_bitmap_to_level(u8 bitmap)
> +{
> +	return 3 - (int)__ffs(bitmap);
> +}
> +
>  /*
> - * Generate up to two range TLBI command payloads covering [iova, iova+size).
> - * Sets use_full_inv if the range is too large to represent.
> + * Compute the TTL hint from leaf/table level bitmaps. 0 ttl means no hint
> + * invalidate all levels.
> + */
> +static unsigned int arm_smmu_compute_ttl(u8 leaf_bitmap, u8 table_bitmap,
> +					 u8 tgsz_lg2)
> +{
> +	int ttl;
> +
> +	if (leaf_bitmap) {
> +		/* If TTL is used then only leaves at the TTL are invalidated */
> +		if (!is_power_of_2(leaf_bitmap))
> +			return 0;
> +
> +		ttl = arm_smmu_bitmap_to_level(leaf_bitmap);
> +		if (table_bitmap) {
> +			int table_ttl = arm_smmu_bitmap_to_level(table_bitmap) + 1;
> +
> +			/*
> +			 * A RIL invalidation with !leaf_only clears out all
> +			 * table levels above the leaf level ttl only.
> +			 */
> +			if (table_ttl > ttl)
> +				return 0;
> +		}
> +	} else if (table_bitmap) {
> +		/*
> +		 * Table-only invalidation. Spec says:
> +		 *  For operations with Leaf=0, invalidation of cached Table
> +		 *  descriptors for the address and scope additionally occurs at
> +		 *  levels between the start of the walk and the level before
> +		 *  the last level given by TTL.
> +		 * Choose a TTL hint that covers the only target table
> +		 * descriptor levels.
> +		 */
> +		ttl = arm_smmu_bitmap_to_level(table_bitmap) + 1;
> +
> +		/*
> +		 * 16K granule, ARM TTL=1 is reserved (SMMUv3 H.a Section
> +		 * 4.4.1.1) if DS=0, avoid it always for table invalidations
> +		 * since we don't know what instance this will be applied to
> +		 * yet.
> +		 */
> +		if (tgsz_lg2 == 14 && ttl == 1)
> +			return 0;
> +	} else {
> +		/* Both bitmaps zero is not allowed */
> +		WARN_ON(true);
> +		return 0;
> +	}
> +
> +	/*
> +	 * Assumes the page table is formed properly and does not trigger the
> +	 * 16k TTL=1 condition for leaf-only unless DS is enabled.
> +	 *
> +	 * ARM level -1 never has a leaf so something has gone wrong. ARM Level
> +	 * 0 cannot be hinted because ttl=0 means no-hint.
> +	 */
> +	if (WARN_ON(ttl < 0))
> +		return 0;
> +	return ttl;
> +}
> +
> +/*
> + * Generate up to two range TLBI command payloads covering [start, last]. Sets
> + * use_full_inv if the range is too large to represent.
>   *
>   * Normally the first RIL is the largest representable span which does not
>   * exceed the requested range. If necessary, the second RIL is the smallest
> @@ -2565,21 +2628,14 @@ static void arm_smmu_tlbi_calc_range(struct arm_smmu_tlbi *tlbi,
>  				     bool single_ril)
>  {
>  	u8 tgsz_lg2 = tlbi->tgsz_lg2;
> -	struct arm_smmu_ril_range first = { .start_tg = tlbi->iova >>
> +	unsigned int ttl = arm_smmu_compute_ttl(
> +		tlbi->leaf_levels_bitmap, tlbi->table_levels_bitmap, tgsz_lg2);
> +	struct arm_smmu_ril_range first = { .start_tg = tlbi->start >>
>  							tgsz_lg2 };
> -	u64 last_tg = (tlbi->iova + tlbi->size - 1) >> tgsz_lg2;
> +	u64 last_tg = tlbi->last >> 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;
> -
> -	/*
> -	 * 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.
> -	 */
> -	if (tlbi->leaf_only)
> -		ttl = 4 - ((ilog2(tlbi->iopte_size) - 3) / (tgsz_lg2 - 3));
>  
>  	/*
>  	 * The spec defines the invalidated range as:
> @@ -2620,20 +2676,44 @@ static void arm_smmu_tlbi_calc_range(struct arm_smmu_tlbi *tlbi,
>  }
>  
>  /*
> - * One TLBI command per IOTLB entry, assuming the entries are all at least
> - * iopte_granule sized. Sets use_full_inv 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.
> + * Compute the stride for non-RIL single-page invalidation. Returns the log2
> + * stride of the lowest affected level. Single invalidation removes all IOPTEs
> + * that contain the IOVA invalidated, and we can reliably assume that the
> + * architected page size and table sizes (not contiguous!) are reflected in the
> + * IOTLB. Thus if there is a 2M leaf entry we only need to issue a single IOTLB
> + * invalidation within that 2M IOVA.
> + */
> +static u8 arm_smmu_tlbi_calc_stride(struct arm_smmu_tlbi *tlbi)
> +{
> +	u8 combined = tlbi->table_levels_bitmap | tlbi->leaf_levels_bitmap;
> +	u8 tg_szlg2 = tlbi->tgsz_lg2;
> +
> +	if (WARN_ON(!combined))
> +		return U8_MAX;

When can that happen?

> +	return (tg_szlg2 - 3) * __ffs(combined) + tg_szlg2;
> +}
> +
> +/*
> + * One TLBI command per stride-sized entry. Sets use_full_inv if too many
> + * commands would be needed. The threshold is similar to MAX_DVM_OPS in
> + * arch/arm64/include/asm/tlbflush.h.
>   */
>  static void arm_smmu_tlbi_calc_single(struct arm_smmu_tlbi *tlbi)
>  {
> -	unsigned long num_ops = tlbi->size / tlbi->iopte_size;
> +	u8 stride_lg2 = arm_smmu_tlbi_calc_stride(tlbi);
> +	unsigned long num_ops;
>  
> +	if (stride_lg2 == U8_MAX) {
> +		tlbi->single.use_full_inv = true;
> +		return;
> +	}
> +	num_ops = (tlbi->last - tlbi->start + 1) >> stride_lg2;
>  	if (!num_ops || num_ops > 512) {
>  		tlbi->single.use_full_inv = true;
>  		return;
>  	}
>  	tlbi->single.num = num_ops;
> +	tlbi->single.stride_lg2 = stride_lg2;
>  }
>  
>  static void arm_smmu_inv_all_cmd(struct arm_smmu_inv *inv,
> @@ -2653,7 +2733,7 @@ static bool arm_smmu_inv_to_cmdq_batch(struct arm_smmu_inv *inv,
>  				       struct arm_smmu_cmd *cmd,
>  				       struct arm_smmu_tlbi *tlbi)
>  {
> -	u64 iova = tlbi->iova;
> +	u64 iova = tlbi->start;
>  	unsigned int i;
>  
>  	if (inv->smmu->features & ARM_SMMU_FEAT_RANGE_INV) {
> @@ -2678,9 +2758,10 @@ static bool arm_smmu_inv_to_cmdq_batch(struct arm_smmu_inv *inv,
>  	}
>  
>  	for (i = 0; i < tlbi->single.num; i++) {
> -		cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF, tlbi->leaf_only) |
> +		cmd->data[1] = FIELD_PREP(CMDQ_TLBI_1_LEAF,
> +					  !tlbi->table_levels_bitmap) |
>  			       (iova & ~GENMASK_U64(11, 0));
> -		iova += tlbi->iopte_size;
> +		iova += BIT_U64(tlbi->single.stride_lg2);
>  		arm_smmu_cmdq_batch_add_cmd_p(inv->smmu, cmds, cmd);
>  	}
>  	return false;
> @@ -2876,12 +2957,16 @@ static void arm_smmu_tlb_inv_walk(unsigned long iova, size_t size,
>  				  size_t granule, void *cookie)
>  {
>  	struct arm_smmu_domain *smmu_domain = cookie;
> +	u8 tgsz_lg2 = smmu_domain->tgsz_lg2;
>  	struct arm_smmu_tlbi tlbi = {
>  		.tgsz_lg2 = smmu_domain->tgsz_lg2,
> -		.iova = iova,
> -		.size = size,
> -		.iopte_size = 1 << smmu_domain->tgsz_lg2,
> +		.start = iova,
> +		.last = iova + size - 1,
>  	};
> +	u8 table_levels = BIT((ilog2(size) - tgsz_lg2) / (tgsz_lg2 - 3));
> +
> +	tlbi.table_levels_bitmap = table_levels;
> +	tlbi.leaf_levels_bitmap = table_levels - 1;
>  
>  	arm_smmu_domain_tlbi(&tlbi, smmu_domain);
>  }
> @@ -4152,21 +4237,28 @@ static void arm_smmu_flush_iotlb_all(struct iommu_domain *domain)
>  		arm_smmu_tlb_inv_context(smmu_domain);
>  }
>  
> +/*
> + * Called by io-pgtable-arm.c for each run of same pgsize leaf only

I believe that it is called from dma-iommu.c, io-pgtable-arm.c will
call the tlb_add_page which builds the gather though.

> + * invalidation. If it has to change to a different leaf level then it flushes
> + * the gather and starts a fresh one. Thus this always targets only a single
> + * leaf level.
> + */
>  static void arm_smmu_iotlb_sync(struct iommu_domain *domain,
>  				struct iommu_iotlb_gather *gather)
>  {
>  	struct arm_smmu_domain *smmu_domain = to_smmu_domain(domain);
> +	unsigned int tg = smmu_domain->tgsz_lg2;
>  	struct arm_smmu_tlbi tlbi = {
>  		.tgsz_lg2 = smmu_domain->tgsz_lg2,
> -		.iova = gather->start,
> -		.size = gather->end - gather->start + 1,
> -		.iopte_size = gather->pgsize,
> -		.leaf_only = true,
> +		.start = gather->start,
> +		.last = gather->end,
>  	};
>  
> -	if (!gather->pgsize)
> +	if (WARN_ON(gather->pgsize < BIT(tg)))
>  		return;
>  
> +	tlbi.leaf_levels_bitmap = BIT((ilog2(gather->pgsize) - tg) / (tg - 3));

Having some page table macros would be helpful (and in other places in
this patch)

Thanks,
Mostafa

> +
>  	arm_smmu_domain_tlbi(&tlbi, smmu_domain);
>  }
>  
> 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 09befe7b284fed..6582203eb7425f 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h
> @@ -809,17 +809,31 @@ static inline struct arm_smmu_invs *arm_smmu_invs_alloc(size_t num_invs)
>  }
>  
>  struct arm_smmu_tlbi {
> -	unsigned long iova;
> -	size_t size;
> -	/* page or block size of the leaf iopte */
> -	unsigned int iopte_size;
> +	unsigned long start;
> +	unsigned long last;
>  	/* Base Translation Granule of the page table */
>  	u8 tgsz_lg2;
>  	bool leaf_only;
> +	/*
> +	 * Level bitmaps use iommupt numbering: bit 0 is the leaf-only level
> +	 * (ARM level 3), bit 1 is the next level up (ARM level 2), etc. These
> +	 * match the iommu_iotlb_gather.pt fields. Each set bit indicates a
> +	 * change at that level. The contiguous hint has no effect on
> +	 * invalidation processing because HW can ignore the hint.
> +	 *
> +	 * The pair selects the invalidation scope:
> +	 *   table!=0, leaf==0 : walk cache only
> +	 *   table==0, leaf!=0 : leaves only
> +	 *   table!=0, leaf!=0 : walk cache + all leaves
> +	 *   table==0, leaf==0 : illegal
> +	 */
> +	u8 leaf_levels_bitmap;
> +	u8 table_levels_bitmap;
>  
>  	struct {
>  		bool use_full_inv;
>  		u16 num;
> +		u8 stride_lg2;
>  	} single;
>  
>  	struct {
> @@ -1188,6 +1202,8 @@ static inline void arm_smmu_domain_inv(struct arm_smmu_domain *smmu_domain)
>  {
>  	/* Prefilled for invalidate all */
>  	struct arm_smmu_tlbi tlbi = {
> +		.start = 0,
> +		.last = ULONG_MAX,
>  		.tgsz_lg2 = smmu_domain->tgsz_lg2,
>  		.single.use_full_inv = true,
>  		.range.use_full_inv = true,
> -- 
> 2.43.0
> 


  reply	other threads:[~2026-09-07 14:43 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
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 [this message]
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=ap7NcebXzWC38VVo@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