Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754033AbbG3ID3 (ORCPT ); Thu, 30 Jul 2015 04:03:29 -0400 Received: from mail.skyhub.de ([78.46.96.112]:35313 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866AbbG3ID0 (ORCPT ); Thu, 30 Jul 2015 04:03:26 -0400 Date: Thu, 30 Jul 2015 10:03:23 +0200 From: Borislav Petkov To: "H. Peter Anvin" , Matt Fleming Cc: "Lee, Chun-Yi" , Thomas Gleixner , Ingo Molnar , x86@kernel.org, linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org, "Lee, Chun-Yi" Subject: Re: [PATCH] x86_64/efi: Mapping Boot and Runtime EFI memory regions to different starting virtual address Message-ID: <20150730080323.GD8984@nazgul.tnic> References: <1438230757-30840-1-git-send-email-jlee@suse.com> <55B9D806.7030705@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <55B9D806.7030705@zytor.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: 821 Lines: 23 On Thu, Jul 30, 2015 at 12:53:42AM -0700, H. Peter Anvin wrote: > This changelog is at least partially incomprehensive. It also seems > more than a bit aggressive to expect that 1 GB will be sufficient > forever. Right, before we do anything, I'd like for us to figure out first why this is a problem all of a sudden. And why should we even keep boot code/data, if it is fair game, once runtime services get enabled. Matt, can you please chime in first before we even talk about a solution... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- 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/