From: Alex Thorlton <athorlton@sgi.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>, Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Hedi Berriche <hedi@sgi.com>, Dimitri Sivanich <sivanich@sgi.com>,
x86@kernel.org, linux-efi@vger.kernel.org,
matt@codeblueprint.co.uk
Subject: Re: [PATCH 1/2] Remove EFI memmap quirk for UV
Date: Wed, 18 Nov 2015 11:00:13 -0600 [thread overview]
Message-ID: <20151118170013.GD161386@asylum.americas.sgi.com> (raw)
In-Reply-To: <20151118092315.GB4138@pd.tnic>
On Wed, Nov 18, 2015 at 10:23:16AM +0100, Borislav Petkov wrote:
> On Wed, Nov 18, 2015 at 09:00:47AM +0100, Ingo Molnar wrote:
> > We should at least check the BIOS version via a DMI quirk and panic in some nicely
> > informative 'upgrade your BIOS!' way to ease the transition ...
>
> Or since we're touching BIOS anyway, maybe stick a bit somewhere which
> says "EFI is fixed/quirk not needed anymore" when set and software can
> check that bit instead of checking BIOS versions...
After talking through this with Russ, we agree that we should fix this
up to play nice on UV1, without users needing to add the memmap quirk to
the command line. I'll figure out which check we need to make and spin
another version.
Thanks for looking over this, guys!
- Alex
prev parent reply other threads:[~2015-11-18 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 17:59 [PATCH 1/2] Remove EFI memmap quirk for UV Alex Thorlton
2015-11-16 17:59 ` [PATCH 2/2] Remove extra mapping code for UV MMRs Alex Thorlton
2015-11-16 18:02 ` [PATCH 1/2] Remove EFI memmap quirk for UV Thomas Gleixner
2015-11-17 9:52 ` Matt Fleming
2015-11-17 18:24 ` Alex Thorlton
2015-11-17 19:32 ` Borislav Petkov
2015-11-18 1:56 ` Alex Thorlton
2015-11-18 8:00 ` Ingo Molnar
2015-11-18 9:23 ` Borislav Petkov
2015-11-18 17:00 ` Alex Thorlton [this message]
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=20151118170013.GD161386@asylum.americas.sgi.com \
--to=athorlton@sgi.com \
--cc=bp@alien8.de \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--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