From: Nick Kossifidis <mick@ics.forth.gr>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: mick@ics.forth.gr, linux-riscv@lists.infradead.org,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] RISC-V: Add kexec/kdump support
Date: Fri, 23 Apr 2021 06:53:40 +0300 [thread overview]
Message-ID: <d3e45b902a28ec95c25cfa1f34d07d0d@mailhost.ics.forth.gr> (raw)
In-Reply-To: <mhng-c073ca02-d152-4ef5-86c5-4bcf58154afc@palmerdabbelt-glaptop>
Στις 2021-04-23 06:48, Palmer Dabbelt έγραψε:
> On Thu, 22 Apr 2021 20:36:56 PDT (-0700), mick@ics.forth.gr wrote:
>> Στις 2021-04-23 06:30, Palmer Dabbelt έγραψε:
>>> On Mon, 05 Apr 2021 01:57:07 PDT (-0700), mick@ics.forth.gr wrote:
>>>> This patch series adds kexec/kdump and crash kernel
>>>> support on RISC-V. For testing the patches a patched
>>>> version of kexec-tools is needed (still a work in
>>>> progress) which can be found at:
>>>>
>>>> https://riscv.ics.forth.gr/kexec-tools-patched.tar.xz
>>>>
>>>> v3:
>>>> * Rebase on newer kernel tree
>>>> * Minor cleanups
>>>> * Split UAPI changes to a separate patch
>>>> * Improve / cleanup init_resources
>>>> * Resolve Palmer's comments
>>>>
>>>> v2:
>>>> * Rebase on newer kernel tree
>>>> * Minor cleanups
>>>> * Properly populate the ioresources tre, so that it
>>>> can be used later on for implementing strict /dev/mem
>>>> * Use linux,usable-memory on /memory instead of a new binding
>>>> * USe a reserved-memory node for ELF core header
>>>>
>>>> Nick Kossifidis (5):
>>>> RISC-V: Add EM_RISCV to kexec UAPI header
>>>> RISC-V: Add kexec support
>>>> RISC-V: Improve init_resources
>>>> RISC-V: Add kdump support
>>>> RISC-V: Add crash kernel support
>>>>
>>>> arch/riscv/Kconfig | 25 ++++
>>>> arch/riscv/include/asm/elf.h | 6 +
>>>> arch/riscv/include/asm/kexec.h | 54 +++++++
>>>> arch/riscv/kernel/Makefile | 6 +
>>>> arch/riscv/kernel/crash_dump.c | 46 ++++++
>>>> arch/riscv/kernel/crash_save_regs.S | 56 +++++++
>>>> arch/riscv/kernel/kexec_relocate.S | 222
>>>> ++++++++++++++++++++++++++++
>>>> arch/riscv/kernel/machine_kexec.c | 193 ++++++++++++++++++++++++
>>>> arch/riscv/kernel/setup.c | 113 ++++++++------
>>>> arch/riscv/mm/init.c | 110 ++++++++++++++
>>>> include/uapi/linux/kexec.h | 1 +
>>>> 11 files changed, 787 insertions(+), 45 deletions(-)
>>>> create mode 100644 arch/riscv/include/asm/kexec.h
>>>> create mode 100644 arch/riscv/kernel/crash_dump.c
>>>> create mode 100644 arch/riscv/kernel/crash_save_regs.S
>>>> create mode 100644 arch/riscv/kernel/kexec_relocate.S
>>>> create mode 100644 arch/riscv/kernel/machine_kexec.c
>>>
>>> Thanks. There were some minor issues and some merge conflicts, I put
>>> this on for-next with some fixups.
>>
>> I've sent a v4 that shouldn't have merge conflicts, addressing some
>> comments from Alex as well, could you use that instead or is it too
>> late
>> ?
>
> Thanks, for some reason I didn't see it when poking around. There was
> still that one init_resources() merge conflict and I fixed up some of
> the commit texts, it's now on for-next as
>
> b94394119804 (HEAD -> for-next, riscv/for-next) RISC-V: Add crash
> kernel support
> 6e8451782c90 RISC-V: Add kdump support
> 0a0652429bdb RISC-V: Improve init_resources()
> d9a8897d6b5d RISC-V: Add kexec support
> f59938095b94 RISC-V: Add EM_RISCV to kexec UAPI header
Thanks a lot ! I'll keep on working on the user-space part and submit it
on kexec-tools later on.
prev parent reply other threads:[~2021-04-23 3:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 8:57 [PATCH v3 0/5] RISC-V: Add kexec/kdump support Nick Kossifidis
2021-04-05 8:57 ` [PATCH v3 1/5] RISC-V: Add EM_RISCV to kexec UAPI header Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 2/5] RISC-V: Add kexec support Nick Kossifidis
2021-04-06 18:38 ` Alex Ghiti
2021-04-09 10:19 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 3/5] RISC-V: Improve init_resources Nick Kossifidis
2021-04-06 7:19 ` Geert Uytterhoeven
2021-04-06 8:11 ` Nick Kossifidis
2021-04-06 8:22 ` Geert Uytterhoeven
2021-04-09 10:11 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 4/5] RISC-V: Add kdump support Nick Kossifidis
2021-04-06 18:36 ` Alex Ghiti
2021-04-09 10:21 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-05 8:57 ` [PATCH v3 5/5] RISC-V: Add crash kernel support Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-07 7:45 ` [PATCH v3 0/5] RISC-V: Add kexec/kdump support Yixun Lan
2021-04-07 16:29 ` Rob Herring
2021-04-09 10:02 ` Nick Kossifidis
2021-04-23 3:30 ` Palmer Dabbelt
2021-04-23 3:36 ` Nick Kossifidis
2021-04-23 3:48 ` Palmer Dabbelt
2021-04-23 3:53 ` Nick Kossifidis [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=d3e45b902a28ec95c25cfa1f34d07d0d@mailhost.ics.forth.gr \
--to=mick@ics.forth.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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).