From: Baoquan He <bhe@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@kernel.org, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level kernel checking
Date: Tue, 4 Sep 2018 15:16:20 +0800 [thread overview]
Message-ID: <20180904071620.GL1740@192.168.1.3> (raw)
In-Reply-To: <44fc1530-eb88-d8c5-7465-e48c91799a98@zytor.com>
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
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2018-09-04 7:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:16 [PATCH 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Baoquan He
2018-08-29 14:16 ` [PATCH 1/3] x86/boot: Add bit fields into xloadflags for 5-level kernel checking Baoquan He
2018-09-04 2:41 ` H. Peter Anvin
2018-09-04 3:44 ` Baoquan He
2018-09-04 4:13 ` H. Peter Anvin
2018-09-04 5:20 ` Baoquan He
2018-09-04 5:46 ` H. Peter Anvin
2018-09-04 6:06 ` Baoquan He
2018-09-04 6:36 ` H. Peter Anvin
2018-09-04 7:16 ` Baoquan He [this message]
2018-09-04 8:42 ` Kirill A. Shutemov
2018-09-05 4:06 ` H. Peter Anvin
2018-09-05 8:02 ` Thomas Gleixner
2018-09-26 7:54 ` Baoquan He
2018-08-29 14:16 ` [PATCH 2/3] x86/kexec/64: Error out if try to jump to old 4-level kernel from 5-level kernel Baoquan He
2018-08-29 14:16 ` [PATCH 3/3] x86/kdump/64: Change the upper limit of crashkernel reservation Baoquan He
2018-08-30 13:50 ` Kirill A. Shutemov
2018-08-30 14:13 ` Baoquan He
2018-08-30 13:58 ` [PATCH 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Kirill A. Shutemov
2018-08-30 14:12 ` Baoquan He
2018-08-30 14:27 ` Kirill A. Shutemov
2018-08-30 14:57 ` Baoquan He
2018-08-30 15:01 ` Baoquan He
2018-09-02 20:45 ` Kirill A. Shutemov
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=20180904071620.GL1740@192.168.1.3 \
--to=bhe@redhat.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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