From: "Jan Beulich" <JBeulich@suse.com>
To: "Matt Fleming" <matt@console-pimps.org>
Cc: "Matt Fleming" <matt.fleming@intel.com>,
"Ingo Molnar" <mingo@kernel.org>, <x86@kernel.org>,
"Matthew Garrett" <mjg@redhat.com>, <linux-efi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v2 0/3] x86/efi: Identity mapping pagetable
Date: Fri, 05 Oct 2012 14:54:51 +0100 [thread overview]
Message-ID: <506F02CB02000078000A0050@nat28.tlf.novell.com> (raw)
In-Reply-To: <1349442872-5266-1-git-send-email-matt@console-pimps.org>
>>> On 05.10.12 at 15:14, Matt Fleming <matt@console-pimps.org> wrote:
> 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.
>
> v2: Based on feedback from Jan Beulich delete the 32-bit changes in
> [PATCH 1/3], they were likely to create more problems than they would
> solve and the identity I/O mappings are unused on 32-bit anyway.
>
> Matt Fleming (2):
> x86, mm: Include the entire kernel memory map in trampoline_pgd
> x86, efi: 1:1 pagetable mapping for virtual EFI calls
Acked-by: Jan Beulich <jbeulich@suse.com>
(I know too little about the tboot code to meaningfully ack that
one too.)
> 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 | 105 +++++++++++++++++++++++++++++++++++++++++
> arch/x86/platform/efi/efi_64.c | 15 ++++++
> arch/x86/realmode/init.c | 17 ++++++-
> 6 files changed, 169 insertions(+), 83 deletions(-)
>
> --
> 1.7.11.4
prev parent reply other threads:[~2012-10-05 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 13:14 Matt Fleming
2012-10-05 13:14 ` [PATCH v2 1/3] x86, mm: Include the entire kernel memory map in trampoline_pgd Matt Fleming
2012-10-05 13:14 ` [PATCH 2/3] x86, efi: 1:1 pagetable mapping for virtual EFI calls Matt Fleming
2012-10-05 13:14 ` [PATCH 3/3] x86/kernel: remove tboot 1:1 page table creation code Matt Fleming
2012-10-05 13:54 ` Jan Beulich [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=506F02CB02000078000A0050@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--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
all inboxes | Powered by JetHome®