Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "H. Peter Anvin" <hpa@xxxxxxxxx>
Subject: Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
Date: Sun, 27 Sep 2015 09:30:48 -0700
Cc: Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Leif Lindholm <leif.lindholm@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, stable <stable@xxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Matthew Garrett <mjg59@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Brian Gerst <brgerst@xxxxxxxxx>, Dave Young <dyoung@xxxxxxxxxx>, "linux-efi@xxxxxxxxxxxxxxx" <linux-efi@xxxxxxxxxxxxxxx>, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Peter Jones <pjones@xxxxxxxxxx>, Matt Fleming <matt@xxxxxxxxxxxxxxxxxxx>, Matt Fleming <matt.fleming@xxxxxxxxx>, Borislav Petkov <bp@xxxxxxx>, "Lee, Chun-Yi" <jlee@xxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, James Bottomley <JBottomley@xxxxxxxx>
In-reply-to: <F1F37F57-7D03-4FC2-955E-7E8C82540A24@zytor.com>

On Sep 26, 2015 1:19 PM, "H. Peter Anvin" <hpa@xxxxxxxxx> wrote:
>
> Sadly a lot of firmware is known to fail in that configuration :(  That was very much our guest choice.
>

Why can't we map everything completely 1:1 (VA = PA) and call the
setVA thing but pass it literally the identity.

Firmwares that need it to be called will work, and firmwares that fail
to update all offsets will be fine because there's nothing to update.

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Matthew Garrett

References:
- [GIT PULL 0/2] EFI urgent fixes
  - From: Matt Fleming
- [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Matt Fleming
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Ingo Molnar
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Andy Lutomirski
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: H. Peter Anvin
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Ard Biesheuvel
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: H. Peter Anvin
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Matt Fleming
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Ard Biesheuvel
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: H. Peter Anvin

Prev by Date: Re: [PATCH 2/2] arm64/efi: Don't pad between EFI_MEMORY_RUNTIME regions
Next by Date: Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
Previous by thread: Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
Next by thread: Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]