From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: James Bottomley
<James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Jordan L Justen
<jordan.l.justen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Curious crash with secure variables
Date: Mon, 18 Mar 2013 15:16:34 +0000 [thread overview]
Message-ID: <51472FD2.6020205@console-pimps.org> (raw)
In-Reply-To: <1363619058.11342.74.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
On 03/18/2013 03:04 PM, David Woodhouse wrote:
> On Mon, 2013-03-18 at 15:02 +0000, Matt Fleming wrote:
>> On 03/18/2013 02:23 PM, James Bottomley wrote:
>>> Yes, it's a phenomenally complicated operation from looking at the
>>> TianoCore source ... might we not be better off not bothering to
>>> relocate and just using a private physical mapping for the calls?
>>
>> Yeah, there have been various discussions about doing this. I sent some
>> patches last year but they broke various non-EFI machines and I haven't
>> had chance to pick it up again.
>
> Got a pointer? I may take a look...
>
See,
commit 53b87cf0 ("x86, mm: Include the entire kernel memory map in trampoline_pgd"),
commit 185034e7 ("x86, efi: 1:1 pagetable mapping for virtual EFI calls"),
commit da5a108d05b4 ("x86/kernel: remove tboot 1:1 page table creation code") and
commit bd52276fa1d4 ("x86-64/efi: Use EFI to deal with platform wall clock (again)")
and the two revert commits from Linus, be354f40 and 11520e5e.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-03-18 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 8:01 Curious crash with secure variables James Bottomley
[not found] ` <1363593684.2412.5.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-18 11:49 ` Matt Fleming
[not found] ` <1363607345.15011.339.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-03-18 14:23 ` James Bottomley
[not found] ` <1363616613.2412.19.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2013-03-18 14:32 ` David Woodhouse
2013-03-18 15:02 ` Matt Fleming
[not found] ` <51472C81.5020801-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-03-18 15:04 ` David Woodhouse
[not found] ` <1363619058.11342.74.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
2013-03-18 15:16 ` Matt Fleming [this message]
[not found] ` <51472FD2.6020205-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-03-18 15:32 ` David Woodhouse
[not found] ` <1363620768.11342.76.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
2013-03-18 18:04 ` Matt Fleming
[not found] ` <51475735.40201-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
2013-03-18 18:22 ` H. Peter Anvin
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=51472FD2.6020205@console-pimps.org \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=jordan.l.justen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).