Re: [tip:efi/core] x86/efi: Unmap EFI boot services code/data regions from efi_pgd
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:efi/core] x86/efi: Unmap EFI boot services code/data regions from efi_pgd
- From: Matt Fleming <matt@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 7 Jan 2019 15:57:52 +0000
- Cc: Borislav Petkov <bp@xxxxxxxxx>, "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, "marc.zyngier@xxxxxxx" <marc.zyngier@xxxxxxx>, "eric.snowberg@xxxxxxxxxx" <eric.snowberg@xxxxxxxxxx>, "hdegoede@xxxxxxxxxx" <hdegoede@xxxxxxxxxx>, "Hansen, Dave" <dave.hansen@xxxxxxxxx>, "peterz@xxxxxxxxxxxxx" <peterz@xxxxxxxxxxxxx>, "hpa@xxxxxxxxx" <hpa@xxxxxxxxx>, "arend.vanspriel@xxxxxxxxxxxx" <arend.vanspriel@xxxxxxxxxxxx>, "julien.thierry@xxxxxxx" <julien.thierry@xxxxxxx>, "bhsharma@xxxxxxxxxx" <bhsharma@xxxxxxxxxx>, "jonathanh@xxxxxxxxxx" <jonathanh@xxxxxxxxxx>, "joe@xxxxxxxxxxx" <joe@xxxxxxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "natechancellor@xxxxxxxxx" <natechancellor@xxxxxxxxx>, "luto@xxxxxxxxxx" <luto@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "sedat.dilek@xxxxxxxxx" <sedat.dilek@xxxxxxxxx>, "zhuyifei1999@xxxxxxxxx" <zhuyifei1999@xxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>
- In-reply-to: <CAKv+Gu-v+nBh2yK0uXbuwwnpEnpG8bk4ufSMXygMOdOd2XSTYw@mail.gmail.com>
- References: <FFF73D592F13FD46B8700F0A279B802F48604575@ORSMSX114.amr.corp.intel.com> <CAKv+Gu_vTHFxpKRu_CxKP-GdNdgdFKr7fi87VkNur0sqGQNVDw@mail.gmail.com> <FFF73D592F13FD46B8700F0A279B802F486045CA@ORSMSX114.amr.corp.intel.com> <CAKv+Gu9iJinkP-buhmzRyB91_HcJ-tDwT3YHeHGFo4Bsiv7O_Q@mail.gmail.com> <FFF73D592F13FD46B8700F0A279B802F486046A9@ORSMSX114.amr.corp.intel.com> <CAKv+Gu99VdPero0yrXiaByURyp1idYE948Qi4j1eqY0ENCrF5A@mail.gmail.com> <20181221171308.GJ1325@zn.tnic> <CAKv+Gu91YsuK2QmWStPe84v8L7XD9x4cduTYgUjj3TPRfQckfw@mail.gmail.com> <20181221192928.GM1325@zn.tnic> <CAKv+Gu-v+nBh2yK0uXbuwwnpEnpG8bk4ufSMXygMOdOd2XSTYw@mail.gmail.com>
- User-agent: Mutt/1.5.24 (2015-08-30)
On Sat, 22 Dec, at 12:07:48PM, Ard Biesheuvel wrote:
> On Fri, 21 Dec 2018 at 20:29, Borislav Petkov <bp@xxxxxxxxx> wrote:
> >
> > On Fri, Dec 21, 2018 at 06:26:23PM +0100, Ard Biesheuvel wrote:
> > > On Fri, 21 Dec 2018 at 18:13, Borislav Petkov <bp@xxxxxxxxx> wrote:
> > > >
> > > > On Fri, Dec 21, 2018 at 06:02:29PM +0100, Ard Biesheuvel wrote:
> > > > > As far as I can tell, the SGI x86 UV platforms still rely on this, so
> > > > > we're stuck with it for the foreseeable future.
> > > >
> > > > What happened with the old apple laptops which couldn't handle high
> > > > virtual mappings and needed 1:1? We don't care anymore?
> > > >
> > >
> > > If that is the case (I wouldn't know) then yes, there is a second
> > > reason why we need to keep this code.
> >
> > Fleming knows details and he's on CC, lemme "pull" him up into To: :-)
> >
>
> IIUC the 1:1 mapping and the 'old' mapping are two different things,
> and the new mapping also contains a 1:1 mapping of the boot services
> regions, at least until SetVirtualAddressMap() returns.
Yep, they're different. And yes the 1:1 mapping should stick around
with the new scheme IIRC (it's been a while).
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]