[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130603212930.GA28955@srcf.ucam.org>
Date: Mon, 3 Jun 2013 22:29:30 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Borislav Petkov <bp@...en8.de>,
Linux EFI <linux-efi@...r.kernel.org>,
Matt Fleming <matt@...sole-pimps.org>,
Jiri Kosina <jkosina@...e.cz>, X86-ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH 0/4] EFI 1:1 mapping
On Mon, Jun 03, 2013 at 02:19:05PM -0700, James Bottomley wrote:
> On Mon, 2013-06-03 at 19:11 +0100, Matthew Garrett wrote:
> > No. I'm saying that calling it with the 1:1 map is something very
> > different to the behaviour of Windows, and I'm saying that doing so is
> > known to cause variable writes on some Apple hardware to stop working.
> > If we're aiming for maximum compatibility, we need to call
> > SetVirtualAddressMap() with addresses above the canonicalisation hole.
>
> OK, so tell me this problem: it's a new one one me. I think you're
> saying if we don't call SetVirtualAddressMap with a mapping above a
> certain value, some Apple system breaks somehow? (how?).
SetVariable() returns an error. Digging through disassembly of the code
generating the error got me to the point of realising it was doing some
sort of pointer arithmetic and then giving up.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists