From: Alex Thorlton <athorlton@sgi.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>,
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
Subject: Re: [PATCH 1/2] Remove EFI memmap quirk for UV
Date: Tue, 17 Nov 2015 19:56:30 -0600 [thread overview]
Message-ID: <20151118015630.GC161386@asylum.americas.sgi.com> (raw)
In-Reply-To: <20151117193258.GB9374@pd.tnic>
On Tue, Nov 17, 2015 at 08:32:59PM +0100, Borislav Petkov wrote:
> On Mon, Nov 16, 2015 at 11:59:40AM -0600, Alex Thorlton wrote:
> > Commit a5d90c923bcf ("x86/efi: Quirk out SGI UV") added a quirk to
> > efi_apply_memmap_quirks to force SGI UV systems to fall back to the old
> > EFI memmap mechanism. We have a BIOS fix for this issue now, so we no
> > longer need this quirk in the kernel.
>
> So does that mean that all UV systems out there will get the BIOS update
> or at least will have a BIOS update available so that we won't need the
> quirk at all?
Essentially, yes. The BIOS fix isn't available on UV1, but that's older
hardware at this point, and the distro kernels that run on it will
still have the quirk. This change is mainly so that we can get the
un-quirked code pulled in for the next major distro release.
We won't be checking this down into the stable branches. Mainly just
planning ahead here for future UV and distro releases.
- Alex
next prev parent reply other threads:[~2015-11-18 1:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 17:59 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 [this message]
2015-11-18 8:00 ` Ingo Molnar
2015-11-18 9:23 ` Borislav Petkov
2015-11-18 17:00 ` Alex Thorlton
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=20151118015630.GC161386@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.fleming@intel.com \
--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
all inboxes | Powered by JetHome®