From: John Garry <john.garry@huawei.com>
To: Jan Glauber <Jan.Glauber@cavium.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "marc.zyngier@arm.com" <marc.zyngier@arm.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFT PATCH] efi: map memreserve table before first use
Date: Wed, 21 Nov 2018 13:33:34 +0000 [thread overview]
Message-ID: <d754166a-7c5e-9673-1052-9d433f5593eb@huawei.com> (raw)
In-Reply-To: <20181121095648.GA11514@hc>
On 21/11/2018 09:56, Jan Glauber wrote:
> On Tue, Nov 20, 2018 at 06:35:42PM +0100, 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 of the initcalls.
>>
>> So instead, move the initialization performed by the initcall into
>> efi_mem_reserve_persistent() itself.
>>
>> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> ---
>> drivers/firmware/efi/efi.c | 26 ++++++++++----------------
>> 1 file changed, 10 insertions(+), 16 deletions(-)
>>
>> diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c
>> index fad7c62cfc0e..40de2f6734cc 100644
>> --- a/drivers/firmware/efi/efi.c
>> +++ b/drivers/firmware/efi/efi.c
>> @@ -967,15 +967,23 @@ bool efi_is_table_address(unsigned long phys_addr)
>> }
>>
>> static DEFINE_SPINLOCK(efi_mem_reserve_persistent_lock);
>> -static struct linux_efi_memreserve *efi_memreserve_root __ro_after_init;
>> +static struct linux_efi_memreserve *efi_memreserve_root;
>>
>> int efi_mem_reserve_persistent(phys_addr_t addr, u64 size)
>> {
>> struct linux_efi_memreserve *rsv;
>>
>> - if (!efi_memreserve_root)
>> + if (efi.mem_reserve == EFI_INVALID_TABLE_ADDR)
>> return -ENODEV;
>>
>> + if (!efi_memreserve_root) {
>> + efi_memreserve_root = memremap(efi.mem_reserve,
>> + sizeof(*efi_memreserve_root),
>> + MEMREMAP_WB);
>> + if (WARN_ON_ONCE(!efi_memreserve_root))
>> + return -ENOMEM;
>> + }
>> +
>> rsv = kmalloc(sizeof(*rsv), GFP_ATOMIC);
>> if (!rsv)
>> return -ENOMEM;
>> @@ -991,20 +999,6 @@ int efi_mem_reserve_persistent(phys_addr_t addr, u64 size)
>> return 0;
>> }
>>
>> -static int __init efi_memreserve_root_init(void)
>> -{
>> - if (efi.mem_reserve == EFI_INVALID_TABLE_ADDR)
>> - return -ENODEV;
>> -
>> - efi_memreserve_root = memremap(efi.mem_reserve,
>> - sizeof(*efi_memreserve_root),
>> - MEMREMAP_WB);
>> - if (!efi_memreserve_root)
>> - return -ENOMEM;
>> - return 0;
>> -}
>> -early_initcall(efi_memreserve_root_init);
>> -
>> #ifdef CONFIG_KEXEC
>> static int update_efi_random_seed(struct notifier_block *nb,
>> unsigned long code, void *unused)
>> --
>> 2.17.1
>
> Hi Ard,
>
> thanks for the patch, it works fine for me.
>
> If you want:
> Tested-by: Jan Glauber <jglauber@cavium.com>
FWIW, the splat is gone:
Tested-by: John Garry <john.garry@huawei.com>
>
> --Jan
>
>
prev parent reply other threads:[~2018-11-21 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 17:35 [RFT PATCH] efi: map memreserve table before first use Ard Biesheuvel
2018-11-20 18:29 ` Marc Zyngier
2018-11-20 18:35 ` Ard Biesheuvel
2018-11-20 18:44 ` Marc Zyngier
2018-11-21 9:56 ` Jan Glauber
2018-11-21 13:33 ` John Garry [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=d754166a-7c5e-9673-1052-9d433f5593eb@huawei.com \
--to=john.garry@huawei.com \
--cc=Jan.Glauber@cavium.com \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=marc.zyngier@arm.com \
/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