From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3 0/8] 52-bit kernel VAs for arm64
Date: Fri, 7 Sep 2018 15:45:31 -0400 [thread overview]
Message-ID: <00073c2c-9e9f-d194-100a-735f420fa3b6@redhat.com> (raw)
In-Reply-To: <20180907141305.dwuwxj22vyqtbq4m@capper-debian.cambridge.arm.com>
On 09/07/2018 10:13 AM, Steve Capper wrote:
> On Fri, Sep 07, 2018 at 02:25:49AM -0400, Jon Masters wrote:
>> On 05/10/2018 12:23 PM, Steve Capper wrote:
>>
>>> This patch series brings 52-bit kernel VA support to arm64; if supported
>>> at boot time. A new kernel option CONFIG_ARM64_VA_BITS_52 is available
>>> when configured with a 64KB PAGE_SIZE (as on ARMv8.2-LPA, 52-bit VAs are
>>> only allowed when running with a 64KB granule).
>>
>> What's the plan with this series?
> The series is quite heavyweight in that it affects quite a few subtle
> areas of the kernel.
Sure. I've looked through the KASAN changes and the memory map changes.
But this is all the more reason I want to see it upstream due to various
downstream dependencies that would like to receive this support.
> Catalin can better comment, but my understanding is that the plan is to
> hold off expanding the kernel VA space until strictly necessary.
Unless or until this happens, what's the case for machines with
populated memory exceeding 48 bits? There's no way to setup the linear
map so we can't use that memory, correct? I think that's a problem.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
prev parent reply other threads:[~2018-09-07 19:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:23 [PATCH V3 0/8] 52-bit kernel VAs for arm64 Steve Capper
2018-05-10 16:23 ` [PATCH v3 1/8] arm/arm64: KVM: Formalise end of direct linear map Steve Capper
2018-05-10 17:11 ` Marc Zyngier
2018-05-11 9:46 ` Steve Capper
2018-05-11 10:00 ` Steve Capper
2018-05-10 16:23 ` [PATCH v3 2/8] arm64: mm: Flip kernel VA space Steve Capper
2018-05-10 16:23 ` [PATCH v3 3/8] arm64: kasan: Switch to using KASAN_SHADOW_OFFSET Steve Capper
2018-05-10 16:23 ` [PATCH v3 4/8] arm64: mm: Replace fixed map BUILD_BUG_ON's with BUG_ON's Steve Capper
2018-05-10 16:23 ` [PATCH v3 5/8] arm64: dump: Make kernel page table dumper dynamic again Steve Capper
2018-05-10 16:23 ` [PATCH v3 6/8] arm64: module-plts: Extend veneer to address 52-bit VAs Steve Capper
2018-05-10 22:01 ` Ard Biesheuvel
2018-05-11 10:11 ` Steve Capper
2018-05-14 10:31 ` Ard Biesheuvel
2018-05-10 16:23 ` [PATCH v3 7/8] arm64: mm: Make VA space size variable Steve Capper
2018-05-10 16:23 ` [PATCH v3 8/8] arm64: mm: Add 48/52-bit kernel VA support Steve Capper
2018-09-07 6:25 ` [PATCH V3 0/8] 52-bit kernel VAs for arm64 Jon Masters
2018-09-07 14:13 ` Steve Capper
2018-09-07 19:45 ` Jon Masters [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=00073c2c-9e9f-d194-100a-735f420fa3b6@redhat.com \
--to=jcm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.