From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Ard Biesheuvel <ardb@kernel.org>, Marc Zyngier <maz@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: Force SPARSEMEM_VMEMMAP as the only memory management model
Date: Fri, 23 Apr 2021 18:09:46 +0100 [thread overview]
Message-ID: <161919777114.6013.6751893244325348911.b4-ty@arm.com> (raw)
In-Reply-To: <20210420093559.23168-1-catalin.marinas@arm.com>
On Tue, 20 Apr 2021 10:35:59 +0100, Catalin Marinas wrote:
> Currently arm64 allows a choice of FLATMEM, SPARSEMEM and
> SPARSEMEM_VMEMMAP. However, only the latter is tested regularly. FLATMEM
> does not seem to boot in certain configurations (guest under KVM with
> Qemu as a VMM). Since the reduction of the SECTION_SIZE_BITS to 27 (4K
> pages) or 29 (64K page), there's little argument against the memory
> wasted by the mem_map array with SPARSEMEM.
>
> [...]
Applied to arm64 (for-next/core).
[1/1] arm64: Force SPARSEMEM_VMEMMAP as the only memory management model
https://git.kernel.org/arm64/c/782276b4d0ad
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-04-23 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 9:35 [PATCH] arm64: Force SPARSEMEM_VMEMMAP as the only memory management model Catalin Marinas
2021-04-20 10:19 ` Will Deacon
2021-04-20 10:28 ` Ard Biesheuvel
2021-04-20 10:47 ` Marc Zyngier
2021-04-21 4:48 ` Anshuman Khandual
2021-04-21 13:02 ` Catalin Marinas
2021-04-22 3:04 ` Anshuman Khandual
2021-04-22 10:08 ` Mike Rapoport
2021-04-23 17:09 ` Catalin Marinas [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=161919777114.6013.6751893244325348911.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).