From: nkela@cisco.com (Nikunj Kela)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: add support for 43bit physical address
Date: Mon, 2 Jul 2018 14:04:51 -0700 [thread overview]
Message-ID: <20180702210451.16057-2-nkela@cisco.com> (raw)
This patch adds support for 43bit physical address. Additionally,
this patch adds support for 27bit section size. This is useful in
reducing kernel memory usage. One usecase is in kdump kernel.
Cc: xe-kernel at external.cisco.com
Cc: Nikunj Kela <nkela@cisco.com>
Signed-off-by: Nikunj Kela <nkela@cisco.com>
---
arch/arm64/Kconfig | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index edf327f..76d0bfb 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -665,6 +665,9 @@ choice
Choose the maximum physical address range that the kernel will
support.
+config ARM64_PA_BITS_43
+ bool "43-bit"
+
config ARM64_PA_BITS_48
bool "48-bit"
@@ -684,6 +687,7 @@ endchoice
config ARM64_PA_BITS
int
+ default 43 if ARM64_PA_BITS_43
default 48 if ARM64_PA_BITS_48
default 52 if ARM64_PA_BITS_52
@@ -693,6 +697,9 @@ choice
help
Choose the maximum amount of memory in a section.
+config ARM64_SEC_BITS_27
+ bool "27-bit"
+
config ARM64_SEC_BITS_30
bool "30-bit"
@@ -700,6 +707,7 @@ endchoice
config ARM64_SEC_BITS
int
+ default 27 if ARM64_SEC_BITS_27
default 30 if ARM64_SEC_BITS_30
config CPU_BIG_ENDIAN
--
2.5.0
next reply other threads:[~2018-07-02 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 21:04 Nikunj Kela [this message]
2018-07-03 14:56 ` [PATCH 2/2] arm64: add support for 43bit physical address Catalin Marinas
2018-07-03 18:35 ` Nikunj Kela (nkela)
2018-07-05 18:34 ` Catalin Marinas
2018-07-05 23:40 ` Nikunj Kela (nkela)
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=20180702210451.16057-2-nkela@cisco.com \
--to=nkela@cisco.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).