archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <>
Cc: "Anshuman Khandual" <>,
	"Catalin Marinas" <>,
	"Will Deacon" <>,
	"Ard Biesheuvel" <>,
	"Mark Rutland" <>,
	"James Morse" <>,
	"Robin Murphy" <>,
	"Jérôme Glisse" <>,
	"Dan Williams" <>,
	"David Hildenbrand" <>,
	"Mike Rapoport" <>
Subject: [PATCH 1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Fri, 29 Jan 2021 13:09:45 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

pfn_valid() validates a pfn but basically it checks for a valid struct page
backing for that pfn. It should always return positive for memory ranges
backed with struct page mapping. But currently pfn_valid() fails for all
ZONE_DEVICE based memory types even though they have struct page mapping.

pfn_valid() asserts that there is a memblock entry for a given pfn without
MEMBLOCK_NOMAP flag being set. The problem with ZONE_DEVICE based memory is
that they do not have memblock entries. Hence memblock_is_map_memory() will
invariably fail via memblock_search() for a ZONE_DEVICE based address. This
eventually fails pfn_valid() which is wrong. memblock_is_map_memory() needs
to be skipped for such memory ranges. As ZONE_DEVICE memory gets hotplugged
into the system via memremap_pages() called from a driver, their respective
memory sections will not have SECTION_IS_EARLY set.

Normal hotplug memory will never have MEMBLOCK_NOMAP set in their memblock
regions. Because the flag MEMBLOCK_NOMAP was specifically designed and set
for firmware reserved memory regions. memblock_is_map_memory() can just be
skipped as its always going to be positive and that will be an optimization
for the normal hotplug memory. Like ZONE_DEVICE based memory, all normal
hotplugged memory too will not have SECTION_IS_EARLY set for their sections

Skipping memblock_is_map_memory() for all non early memory sections would
fix pfn_valid() problem for ZONE_DEVICE based memory and also improve its
performance for normal hotplug memory as well.

Cc: Catalin Marinas <>
Cc: Will Deacon <>
Cc: Ard Biesheuvel <>
Cc: Robin Murphy <>
Fixes: 73b20c84d42d ("arm64: mm: implement pte_devmap support")
Signed-off-by: Anshuman Khandual <>
 arch/arm64/mm/init.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
index 709d98fea90c..1141075e4d53 100644
--- a/arch/arm64/mm/init.c
+++ b/arch/arm64/mm/init.c
@@ -230,6 +230,18 @@ int pfn_valid(unsigned long pfn)
 	if (!valid_section(__pfn_to_section(pfn)))
 		return 0;
+	/*
+	 * ZONE_DEVICE memory does not have the memblock entries.
+	 * memblock_is_map_memory() check for ZONE_DEVICE based
+	 * addresses will always fail. Even the normal hotplugged
+	 * memory will never have MEMBLOCK_NOMAP flag set in their
+	 * memblock entries. Skip memblock search for all non early
+	 * memory sections covering all of hotplug memory including
+	 * both normal and ZONE_DEVICE based.
+	 */
+	if (!early_section(__pfn_to_section(pfn)))
+		return pfn_section_valid(__pfn_to_section(pfn), pfn);
 	return memblock_is_map_memory(addr);

  reply	other threads:[~2021-01-29  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  7:39 [PATCH 0/2] " Anshuman Khandual
2021-01-29  7:39 ` Anshuman Khandual [this message]
2021-01-29  9:58   ` [PATCH 1/2] " David Hildenbrand
2021-01-29  7:39 ` [PATCH 2/2] arm64/mm: Reorganize pfn_valid() Anshuman Khandual
2021-01-29 10:07   ` David Hildenbrand
2021-02-01  3:47     ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH 1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).