linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Donald Dutile <ddutile@redhat.com>
To: Peter Xu <peterx@redhat.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] mm/arm64: Drop dead code for pud special bit handling
Date: Thu, 20 Mar 2025 17:03:05 -0400	[thread overview]
Message-ID: <73969634-a6f6-4dbb-bc30-801a5c4500cf@redhat.com> (raw)
In-Reply-To: <20250320183405.12659-1-peterx@redhat.com>

Peter,

Thanks for the cc, as I have the original commit in a recent, proposed backport that now needs an edit...
or, since harmless, maybe this patch to additionally backport, once committed. :-)

On 3/20/25 2:34 PM, Peter Xu wrote:
> Keith Busch observed some incorrect macros defined in arm64 code [1].
> 
> It turns out the two lines should never be needed and won't be exposed to
> anyone, because aarch64 doesn't select HAVE_ARCH_TRANSPARENT_HUGEPAGE_PUD,
> hence ARCH_SUPPORTS_PUD_PFNMAP is always N.  The only archs that support
> THP PUDs so far are x86 and powerpc.
> 
> Instead of fixing the lines (with no way to test it..), remove the two
> lines that are in reality dead code, to avoid confusing readers.
> 
> Fixes tag is attached to reflect where the wrong macros were introduced,
> but explicitly not copying stable, because there's no real issue to be
> fixed.  So it's only about removing the dead code so far.
> 
> [1] https://lore.kernel.org/all/Z9tDjOk-JdV_fCY4@kbusch-mbp.dhcp.thefacebook.com/#t
> 
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Cc: Donald Dutile <ddutile@redhat.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Fixes: 3e509c9b03f9 ("mm/arm64: support large pfn mappings")
> Reported-by: Keith Busch <kbusch@kernel.org>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>   arch/arm64/include/asm/pgtable.h | 5 -----
>   1 file changed, 5 deletions(-)
> 
> diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
> index 0b2a2ad1b9e8..15211f74b035 100644
> --- a/arch/arm64/include/asm/pgtable.h
> +++ b/arch/arm64/include/asm/pgtable.h
> @@ -620,11 +620,6 @@ static inline pmd_t pmd_mkspecial(pmd_t pmd)
>   #define pud_pfn(pud)		((__pud_to_phys(pud) & PUD_MASK) >> PAGE_SHIFT)
>   #define pfn_pud(pfn,prot)	__pud(__phys_to_pud_val((phys_addr_t)(pfn) << PAGE_SHIFT) | pgprot_val(prot))
>   
> -#ifdef CONFIG_ARCH_SUPPORTS_PUD_PFNMAP
> -#define pud_special(pte)	pte_special(pud_pte(pud))
> -#define pud_mkspecial(pte)	pte_pud(pte_mkspecial(pud_pte(pud)))
> -#endif
> -
>   #define pmd_pgprot pmd_pgprot
>   static inline pgprot_t pmd_pgprot(pmd_t pmd)
>   {

Reviewed-by: Donald Dutile <ddutile@redhat.com>



  reply	other threads:[~2025-03-20 21:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 18:34 Peter Xu
2025-03-20 21:03 ` Donald Dutile [this message]
2025-03-20 21:45   ` Peter Xu
2025-03-21  4:21 ` Anshuman Khandual
2025-03-28 20:08 ` Catalin Marinas

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=73969634-a6f6-4dbb-bc30-801a5c4500cf@redhat.com \
    --to=ddutile@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.williamson@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=peterx@redhat.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