From: Matt Fleming <matt@console-pimps.org>
To: linux-kernel@vger.kernel.org
Cc: linux-efi@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Matthew Garrett <mjg@redhat.com>, Jan Beulich <jbeulich@suse.com>,
x86@kernel.org, Ingo Molnar <mingo@kernel.org>,
Matt Fleming <matt.fleming@intel.com>
Subject: [PATCH 0/3] x86/efi: Identity mapping pagetable
Date: Wed, 3 Oct 2012 13:59:14 +0100 [thread overview]
Message-ID: <1349269157-25956-1-git-send-email-matt@console-pimps.org> (raw)
From: Matt Fleming <matt.fleming@intel.com>
This series upgrades real_mode_header->trampoline_pgd to a proper
kernel pagetable instead of just mapping the kernel text and module
space. It also inserts the physical mappings for anything we
ioremap(), so I/O regions are always accessible via their physical
addresses whenever this pagetable is loaded, making it a true identity
mapping.
These changes make it suitable for loading when calling virtual EFI
runtime functions on x86-64. The main benefit of this change is to fix
the ASUS firmware bug documented here,
https://lkml.org/lkml/2012/8/7/108
but having our own EFI pagetable makes sense anyway. The memory map
code is easily the most complicatd part of the EFI infrastructure, and
it's likely that there will be other funky stuff we have to do with
our memory map as more and more machines ship with various
implementations of EFI firmware.
Note that we only switch to the identity pagetable for x86-64. I'm
unaware of any bugs like the above on 32-bit EFI platforms, but we can
easily adopt the 64-bit scheme if one is discovered.
Matt Fleming (2):
x86, mm: Include the entire kernel memory map in trampoline_pgd
x86, efi: 1:1 pagetable mapping for virtual EFI calls
Xiaoyan Zhang (1):
x86/kernel: remove tboot 1:1 page table creation code
arch/x86/include/asm/efi.h | 28 +++++++++---
arch/x86/kernel/tboot.c | 78 +++------------------------------
arch/x86/mm/init_64.c | 9 +++-
arch/x86/mm/ioremap.c | 99 ++++++++++++++++++++++++++++++++++++++++++
arch/x86/platform/efi/efi_64.c | 15 +++++++
arch/x86/realmode/init.c | 17 +++++++-
6 files changed, 163 insertions(+), 83 deletions(-)
--
1.7.11.4
next reply other threads:[~2012-10-03 12:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:59 Matt Fleming [this message]
2012-10-03 12:59 ` [PATCH 1/3] x86, mm: Include the entire kernel memory map in trampoline_pgd Matt Fleming
2012-10-03 13:31 ` Jan Beulich
2012-10-03 14:03 ` Matt Fleming
2012-10-04 6:32 ` Jan Beulich
2012-10-04 9:18 ` Matt Fleming
2012-10-04 10:01 ` Jan Beulich
2012-10-10 10:45 ` Matt Fleming
2012-10-15 7:22 ` Jan Beulich
2012-10-04 21:08 ` H. Peter Anvin
2012-10-05 6:39 ` Jan Beulich
2012-10-05 6:48 ` Matt Fleming
2012-10-05 8:19 ` Jan Beulich
2012-10-05 16:28 ` H. Peter Anvin
2012-10-07 8:16 ` Jan Beulich
2012-10-07 10:26 ` H. Peter Anvin
2012-10-08 6:43 ` Jan Beulich
2012-10-03 12:59 ` [PATCH 2/3] x86, efi: 1:1 pagetable mapping for virtual EFI calls Matt Fleming
2012-10-03 12:59 ` [PATCH 3/3] x86/kernel: remove tboot 1:1 page table creation code Matt Fleming
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=1349269157-25956-1-git-send-email-matt@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=mjg@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).