From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mike Rapoport <rppt@kernel.org>, David Hildenbrand <david@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC V2] mm: Enable generic pfn_valid() to handle early sections with memmap holes
Date: Thu, 22 Apr 2021 15:29:10 +0530 [thread overview]
Message-ID: <d82ee03f-71da-e0ab-def0-306236b00e8d@arm.com> (raw)
In-Reply-To: <YIFFIiuy+z3WLHDi@kernel.org>
On 4/22/21 3:12 PM, Mike Rapoport wrote:
> The "generic" pfn_valid() is only available with CONFIG_SPARSEMEM.
> With FLATMEM it's wild west:
>
> $ git grep -w "define pfn_valid" arch/*/include/asm/ | wc -l
> 22
>
> This would actually mean that we still need arm64::pfn_valid() for the
> FLATMEM case.
SPARSEMEM would be the only memory model going forward.
https://patchwork.kernel.org/project/linux-arm-kernel/patch/20210420093559.23168-1-catalin.marinas@arm.com/
next prev parent reply other threads:[~2021-04-22 9:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 6:18 [PATCH v3 0/4] arm64: drop pfn_valid_within() and simplify pfn_valid() Mike Rapoport
2021-04-22 6:18 ` [PATCH v3 1/4] include/linux/mmzone.h: add documentation for pfn_valid() Mike Rapoport
2021-04-22 6:19 ` [PATCH v3 2/4] memblock: update initialization of reserved pages Mike Rapoport
2021-04-22 6:19 ` [PATCH v3 3/4] arm64: decouple check whether pfn is in linear map from pfn_valid() Mike Rapoport
2021-04-22 8:57 ` David Hildenbrand
2021-04-22 6:19 ` [PATCH v3 4/4] arm64: drop pfn_valid_within() and simplify pfn_valid() Mike Rapoport
2021-04-22 7:50 ` [RFC V2] mm: Enable generic pfn_valid() to handle early sections with memmap holes Anshuman Khandual
2021-04-22 8:27 ` Mike Rapoport
2021-04-22 11:23 ` Anshuman Khandual
2021-04-22 12:19 ` Mike Rapoport
2021-04-22 9:03 ` David Hildenbrand
2021-04-22 9:42 ` Mike Rapoport
2021-04-22 9:48 ` David Hildenbrand
2021-04-22 10:03 ` Mike Rapoport
2021-04-22 9:59 ` Anshuman Khandual [this message]
2021-05-24 4:58 ` Anshuman Khandual
2021-05-24 6:52 ` Mike Rapoport
2021-05-25 6:00 ` Anshuman Khandual
2021-05-25 6:32 ` Mike Rapoport
2021-05-25 9:52 ` Anshuman Khandual
2021-05-25 10:03 ` Mike Rapoport
2021-05-25 10:04 ` David Hildenbrand
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=d82ee03f-71da-e0ab-def0-306236b00e8d@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--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