[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180904071620.GL1740@192.168.1.3>
Date: Tue, 4 Sep 2018 15:16:20 +0800
From: Baoquan He <bhe@...hat.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: kirill.shutemov@...ux.intel.com, x86@...nel.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
tglx@...utronix.de, mingo@...nel.org
Subject: Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level
kernel checking
On 09/03/18 at 11:36pm, H. Peter Anvin wrote:
> On 09/03/18 23:06, Baoquan He wrote:
> >>
> >> That makes no sense. I'm talking about *entering* the kernel; the second
> >> kernel should switch to 5-level mode as necessary.
> >
> > OK, I didn't get your point. I forget what difficulty was met so that
> > Kirill need to take this way. In that way, we will never have chance to
> > put kernel above 64TB even from 5-level kernel to jump to 5-level
> > kernel.
> >
>
> It sounds like you have no intent of doing that anyway? Now, that is
> something one could use an xloadflag for, as I previously stated: "this kernel
> supports being entered in 5-level mode."
I am willing to take any better way to improve. May need to make clear
why that was not taken. Not sure if Kirill still has the details.
Thanks
Baoquan
Powered by blists - more mailing lists