Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936309Ab3DRQid (ORCPT ); Thu, 18 Apr 2013 12:38:33 -0400 Received: from terminus.zytor.com ([198.137.202.10]:39901 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933132Ab3DRQib (ORCPT ); Thu, 18 Apr 2013 12:38:31 -0400 Message-ID: <5170216C.9020300@zytor.com> Date: Thu, 18 Apr 2013 09:38:04 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: Josh Triplett CC: Matt Fleming , "Bryan O'Donoghue" , matthew.garrett@nebula.com, linux-efi@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Darren Hart , Ingo Molnar , Thomas Gleixner , Josh Boyer Subject: Re: [PATCH] Remove warning in efi_enter_virtual_mode References: <1366127886-31460-1-git-send-email-bryan.odonoghue.lkml@nexus-software.ie> <516EAC4A.6040202@console-pimps.org> <516F1B90.9040508@nexus-software.ie> <516FD24A.3070502@console-pimps.org> <20130418163325.GA6884@leaf> In-Reply-To: <20130418163325.GA6884@leaf> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1481 Lines: 36 On 04/18/2013 09:33 AM, Josh Triplett wrote: > On Thu, Apr 18, 2013 at 12:00:26PM +0100, Matt Fleming wrote: >>> No, no - we *don't* have a BGRT object at all. >>> >>> We have a completely clean memory map - but the BGRT code is causing the >>> is_ram() failure. >> >> You assume that mapping of the Boot Services regions is done purely for >> the benefit of pulling out the bgrt image - it's not, see the above >> commit log - and I assumed that you had an ACPI bgrt pointer in your >> memory map, but you don't. >> >> Darren, Josh, have you ever seen an i386 machine with a bgrt pointer? If >> not, and given that we've never seen an i386 firmware that requires the >> above workaround from Matthew, combined with the fact that there are so >> few i386 implementations out there, I'm inclined to apply the patch >> below, because anything else is a lot more work. We can address this >> properly if we ever start seeing i386 machines with bgrt pointers that >> reference highmem. > > The machine I developed the BGRT changes on kept the image below the 4G > mark, inside one of the memory regions reclaimable via > ExitBootServices(). > Well, highmem is >= ~896M. Do you have a machine with BGRT over the highmem mark? -hpa -- 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/