From: Baoquan He <bhe@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, kirill.shutemov@linux.intel.com,
mingo@kernel.org, bp@alien8.de, hpa@zytor.com, dyoung@redhat.com,
x86@kernel.org
Subject: Re: [PATCH v3 1/3] x86/boot: Add xloadflags bits for 5-level kernel checking
Date: Sat, 6 Apr 2019 09:40:53 +0800 [thread overview]
Message-ID: <20190406014053.GW7627@MiWiFi-R3L-srv> (raw)
In-Reply-To: <alpine.DEB.2.21.1904052220480.1802@nanos.tec.linutronix.de>
On 04/05/19 at 10:23pm, Thomas Gleixner wrote:
> On Tue, 12 Mar 2019, Baoquan He wrote:
>
> > Add two bits XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
> > Bit XLF_5LEVEL indicates if 5-level related code is contained
> > in this kernel.
> > Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_5LEVEL=y is set.
> >
> > They are being used in later patch to check if kexec/kdump kernel
> > is loaded in right place.
>
> Only XLF_5LEVEL is checked. So what's the second flag for?
I put the explanation why only XLF_5LEVEL is checked in cover letter.
Will add them in this log.
next prev parent reply other threads:[~2019-04-06 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 10:30 [PATCH v3 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Baoquan He
2019-03-12 10:30 ` [PATCH v3 1/3] x86/boot: Add xloadflags bits for 5-level kernel checking Baoquan He
2019-04-05 20:23 ` Thomas Gleixner
2019-04-06 1:40 ` Baoquan He [this message]
2019-03-12 10:30 ` [PATCH v3 2/3] x86/kexec/64: Error out if try to jump to old 4-level kernel from 5-level kernel Baoquan He
2019-04-05 20:38 ` Thomas Gleixner
2019-04-06 1:39 ` Baoquan He
2019-03-12 10:30 ` [PATCH v3 3/3] x86/kdump/64: Change the upper limit of crashkernel reservation Baoquan He
2019-04-04 2:20 ` [PATCH v3 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Baoquan He
2019-04-06 1:43 ` Baoquan He
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=20190406014053.GW7627@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).