From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752584Ab3KNBk5 (ORCPT ); Wed, 13 Nov 2013 20:40:57 -0500 Received: from g4t0015.houston.hp.com ([15.201.24.18]:45360 "EHLO g4t0015.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751150Ab3KNBkr (ORCPT ); Wed, 13 Nov 2013 20:40:47 -0500 Date: Wed, 13 Nov 2013 18:40:43 -0700 From: jerry.hoemann@hp.com To: "H. Peter Anvin" Cc: rob@landley.net, tglx@linutronix.de, mingo@redhat.com, x86@kernel.org, matt.fleming@intel.com, yinghai@kernel.org, penberg@kernel.org, akpm@linux-foundation.org, linux-doc@vger.kernel.org, linux-efi@vger.kernel.org, vgoyal@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] Early use of boot service memory Message-ID: <20131114014043.GD25344@anatevka.fc.hp.com> Reply-To: jerry.hoemann@hp.com References: <1384222558-38527-1-git-send-email-jerry.hoemann@hp.com> <20131113224503.GB25344@anatevka.fc.hp.com> <52840206.5020006@zytor.com> <20131113235708.GC25344@anatevka.fc.hp.com> <528413DE.1090203@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <528413DE.1090203@zytor.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 13, 2013 at 04:05:50PM -0800, H. Peter Anvin wrote: > On 11/13/2013 03:57 PM, jerry.hoemann@hp.com wrote: > > > > I think i can go to a date based black list, that removes the manual > > step. System running firmware before certain date assumes we need > > to do the work around. If firmware is newer than that date, we don't > > use the workaround. Blacklist overrides and allows current behavior > > for new firmware that is subsequently found to be broken and for > > which we can't convenience the manufacturer to fix. > > > > No, we can't, at least not for now. We are continually finding new > platforms with the bug. Does you have a list of systems that require efi_reserve_boot_services? might be useful from a testing standpoint to get access to one. > > > > > I will still point out that as currently used, efi_reserve_boot_services > > is wrong. A work around for firmware bugs on one platform shouldn't be > > breaking platforms that don't have that bug. Its just much less likely > > to cause problems with higher crash kernel allocation. > > > > It is wrong, yes, but it seems like a ubiquitous problem. > > -hpa -- ---------------------------------------------------------------------------- Jerry Hoemann Software Engineer Hewlett-Packard/MODL 3404 E Harmony Rd. MS 57 phone: (970) 898-1022 Ft. Collins, CO 80528 FAX: (970) 898-XXXX email: jerry.hoemann@hp.com ----------------------------------------------------------------------------