From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] arm64: defconfig: enable 48-bit VA by default
Date: Mon, 03 Aug 2015 10:00:17 +0200 [thread overview]
Message-ID: <1950491.fy9Zn5k0xY@wuerfel> (raw)
In-Reply-To: <CAKv+Gu89UGzL9=0tYjQmv9dX7KOsfobpO4zG1E8X0g4W9u5Bkg@mail.gmail.com>
On Sunday 02 August 2015 08:19:07 Ard Biesheuvel wrote:
> >> >>
> >> >> PHYS_OFFSET = PHYS_OFFSET0 = memstart_addr
> >> >> PHYS_OFFSET1 = memstart_addr + 2 GB
> >> >> PHYS_OFFSET2 = memstart_addr + 32 GB
> >> >>
> >> >> and only if the ARM recommended physical memory map is detected (with
> >> >> memstart_addr @ 0x8000_0000), switch to
> >> >>
> >> >> PHYS_OFFSET = PHYS_OFFSET0 = memstart_addr
> >> >> PHYS_OFFSET1 = memstart_addr + 30 GB
> >> >> PHYS_OFFSET2 = memstart_addr + 480 GB
> >> >
> >> > I don't really like such complexity when all you need on arm64 is to
> >> > enable 48-bit VA (though it would be interesting to benchmark it).
> >
> > More importantly, hardwiring this in virt_to_phys() would mean we can
> > no longer run a kernel with this hack turned on with systems that have
> > contiguous memory or any other layout besides the one from the document.
> >
>
> Well the hack, if enabled, would be turned on dynamically iff the
> exact layout from the recommendation is detected, and the kernel is
> loaded right at the base of DRAM.
> Note that the first layout I presented is effectively the current
> linear mapping, but with three steps.
Ok, I see. So it would work everywhere, at the price of another conditional
for each virt_to_phys, either runtime or by binary patching at boottime.
Arnd
prev parent reply other threads:[~2015-08-03 8:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 19:49 [RFC] arm64: defconfig: enable 48-bit VA by default Stuart Yoder
2015-07-23 12:44 ` Marc Zyngier
2015-07-23 13:59 ` Stuart Yoder
2015-07-29 19:27 ` Stuart Yoder
2015-07-29 19:51 ` Ard Biesheuvel
2015-07-29 20:49 ` Stuart Yoder
2015-07-29 20:57 ` Arnd Bergmann
2015-07-29 20:58 ` Ard Biesheuvel
2015-07-30 10:13 ` Catalin Marinas
2015-07-30 14:52 ` Stuart Yoder
2015-07-30 16:12 ` Catalin Marinas
2015-07-30 16:32 ` Stuart Yoder
2015-07-30 16:41 ` Catalin Marinas
2015-07-30 17:45 ` Ard Biesheuvel
2015-07-30 18:10 ` Stuart Yoder
2015-08-07 19:01 ` Stuart Yoder
2015-08-08 8:20 ` Ard Biesheuvel
2015-08-13 19:24 ` Stuart Yoder
2015-08-14 12:15 ` Ard Biesheuvel
2015-08-14 13:24 ` Catalin Marinas
2015-08-14 13:55 ` Ard Biesheuvel
2015-08-14 15:37 ` Catalin Marinas
2015-07-30 19:27 ` Ard Biesheuvel
2015-07-31 12:53 ` Catalin Marinas
2015-07-31 13:10 ` Ard Biesheuvel
2015-07-31 13:22 ` Catalin Marinas
2015-07-31 13:30 ` Ard Biesheuvel
2015-08-01 21:08 ` Arnd Bergmann
2015-08-02 6:19 ` Ard Biesheuvel
2015-08-03 8:00 ` Arnd Bergmann [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=1950491.fy9Zn5k0xY@wuerfel \
--to=arnd@arndb.de \
--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