From: Borislav Petkov <bp@alien8.de>
To: Matt Fleming <matt@console-pimps.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Linux EFI <linux-efi@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, X86-ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH 0/4] EFI 1:1 mapping
Date: Tue, 4 Jun 2013 10:15:44 +0200 [thread overview]
Message-ID: <20130604081544.GA23640@pd.tnic> (raw)
In-Reply-To: <20130603145412.GJ2004@console-pimps.org>
On Mon, Jun 03, 2013 at 03:54:12PM +0100, Matt Fleming wrote:
> On Mon, 03 Jun, at 03:32:52PM, Matthew Garrett wrote:
> > We can only pass one set of addresses to SetVirtualAddressMap(), but it
> > doesn't seem like there's any intrinsic reason we can't the runtime
> > regions mapped to multiple virtual addresses.
>
> Indeed. That's the approach I took with my 1:1 series from last year. If
> Windows is mapping things at higher addresses like you said, then
> they're probably doing the same.
Right, the way I've done it now is to do the virtual mapping
unconditionally, then do the 1:1 mapping and call SetVirtualAddressMap
(f*cking camelcase is so nasty to type - that's why they need whole IDEs
to program :-)) with that map, if "efi=1:1_map" has been passed on the
cmd line.
After the call, we use *only* the 1:1 map but the virtual mapping is
still there.
The initial approach to addressing the b0rked Macs would then be to
never use the 1:1 map on them.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-06-04 8:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 12:56 [PATCH 0/4] EFI 1:1 mapping Borislav Petkov
2013-06-02 12:56 ` [PATCH 1/4] efi: Convert runtime services function ptrs Borislav Petkov
2013-06-06 10:07 ` Matt Fleming
2013-06-11 6:49 ` Matt Fleming
2013-06-11 9:33 ` Borislav Petkov
2013-06-02 12:56 ` [PATCH 2/4] x86, cpa: Map in an arbitrary pgd Borislav Petkov
2013-06-06 10:22 ` Matt Fleming
2013-06-06 13:24 ` Borislav Petkov
2013-06-06 13:30 ` Matt Fleming
2013-06-06 13:33 ` Borislav Petkov
2013-06-02 12:56 ` [PATCH 3/4] x86, efi: Add an efi= kernel command line parameter Borislav Petkov
2013-06-04 12:18 ` Borislav Petkov
2013-06-06 10:42 ` Matt Fleming
2013-06-06 13:26 ` Borislav Petkov
2013-06-06 13:36 ` Matt Fleming
2013-06-06 17:50 ` Matthew Garrett
2013-06-06 18:51 ` Borislav Petkov
2013-06-06 19:35 ` Matthew Garrett
2013-06-06 19:41 ` Borislav Petkov
2013-06-06 19:54 ` Matthew Garrett
2013-06-06 20:07 ` Borislav Petkov
2013-06-06 20:18 ` Matthew Garrett
2013-06-06 20:27 ` Borislav Petkov
2013-06-06 20:30 ` Matthew Garrett
2013-06-06 20:44 ` Borislav Petkov
2013-06-06 20:50 ` Matthew Garrett
2013-06-06 21:02 ` Borislav Petkov
2013-06-06 21:03 ` Matthew Garrett
2013-06-02 12:56 ` [PATCH 4/4] x86, efi: Map runtime services 1:1 Borislav Petkov
2013-06-06 13:14 ` Matt Fleming
2013-06-06 13:29 ` Borislav Petkov
2013-06-06 15:58 ` Borislav Petkov
2013-06-06 19:28 ` H. Peter Anvin
2013-06-06 19:36 ` Borislav Petkov
2013-06-06 19:38 ` H. Peter Anvin
2013-06-10 12:55 ` Borislav Petkov
2013-06-02 22:56 ` [PATCH 0/4] EFI 1:1 mapping Matthew Garrett
2013-06-03 8:11 ` Borislav Petkov
2013-06-03 14:27 ` James Bottomley
2013-06-03 14:30 ` Matthew Garrett
2013-06-03 14:38 ` James Bottomley
2013-06-03 15:21 ` Matthew Garrett
2013-06-03 16:18 ` James Bottomley
2013-06-03 16:24 ` Matthew Garrett
2013-06-03 16:35 ` James Bottomley
2013-06-03 16:42 ` Matthew Garrett
2013-06-03 18:05 ` James Bottomley
2013-06-03 18:11 ` Matthew Garrett
2013-06-03 21:19 ` James Bottomley
2013-06-03 21:29 ` Matthew Garrett
2014-02-10 3:59 ` Linux, UEFI, and Chromebooks (was RE: [PATCH 0/4] EFI 1:1 mapping) Yuhong Bao
2013-06-03 14:32 ` [PATCH 0/4] EFI 1:1 mapping Matthew Garrett
2013-06-03 14:54 ` Matt Fleming
2013-06-04 8:15 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130604081544.GA23640@pd.tnic \
--to=bp@alien8.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bp@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox