From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [PATCH -v2 0/4] EFI 1:1 mapping Date: Wed, 19 Jun 2013 17:08:04 +0100 Message-ID: <20130619160804.GB27832@srcf.ucam.org> References: <1371491416-11037-1-git-send-email-bp@alien8.de> <20130619125243.GD11209@gmail.com> <20130619130225.GA28311@pd.tnic> <20130619130434.GB24957@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20130619130434.GB24957-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ingo Molnar Cc: Borislav Petkov , Linux EFI , Matt Fleming , X86 ML , LKML , Borislav Petkov List-Id: linux-efi@vger.kernel.org On Wed, Jun 19, 2013 at 03:04:34PM +0200, Ingo Molnar wrote: > * Borislav Petkov wrote: > > And yet there are the Macs which reportedly cannot stomach this. > > Do we know why? I got lost in a maze of pointer arithmetic. There seems to be an assumption that nvram writes should be forbidden if in runtime mode but with pointers still below the phys/virt split, which obviously makes no sense but hey. But, as always, the only reliable thing to do here is to behave as much like Windows as possible. Which means performing the 1:1 mapping but maintaining the high mapping, and passing the high values via SetVirtualAddressMap. -- Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org