[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACi5LpOJe+dpJBeuZxm80pd0dX9-V=DQv_R3TDzFmn4Q1XA1SA@mail.gmail.com>
Date: Mon, 8 May 2017 00:07:18 +0530
From: Bhupesh Sharma <bhsharma@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Matt Fleming <matt@...eblueprint.co.uk>,
Baoquan He <bhe@...hat.com>, linux-kernel@...r.kernel.org,
Dave Young <dyoung@...hat.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Garnier <thgarnie@...gle.com>,
Kees Cook <keescook@...omium.org>, x86@...nel.org,
linux-efi@...r.kernel.org, Alex Thorlton <athorlton@....com>,
Russ Anderson <rja@....com>,
Dimitri Sivanich <sivanich@....com>,
Mike Travis <travis@....com>
Subject: Re: [PATCH v2] x86/efi: Correct ident mapping of efi old_map when
kalsr enabled
On Sat, May 6, 2017 at 5:06 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Fri, May 05, 2017 at 09:42:14PM +0100, Matt Fleming wrote:
>> (Including the folks from SGI since this was hit on a UV system)
>
> Wasn't there a BIOS fix supplied at some point which obviated the need
> to boot with efi=old_map on SGI boxes?
>
AFAICR, the bios fixes were provided only for SGI boxes with BIOS
version greater than or equal to UV2 (so upstream with recent bios
works on UV2, UV3, and UV4 hardware platforms, both with old and new
mapping, with new mapping being the default), however the UV1
platforms still use efi=old_map
Also as mentioned above since commit
caef78b6cdeddf4ad364f95910bba6b43b8eb9bf fixed the efi=old_map support
on UV systems even with new bios, they should ideally all boot up
properly in upstream both with 'nokaslr' and without 'nokaslr' in the
bootargs when efi=old_map is used.
Regards,
Bhupesh
Powered by blists - more mailing lists