From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk
Cc: marc.zyngier@arm.com, bhsharma@redhat.com,
linux-efi@vger.kernel.org, will.deacon@arm.com,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH v2 0/6] arm/efi: fix memblock reallocation crash due to persistent reservations
Date: Wed, 7 Nov 2018 15:16:05 +0100 [thread overview]
Message-ID: <20181107141611.12076-1-ard.biesheuvel@linaro.org> (raw)
This series addresses the kexec/kdump crash on arm64 system with many CPUs
that was reported by Bhupesh.
Patch #1 fixes the actual crash, but may result in memblock_reserve() to
fail. This is fixed in patch #4, where the point that the persistent
reservations are applied is moved to after memblock_allow_resize() has
been called.
Patches #2 and #3 contain some minor preparatory changes that are
required on ARM to ensure that efi_apply_persistent_mem_reservations()
can be called at some point (i.e., when memblock resizing is already
permitted and early memremap() is still usable)
Patches #5 and #6 optimize the EFI persistent memreserve infrastructure
so that fewer memblock reservations are required.
Changes since v1:
- Russell pointed out that switching to ordinary memremap() was not
possible this early, and so I refactored the ARM early boot code
slightly so that we can keep using early_memremap().
Ard Biesheuvel (6):
arm64: memblock: don't permit memblock resizing until linear mapping
is up
ARM: mm: permit memblock resizing right after mapping the linear
region
ARM: mm: permit early_memremap() to be used in paging_init()
efi/arm: defer persistent reservations until after paging_init()
efi: permit multiple entries in persistent memreserve data structure
efi: reduce the amount of memblock reservations for persistent
allocations
arch/arm/kernel/setup.c | 2 -
arch/arm/mm/init.c | 1 -
arch/arm/mm/mmu.c | 5 ++
arch/arm64/kernel/setup.c | 1 +
arch/arm64/mm/init.c | 2 -
arch/arm64/mm/mmu.c | 2 +
drivers/firmware/efi/efi.c | 59 ++++++++++++++------
drivers/firmware/efi/libstub/arm-stub.c | 2 +-
include/linux/efi.h | 23 +++++++-
9 files changed, 72 insertions(+), 25 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-07 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:16 Ard Biesheuvel [this message]
2018-11-07 14:16 ` [PATCH v2 1/6] arm64: memblock: don't permit memblock resizing until linear mapping is up Ard Biesheuvel
2018-11-08 17:53 ` Catalin Marinas
2018-11-07 14:16 ` [PATCH v2 2/6] ARM: mm: permit memblock resizing right after mapping the linear region Ard Biesheuvel
2018-11-07 14:16 ` [PATCH v2 3/6] ARM: mm: permit early_memremap() to be used in paging_init() Ard Biesheuvel
2018-11-07 14:16 ` [PATCH v2 4/6] efi/arm: defer persistent reservations until after paging_init() Ard Biesheuvel
2018-11-07 14:16 ` [PATCH v2 5/6] efi: permit multiple entries in persistent memreserve data structure Ard Biesheuvel
2018-11-07 14:16 ` [PATCH v2 6/6] efi: reduce the amount of memblock reservations for persistent allocations Ard Biesheuvel
2018-11-08 19:13 ` [PATCH v2 0/6] arm/efi: fix memblock reallocation crash due to persistent reservations Bhupesh Sharma
2018-11-08 19:14 ` Bhupesh Sharma
2018-11-08 19:14 ` Ard Biesheuvel
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=20181107141611.12076-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).