[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180706181110.GC25550@tassilo.jf.intel.com>
Date: Fri, 6 Jul 2018 11:11:10 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: "Kirill A. Shutemov" <kirill@...temov.name>
Cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Gabriel C <nix.or.die@...il.com>,
Benjamin Gilbert <bgilbert@...hat.com>,
linux-x86_64@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, X86 ML <x86@...nel.org>,
bero@...dev.ch, Michal Marek <michal.lkml@...kovi.net>
Subject: Re: 4.17.x won't boot due to "x86/boot/compressed/64: Handle 5-level
paging boot if kernel is above 4G"
> At least we need to make user aware about risk of setting custom flags.
There are valid use cases to override the flags. I use it sometimes too,
and know some other people do to.
But you need to know what you're doing.
Perhaps a warning during build would be reasonable. So if you ask
for a build log you would see it.
-Andi
Powered by blists - more mailing lists