From: Borislav Petkov <bp@alien8.de>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Garnier <thgarnie@google.com>,
Kees Cook <keescook@chromium.org>,
x86@kernel.org, linux-efi@vger.kernel.org,
Alex Thorlton <athorlton@sgi.com>, Russ Anderson <rja@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>, Mike Travis <travis@sgi.com>
Subject: Re: [PATCH v2] x86/efi: Correct ident mapping of efi old_map when kalsr enabled
Date: Sat, 6 May 2017 01:36:20 +0200 [thread overview]
Message-ID: <20170505233620.eka5md5mmnp4ituz@pd.tnic> (raw)
In-Reply-To: <20170505204214.GB5225@codeblueprint.co.uk>
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?
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-05-05 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 12:07 Baoquan He
2017-05-01 14:21 ` Thomas Garnier
2017-05-05 20:42 ` Matt Fleming
2017-05-05 23:36 ` Borislav Petkov [this message]
2017-05-07 18:37 ` Bhupesh Sharma
2017-05-08 1:36 ` Baoquan He
2017-05-08 15:25 ` Borislav Petkov
2017-05-09 3:30 ` Baoquan He
2017-05-10 2:30 ` Baoquan He
2017-05-08 3:18 ` Russ Anderson
2017-05-11 9:32 ` 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=20170505233620.eka5md5mmnp4ituz@pd.tnic \
--to=bp@alien8.de \
--cc=ard.biesheuvel@linaro.org \
--cc=athorlton@sgi.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=travis@sgi.com \
--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
all inboxes | Powered by JetHome®