From: Will Deacon <will@kernel.org>
To: anshuman.khandual@arm.com, catalin.marinas@arm.com,
Zhenhua Huang <quic_zhenhuah@quicinc.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
ardb@kernel.org, ryan.roberts@arm.com, mark.rutland@arm.com,
joey.gouly@arm.com, dave.hansen@linux.intel.com,
akpm@linux-foundation.org, chenfeiyang@loongson.cn,
chenhuacai@kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, quic_tingweiz@quicinc.com
Subject: Re: [PATCH v3] arm64: mm: Test for pmd_sect() in vmemmap_check_pmd()
Date: Wed, 8 Jan 2025 16:38:56 +0000 [thread overview]
Message-ID: <173626870329.286960.5328606288066578023.b4-ty@kernel.org> (raw)
In-Reply-To: <20250102074047.674156-1-quic_zhenhuah@quicinc.com>
On Thu, 02 Jan 2025 15:40:47 +0800, Zhenhua Huang wrote:
> Commit 2045a3b8911b ("mm/sparse-vmemmap: generalise vmemmap_populate_hugepages()")
> introduces the vmemmap_check_pmd() while does not verify if the entry is a
> section mapping, as is already done for Loongarch & X86.
> The update includes a check for pmd_sect(). Only if pmd_sect() returns true,
> further vmemmap population for the addr is skipped.
>
>
> [...]
Applied to arm64 (for-next/mm), thanks!
[1/1] arm64: mm: Test for pmd_sect() in vmemmap_check_pmd()
https://git.kernel.org/arm64/c/9ab2601dc4c1
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-01-08 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 7:40 Zhenhua Huang
2025-01-03 7:06 ` Anshuman Khandual
2025-01-08 16:38 ` Will Deacon [this message]
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=173626870329.286960.5328606288066578023.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=chenfeiyang@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_zhenhuah@quicinc.com \
--cc=ryan.roberts@arm.com \
/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
all inboxes | Powered by JetHome®