Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936577Ab3DRTz0 (ORCPT ); Thu, 18 Apr 2013 15:55:26 -0400 Received: from arkanian.console-pimps.org ([212.110.184.194]:40222 "EHLO arkanian.console-pimps.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936351Ab3DRTzY (ORCPT ); Thu, 18 Apr 2013 15:55:24 -0400 Message-ID: <51704FA8.7060801@console-pimps.org> Date: Thu, 18 Apr 2013 20:55:20 +0100 From: Matt Fleming User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: Josh Triplett CC: "H. Peter Anvin" , "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> <5170216C.9020300@zytor.com> <20130418164457.GB6884@leaf> In-Reply-To: <20130418164457.GB6884@leaf> 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: 1257 Lines: 28 On 04/18/2013 05:44 PM, Josh Triplett wrote: >>> 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? > > I don't have the machine in question anymore, and I don't remember. Sorry, I should have been more clear - having a BGRT image in highmem has never worked for the reasons I outlined in my previous mail. What I was really asking was: is it OK that we now explicitly don't support that case? I'm working on the assumption that it's pointless writing support for the BGRT in highmem because no such i386 machines exist. If the BGRT code works for your i386 right now, the address isn't in highmem. If there are machines out there that would require us to write support, it's probably worth doing now instead of punting. But it sounds like there aren't any. -- Matt Fleming, Intel Open Source Technology Center -- 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/