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]

Subject: Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
From: Matthew Garrett <mjg59@xxxxxxxxxxxxx>
Date: Sun, 27 Sep 2015 19:06:33 +0100
Cc: "H. Peter Anvin" <hpa@xxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Leif Lindholm <leif.lindholm@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, stable <stable@xxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, 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: <CALCETrUA6k-oHzuWA54VzEA1v63b5--JPCCuBoOxLisOtjUn+g@mail.gmail.com>
References: <1443218539-7610-2-git-send-email-matt@codeblueprint.co.uk> <20150926055643.GA25877@gmail.com> <CALCETrUeGAedCKcSCvedyooamr6-tyfb3-b3uYDZG+k3Q_v9rw@mail.gmail.com> <E40EBF14-FD9E-49C0-A7FB-951958F72F79@zytor.com> <CAKv+Gu8i4KuXYQZA5noTomj6-chZcuuDEQubOJznyP1DR=+VTw@mail.gmail.com> <0568D1D7-B6AA-437C-ADCE-A86D7A2E4722@zytor.com> <20150926195755.GC3144@codeblueprint.co.uk> <BFDFFBC6-C6CA-4035-8E29-C7220533A787@linaro.org> <F1F37F57-7D03-4FC2-955E-7E8C82540A24@zytor.com> <CALCETrUA6k-oHzuWA54VzEA1v63b5--JPCCuBoOxLisOtjUn+g@mail.gmail.com>
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Sep 27, 2015 at 09:30:48AM -0700, Andy Lutomirski wrote:
> 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.

Last time I tried this I found that some firmware makes assumptions 
about having high addresses.

-- 
Matthew Garrett | mjg59@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe stable" 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: Ingo Molnar

References:
- [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
- Re: [PATCH 1/2] x86/efi: Map EFI memmap entries in-order at runtime
  - From: Andy Lutomirski

Prev by Date: Re: [PATCH 4.2 000/134] 4.2.2-stable review
Next by Date: Re: [PATCH 4.2 000/134] 4.2.2-stable review
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 Kernel] [Kernel Development Newbies] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite Hiking] [Linux Kernel] [Linux SCSI]