From: steve.capper@arm.com (Steve Capper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] arm64: mm: Activate 52-bit userspace VA support
Date: Wed, 29 Aug 2018 13:45:43 +0100 [thread overview]
Message-ID: <20180829124543.25314-6-steve.capper@arm.com> (raw)
In-Reply-To: <20180829124543.25314-1-steve.capper@arm.com>
We have all the pieces in place now to support a 52-bit userspace VA.
This patch enables this logic for systems running with a 48-bit VA and a
64KB PAGE_SIZE.
Signed-off-by: Steve Capper <steve.capper@arm.com>
---
arch/arm64/Kconfig | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 29e75b47becd..2561b541c9df 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -691,6 +691,10 @@ config ARM64_PA_BITS_52
endchoice
+config ARM64_TRY_52BIT_VA
+ def_bool y
+ depends on ARM64_VA_BITS_48 && ARM64_64K_PAGES
+
config ARM64_PA_BITS
int
default 48 if ARM64_PA_BITS_48
--
2.11.0
next prev parent reply other threads:[~2018-08-29 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 12:45 [PATCH 0/5] 52-bit userspace VAs Steve Capper
2018-08-29 12:45 ` [PATCH 1/5] arm64: mm: Introduce DEFAULT_MAP_WINDOW Steve Capper
2018-08-29 12:45 ` [PATCH 2/5] arm64: mm: introduce 52-bit userspace support Steve Capper
2018-09-21 17:40 ` Catalin Marinas
2018-09-27 13:50 ` Steve Capper
2018-09-27 14:48 ` Steve Capper
2018-10-01 10:28 ` Catalin Marinas
2018-10-01 10:50 ` Steve Capper
2018-08-29 12:45 ` [PATCH 3/5] arm64: mm: Copy over arch_get_unmapped_area Steve Capper
2018-09-07 6:15 ` Jon Masters
2018-09-07 14:04 ` Steve Capper
2018-10-17 14:52 ` Steve Capper
2018-08-29 12:45 ` [PATCH 4/5] arm64: mmap: Allow for "high" 52-bit VA allocations Steve Capper
2018-09-21 17:11 ` Catalin Marinas
2018-08-29 12:45 ` Steve Capper [this message]
2018-09-07 6:22 ` [PATCH 0/5] 52-bit userspace VAs Jon Masters
2018-09-07 13:59 ` Steve Capper
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=20180829124543.25314-6-steve.capper@arm.com \
--to=steve.capper@arm.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).