[RFT PATCH v2] efi: map memreserve table before first use

Mapping the MEMRESERVE EFI configuration table from an early initcall is too late: the GICv3 ITS code that creates persistent reservations for the boot CPU's LPI tables is invoked from init_IRQ(), which runs much earlier than the handling of the initcalls. So instead, move the initialization

Re: [RFT PATCH] efi: map memreserve table before first use

On 20/11/2018 18:35, Ard Biesheuvel wrote: > On Tue, 20 Nov 2018 at 19:29, Marc Zyngier wrote: >> >> Hi Ard, >> >> On 20/11/2018 17:35, Ard Biesheuvel wrote: >>> Mapping the MEMRESERVE EFI configuration table from an early initcall >>> is too late: the GICv3 ITS code that creates persistent

Re: [RFT PATCH] efi: map memreserve table before first use

On Tue, 20 Nov 2018 at 19:29, Marc Zyngier wrote: > > Hi Ard, > > On 20/11/2018 17:35, Ard Biesheuvel wrote: > > Mapping the MEMRESERVE EFI configuration table from an early initcall > > is too late: the GICv3 ITS code that creates persistent reservations > > for the boot CPU's LPI tables is

Re: [RFT PATCH] efi: map memreserve table before first use

Hi Ard, On 20/11/2018 17:35, Ard Biesheuvel wrote: > Mapping the MEMRESERVE EFI configuration table from an early initcall > is too late: the GICv3 ITS code that creates persistent reservations > for the boot CPU's LPI tables is invoked from init_IRQ(), which runs > much earlier than the handling

[RFT PATCH] efi: map memreserve table before first use

Mapping the MEMRESERVE EFI configuration table from an early initcall is too late: the GICv3 ITS code that creates persistent reservations for the boot CPU's LPI tables is invoked from init_IRQ(), which runs much earlier than the handling of the initcalls. So instead, move the initialization