From: cernekee@gmail.com (Kevin Cernekee)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multi-v7 build
Date: Thu, 11 Sep 2014 19:22:42 -0700 [thread overview]
Message-ID: <1410488562-21863-3-git-send-email-cernekee@gmail.com> (raw)
In-Reply-To: <1410488562-21863-1-git-send-email-cernekee@gmail.com>
ARMv7 chips with LPAE can often benefit from SPARSEMEM, as portions of
system memory can be located deep in the 36-bit address space. Allow
FLATMEM or SPARSEMEM to be selectable at compile time; FLATMEM remains
the default.
Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
---
arch/arm/Kconfig | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index c3daeaf..db7614e 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -821,6 +821,8 @@ config ARCH_MULTI_V7
bool "ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)"
default y
select ARCH_MULTI_V6_V7
+ select ARCH_FLATMEM_ENABLE
+ select ARCH_SPARSEMEM_ENABLE
select CPU_V7
select HAVE_SMP
@@ -1632,6 +1634,9 @@ config OABI_COMPAT
config ARCH_HAS_HOLES_MEMORYMODEL
bool
+config ARCH_FLATMEM_ENABLE
+ bool
+
config ARCH_SPARSEMEM_ENABLE
bool
--
1.7.9.5
next prev parent reply other threads:[~2014-09-12 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 2:22 [PATCH 1/3] ARM: Add default SPARSEMEM settings Kevin Cernekee
2014-09-12 2:22 ` [PATCH 2/3] ARM: Remove redundant ARCH_SPARSEMEM_DEFAULT setting Kevin Cernekee
2014-10-31 20:12 ` Gregory Fong
2014-09-12 2:22 ` Kevin Cernekee [this message]
2014-10-31 20:12 ` [PATCH 3/3] ARM: Allow either FLATMEM or SPARSEMEM on the multi-v7 build Gregory Fong
2014-10-31 20:48 ` Arnd Bergmann
2014-10-31 20:11 ` [PATCH 1/3] ARM: Add default SPARSEMEM settings Gregory Fong
2014-10-31 20:47 ` Arnd Bergmann
2014-10-31 21:00 ` Russell King - ARM Linux
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=1410488562-21863-3-git-send-email-cernekee@gmail.com \
--to=cernekee@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).