[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190211110451.GD19618@zn.tnic>
Date: Mon, 11 Feb 2019 12:04:51 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc: Chao Fan <fanc.fnst@...fujitsu.com>,
Guenter Roeck <linux@...ck-us.net>,
Thomas Gleixner <tglx@...utronix.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
"Lendacky, Thomas" <thomas.lendacky@....com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
caoj.fnst@...fujitsu.com, Juergen Gross <jgross@...e.com>,
Ingo Molnar <mingo@...nel.org>,
Kees Cook <keescook@...omium.org>,
the arch/x86 maintainers <x86@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>,
linux-tip-commits@...r.kernel.org,
Matt Fleming <matt@...eblueprint.co.uk>
Subject: Re: [tip:x86/boot] x86/boot: Early parse RSDP and save it in
boot_params
On Mon, Feb 11, 2019 at 10:46:18AM +0000, Ard Biesheuvel wrote:
> As I pointed out in my previous reply, systab will be the wrong type
> on 32-bit firmware, it needs to be efi_system_table_32_t
Yeah, that seems to work. It boots now and it says:
[ 0.000000] efi: No EFI runtime due to 32/64-bit mismatch with kernel
Do you think we should mirror that behavoir early too, so that people
don't get any ideas?
Or should we limit that only to the RDSP address computation and
anything else where kernel and EFI bitness mismatch should be disabled?
Thanks Ard!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists