[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171013040354.yscl4gif5vt3tzgv@node.shutemov.name>
Date: Fri, 13 Oct 2017 07:03:54 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: Dave Hansen <dave.hansen@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...capital.net>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Borislav Petkov <bp@...e.de>, Andi Kleen <ak@...ux.intel.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH, RFC] x86/boot/compressed/64: Handle 5-level paging boot
if kernel is above 4G
On Thu, Oct 12, 2017 at 06:07:36PM -0500, Eric W. Biederman wrote:
> "Kirill A. Shutemov" <kirill@...temov.name> writes:
>
> > On Mon, Oct 09, 2017 at 09:54:53AM -0700, Dave Hansen wrote:
> >> On 10/09/2017 09:09 AM, Kirill A. Shutemov wrote:
> >> > Apart from trampoline itself we also need place to store top level page
> >> > table in lower memory as we don't have a way to load 64-bit value into
> >> > CR3 from 32-bit mode. We only really need 8-bytes there as we only use
> >> > the very first entry of the page table.
> >>
> >> Oh, and this is why you have to move "lvl5_pgtable" out of the kernel image?
> >
> > Right. I initialize the new location of top level page table directly.
>
> So just a quick note. I have a fuzzy memory of people loading their
> kernels above 4G physical because they did not have any memory below
> 4G.
>
> That might be a very specialized case if my memory is correct because
> cpu startup has to have a trampoline below 1MB. So I don't know how
> that works. But I do seem to remember someone mentioning it.
>
> Is there really no way to switch to 5 level paging other than to drop to
> 32bit mode and disable paging? The x86 architecture does some very
> bizarre things so I can believe it but that seems like a lot of work to
> get somewhere.
The spec[1] is pretty clear on this, see section 2.2.2:
The processor allows software to modify CR4.LA57 only outside of
IA-32e mode. In IA-32e mode, an attempt to modify CR4.LA57 using
the MOV CR instruction causes a general-protection exception
(#GP).
[1] https://software.intel.com/sites/default/files/managed/2b/80/5-level_paging_white_paper.pdf
--
Kirill A. Shutemov
Powered by blists - more mailing lists