From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: kexec mailing list <kexec@lists.infradead.org>,
Simon Horman <horms@verge.net.au>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
Bhupesh Sharma <bhsharma@redhat.com>,
Masayoshi Mizuma <msys.mizuma@gmail.com>,
James Morse <james.morse@arm.com>
Subject: [PATCH v3 0/3] arm64: handle "reserved" entries in /proc/iomem
Date: Wed, 18 Dec 2019 11:42:29 -0500 [thread overview]
Message-ID: <20191218164232.6086-1-msys.mizuma@gmail.com> (raw)
In recent arm64 kernels, /proc/iomem has an extended file format like:
40000000-5871ffff : System RAM
41800000-426affff : Kernel code
426b0000-42aaffff : reserved
42ab0000-42c64fff : Kernel data
54400000-583fffff : Crash kernel
58590000-585effff : reserved
58700000-5871ffff : reserved
58720000-58b5ffff : reserved
58b60000-5be3ffff : System RAM
58b61000-58b61fff : reserved
where "reserved" entries can be an ACPI table, UEFI related code or
data. They can be corrupted and result in early failure in booting
a new kernel. As an actual example, LPI pending table and LPI property
table, which are pointed by a UEFI data, are sometimes destroyed.
They are expected to be preserved across kexec'ing.
Changelog:
v3: - Re-based to the latest commit (bd07796).
- Added Tested-by tag from Bhupesh and Masayoshi
- Added an error handling in case
mem_regions_alloc_and_exclude() fails (0002 patch).
AKASHI Takahiro (3):
kexec: add variant helper functions for handling memory regions
arm64: kexec: allocate memory space avoiding reserved regions
arm64: kdump: deal with a lot of resource entries in /proc/iomem
kexec/arch/arm64/crashdump-arm64.c | 25 ++---
kexec/arch/arm64/kexec-arm64.c | 153 ++++++++++++++++++-----------
kexec/mem_regions.c | 42 ++++++++
kexec/mem_regions.h | 7 ++
4 files changed, 153 insertions(+), 74 deletions(-)
--
2.18.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2019-12-18 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 16:42 Masayoshi Mizuma [this message]
2019-12-18 16:42 ` [PATCH v3 1/3] kexec: add variant helper functions for handling memory regions Masayoshi Mizuma
2019-12-18 16:42 ` [PATCH v3 2/3] arm64: kexec: allocate memory space avoiding reserved regions Masayoshi Mizuma
2019-12-18 16:42 ` [PATCH v3 3/3] arm64: kdump: deal with a lot of resource entries in /proc/iomem Masayoshi Mizuma
2019-12-23 6:55 ` [PATCH v3 0/3] arm64: handle "reserved" " Bhupesh Sharma
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=20191218164232.6086-1-msys.mizuma@gmail.com \
--to=msys.mizuma@gmail.com \
--cc=bhsharma@redhat.com \
--cc=horms@verge.net.au \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=takahiro.akashi@linaro.org \
/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