From: Nick Kossifidis <mick@ics.forth.gr>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: david.abdurachmanov@sifive.com, anup@brainfault.org,
Atish Patra <Atish.Patra@wdc.com>,
yibin_liu@c-sky.com, Paul Walmsley <paul.walmsley@sifive.com>,
mick@ics.forth.gr, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 0/3] RISC-V: Add kexec/kdump support
Date: Fri, 19 Jun 2020 11:27:18 +0300 [thread overview]
Message-ID: <f0e6106e0ca4c1d8a6fa33dea6ee7276@mailhost.ics.forth.gr> (raw)
In-Reply-To: <mhng-524c37c9-25b7-405f-933f-2029820dbe40@palmerdabbelt-glaptop1>
Στις 2020-06-19 02:06, Palmer Dabbelt έγραψε:
> On Sat, 13 Jun 2020 00:24:01 PDT (-0700), mick@ics.forth.gr wrote:
>> Στις 2020-06-11 22:39, Palmer Dabbelt έγραψε:
>>> On Thu, 11 Jun 2020 12:09:08 PDT (-0700), mick@ics.forth.gr wrote:
>>>> Στις 2020-05-21 21:42, Nick Kossifidis έγραψε:
>>>>> Στις 2020-04-24 20:12, Nick Kossifidis έγραψε:
>>>>>> 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. The patch is still
>>>>>> a work in progress but a draft version can be found at:
>>>>>>
>>>>>> http://riscv.ics.forth.gr/kexec-tools.patch
>>>>>>
>>>>>
>>>>> Any comments / feedback on this ? Should we get it in ?
>>>>>
>>>>> Regards,
>>>>> Nick
>>>>
>>>> Anyone ?
>>>
>>> Sorry, I dropped the ball on this one. After the CPU hotplug
>>> breakage
>>> I
>>> decided I need to get a pre-merge test for all these new features,
>>> and
>>> I
>>> haven't gotten around to actually doing so yet. The merge window is
>>> closing
>>> right now, so with any luck I'll have some time to get around to my
>>> patch
>>> backlog -- first I need to go spin up some better testing, though.
>>
>> Anything I can do to help ? I have a bunch of hw available (unleashed,
>> genesys2 and nexys 2 ddr for Ariane / LowRISC SoC) and I'll probably
>> also need to have a CI flow for the stuff I do internally.
>
> Well, getting CI up and running would be great -- specifically, running
> stress
> tests on real hardware is something we're missing.
Any particular tests / test suites in mind ?
next prev parent reply other threads:[~2020-06-19 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 17:12 [PATCH 0/3] RISC-V: Add kexec/kdump support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 1/3] RISC-V: Add kexec support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 2/3] RISC-V: Add kdump support Nick Kossifidis
2020-04-24 17:12 ` [PATCH 3/3] RISC-V: Add crash kernel support Nick Kossifidis
2020-05-21 18:42 ` [PATCH 0/3] RISC-V: Add kexec/kdump support Nick Kossifidis
2020-06-11 19:09 ` Nick Kossifidis
2020-06-11 19:39 ` Palmer Dabbelt
2020-06-13 7:24 ` Nick Kossifidis
2020-06-13 8:17 ` Anup Patel
2020-06-13 8:21 ` Nick Kossifidis
2020-06-18 23:06 ` Palmer Dabbelt
2020-06-19 8:27 ` Nick Kossifidis [this message]
2020-06-19 17:23 ` Atish Patra
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=f0e6106e0ca4c1d8a6fa33dea6ee7276@mailhost.ics.forth.gr \
--to=mick@ics.forth.gr \
--cc=Atish.Patra@wdc.com \
--cc=anup@brainfault.org \
--cc=david.abdurachmanov@sifive.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=yibin_liu@c-sky.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