From: David Hildenbrand <david@redhat.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mike Rapoport <rppt@linux.ibm.com>, Will Deacon <will@kernel.org>,
kvmarm <kvmarm@lists.cs.columbia.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [RFC/RFT PATCH 1/3] memblock: update initialization of reserved pages
Date: Thu, 15 Apr 2021 11:30:12 +0200 [thread overview]
Message-ID: <f5503130-c0e7-329f-86c4-727ece1c860f@redhat.com> (raw)
In-Reply-To: <YHdPmtpzFxHE9mAt@kernel.org>
> Not sure we really need a new pagetype here, PG_Reserved seems to be quite
> enough to say "don't touch this". I generally agree that we could make
> PG_Reserved a PageType and then have several sub-types for reserved memory.
> This definitely will add clarity but I'm not sure that this justifies
> amount of churn and effort required to audit uses of PageResrved().
>
>> Then, we could mostly avoid having to query memblock at runtime to figure
>> out that this is special memory. This would obviously be an extension to
>> this series. Just a thought.
>
> Stop pushing memblock out of kernel! ;-)
Can't stop. Won't stop. :D
It's lovely for booting up a kernel until we have other data-structures
in place ;)
--
Thanks,
David / dhildenb
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-15 9:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 17:26 [RFC/RFT PATCH 0/3] arm64: drop pfn_valid_within() and simplify pfn_valid() Mike Rapoport
2021-04-07 17:26 ` [RFC/RFT PATCH 1/3] memblock: update initialization of reserved pages Mike Rapoport
2021-04-08 5:16 ` Anshuman Khandual
2021-04-08 5:48 ` Mike Rapoport
2021-04-14 15:12 ` David Hildenbrand
2021-04-14 15:27 ` Ard Biesheuvel
2021-04-14 15:52 ` David Hildenbrand
2021-04-14 20:24 ` Mike Rapoport
2021-04-15 9:30 ` David Hildenbrand [this message]
2021-04-16 11:44 ` Mike Rapoport
2021-04-16 11:54 ` David Hildenbrand
2021-04-14 20:11 ` Mike Rapoport
2021-04-14 20:06 ` Mike Rapoport
2021-04-07 17:26 ` [RFC/RFT PATCH 2/3] arm64: decouple check whether pfn is normal memory from pfn_valid() Mike Rapoport
2021-04-08 5:14 ` Anshuman Khandual
2021-04-08 6:00 ` Mike Rapoport
2021-04-14 15:58 ` David Hildenbrand
2021-04-14 20:29 ` Mike Rapoport
2021-04-15 9:31 ` David Hildenbrand
2021-04-16 11:40 ` Mike Rapoport
2021-04-07 17:26 ` [RFC/RFT PATCH 3/3] arm64: drop pfn_valid_within() and simplify pfn_valid() Mike Rapoport
2021-04-08 5:12 ` Anshuman Khandual
2021-04-08 6:17 ` Mike Rapoport
2021-04-08 5:19 ` [RFC/RFT PATCH 0/3] " Anshuman Khandual
2021-04-08 6:27 ` Mike Rapoport
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=f5503130-c0e7-329f-86c4-727ece1c860f@redhat.com \
--to=david@redhat.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).