[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39ac78ea-1ee5-8911-1208-c56e57df7338@kernel.org>
Date: Tue, 1 Nov 2022 07:50:04 +0100
From: Jiri Slaby <jirislaby@...nel.org>
To: Alexander Lobakin <alexandr.lobakin@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>
Cc: "H. Peter Anvin" <hpa@...or.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Tony Luck <tony.luck@...el.com>,
Kees Cook <keescook@...omium.org>,
Masahiro Yamada <masahiroy@...nel.org>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86/boot: robustify calling startup_{32,64}() from
the decompressor code
On 01. 11. 22, 7:47, Jiri Slaby wrote:
> Tested-by: Jiri Slaby <jirislaby@...nel.org>
FWIW that means: tested with gcc-lto which deliberately stores
startup_64() randomly, not to the beginning of vmlinux.
--
js
suse labs
Powered by blists - more mailing lists