From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: catalin.marinas@arm.com, will.deacon@arm.com, robh+dt@kernel.org,
frowand.list@gmail.com
Cc: james.morse@arm.com, kexec@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
AKASHI Takahiro <takahiro.akashi@linaro.org>
Subject: [PATCH 0/3] arm64: kexec_file: add kdump
Date: Thu, 12 Sep 2019 15:01:47 +0900 [thread overview]
Message-ID: <20190912060150.10818-1-takahiro.akashi@linaro.org> (raw)
This is the last piece of my kexec_file_load implementation for arm64.
It is now ready for being merged as some relevant patch to dtc/libfdt[1]
has finally been integrated in v5.3-rc1.
(Nothing changed since kexec_file v16[2] except adding Patch#1 and #2.)
Patch#1 and #2 are preliminary patches for libfdt component.
Patch#3 is to add kdump support.
[1] commit 9bb9c6a110ea ("scripts/dtc: Update to upstream version
v1.5.0-23-g87963ee20693"), in particular
7fcf8208b8a9 libfdt: add fdt_append_addrrange()
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2018-November/612641.html
AKASHI Takahiro (3):
libfdt: define UINT32_MAX in libfdt_env.h
libfdt: include fdt_addresses.c
arm64: kexec_file: add crash dump support
arch/arm64/include/asm/kexec.h | 4 +
arch/arm64/kernel/kexec_image.c | 4 -
arch/arm64/kernel/machine_kexec_file.c | 105 ++++++++++++++++++++++++-
include/linux/libfdt_env.h | 3 +
lib/Makefile | 2 +-
lib/fdt_addresses.c | 2 +
6 files changed, 112 insertions(+), 8 deletions(-)
create mode 100644 lib/fdt_addresses.c
--
2.21.0
next reply other threads:[~2019-09-12 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 6:01 AKASHI Takahiro [this message]
2019-09-12 6:01 ` [PATCH 1/3] libfdt: define UINT32_MAX in libfdt_env.h AKASHI Takahiro
2019-09-12 6:01 ` [PATCH 2/3] libfdt: include fdt_addresses.c AKASHI Takahiro
2019-09-12 6:01 ` [PATCH 3/3] arm64: kexec_file: add crash dump support AKASHI Takahiro
2019-10-07 3:04 ` [PATCH 0/3] arm64: kexec_file: add kdump AKASHI Takahiro
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=20190912060150.10818-1-takahiro.akashi@linaro.org \
--to=takahiro.akashi@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=frowand.list@gmail.com \
--cc=james.morse@arm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--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).