[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170928132608.priml7nc7dmo5r6d@node.shutemov.name>
Date: Thu, 28 Sep 2017 16:26:08 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Ingo Molnar <mingo@...nel.org>
Cc: "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>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Borislav Petkov <bp@...e.de>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv7 12/19] x86/mm: Adjust virtual address space layout in
early boot.
On Thu, Sep 28, 2017 at 10:31:55AM +0200, Ingo Molnar wrote:
>
> * Kirill A. Shutemov <kirill.shutemov@...ux.intel.com> wrote:
>
> > We need to adjust virtual address space to support switching between
> > paging modes.
> >
> > The adjustment happens in __startup_64().
>
> > +#ifdef CONFIG_X86_5LEVEL
> > + if (__read_cr4() & X86_CR4_LA57) {
> > + pgtable_l5_enabled = 1;
> > + pgdir_shift = 48;
> > + ptrs_per_p4d = 512;
> > + }
> > +#endif
>
> So CR4 really sucks as a parameter passing interface - was it us who enabled LA57
> in the early boot code, right? Couldn't we add a flag which gets set there, or
> something?
It's not necessary that we enabled LA57. At least I tried to write code
that doesn't assume this. We enable it if bootloader haven't done this
already for us.
What is so awful about using CR4 as passing interface? It's one-time
check, so performance shouldn't be an issue.
--
Kirill A. Shutemov
Powered by blists - more mailing lists