Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755293AbbKRIAx (ORCPT ); Wed, 18 Nov 2015 03:00:53 -0500 Received: from mail-wm0-f45.google.com ([74.125.82.45]:36594 "EHLO mail-wm0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755125AbbKRIAv (ORCPT ); Wed, 18 Nov 2015 03:00:51 -0500 Date: Wed, 18 Nov 2015 09:00:47 +0100 From: Ingo Molnar To: Alex Thorlton Cc: Borislav Petkov , linux-kernel@vger.kernel.org, Matt Fleming , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Hedi Berriche , Dimitri Sivanich , x86@kernel.org, linux-efi@vger.kernel.org Subject: Re: [PATCH 1/2] Remove EFI memmap quirk for UV Message-ID: <20151118080047.GA22813@gmail.com> References: <1447696781-159611-1-git-send-email-athorlton@sgi.com> <20151117193258.GB9374@pd.tnic> <20151118015630.GC161386@asylum.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151118015630.GC161386@asylum.americas.sgi.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1819 Lines: 41 * Alex Thorlton wrote: > 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. So how about older UV systems that don't want to upgrade the BIOS for whatever reason but wants to upgrade to a new distro will have a non-booting kernel? Also, what about UV systems that compile their own kernels for whatever reason? > We won't be checking this down into the stable branches. Mainly just planning > ahead here for future UV and distro releases. But eventually the new kernel will become the stable kernel, and we'll be breaking old systems with old BIOSen, which is not good. 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 ... Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/