public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Ryan Roberts <ryan.roberts@arm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/mm: Drop redundant addr increment in set_huge_pte_at()
Date: Tue, 15 Jul 2025 11:28:28 +0530	[thread overview]
Message-ID: <e10e0fac-a81c-445e-8036-9db2b63b77f7@arm.com> (raw)
In-Reply-To: <20250715043922.57195-1-anshuman.khandual@arm.com>


On 15/07/25 10:09 am, Anshuman Khandual wrote:
> The 'addr' need not be incremented while operating on single entry basis as
> BBM is not required for such updates.

"while operating on a single entry basis" should be replaced with
"when transitioning from invalid to valid pte"; BBM is required
for single entry updates when the cont bit is set, as described
in the comment immediately below. In fact, let us not even mention
BBM at all - the reasoning is that the code is written in a way
that, the loop incrementing addr, immediately has a return after
it, and it does not actually use the addr, so let's drop the
increment. It is not immediately obvious from the commit description
that the addr is passed ultimately to flush_tlb_range friends which
is involved in BBM.

Reviewed-by: Dev Jain <dev.jain@arm.com>

>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
>   arch/arm64/mm/hugetlbpage.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/mm/hugetlbpage.c b/arch/arm64/mm/hugetlbpage.c
> index 0c8737f4f2ce..1d90a7e75333 100644
> --- a/arch/arm64/mm/hugetlbpage.c
> +++ b/arch/arm64/mm/hugetlbpage.c
> @@ -225,7 +225,7 @@ void set_huge_pte_at(struct mm_struct *mm, unsigned long addr,
>   	ncontig = num_contig_ptes(sz, &pgsize);
>   
>   	if (!pte_present(pte)) {
> -		for (i = 0; i < ncontig; i++, ptep++, addr += pgsize)
> +		for (i = 0; i < ncontig; i++, ptep++)
>   			__set_ptes_anysz(mm, ptep, pte, 1, pgsize);
>   		return;
>   	}


  reply	other threads:[~2025-07-15  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  4:39 [PATCH] arm64/mm: Drop redundant addr increment in set_huge_pte_at() Anshuman Khandual
2025-07-15  5:58 ` Dev Jain [this message]
2025-07-15  6:36   ` Anshuman Khandual

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=e10e0fac-a81c-445e-8036-9db2b63b77f7@arm.com \
    --to=dev.jain@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan.roberts@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