All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Atish Patra <atishp@atishpatra.org>
To: Nick Kossifidis <mick@ics.forth.gr>, Kevin Hilman <khilman@kernel.org>
Cc: David Abdurachmanov <david.abdurachmanov@sifive.com>,
	Anup Patel <anup@brainfault.org>,
	Atish Patra <Atish.Patra@wdc.com>,
	Liu Yibin <yibin_liu@c-sky.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [PATCH 0/3] RISC-V: Add kexec/kdump support
Date: Fri, 19 Jun 2020 10:23:12 -0700	[thread overview]
Message-ID: <CAOnJCUKjBTdsv=9N1sGwiOe93CMMMyPcteBCQpqOQZScJwS-_A@mail.gmail.com> (raw)
In-Reply-To: <f0e6106e0ca4c1d8a6fa33dea6ee7276@mailhost.ics.forth.gr>

On Fri, Jun 19, 2020 at 1:27 AM Nick Kossifidis <mick@ics.forth.gr> wrote:
>
> Στις 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 ?
>

I quickly checked kerneci project. They regularly build and does a boot test on
HiFive unleashed. Here is the log for the last successful boot test on 5.8-rc1.
https://kernelci.org/test/case/id/5ee3959b44cd149f2b97bf1b/

Can we leverage the same setup locally ?

+kevin

Is there any way to add more tests (lkp test may be ?) for riscv to
kernelci infrastructure ?

-- 
Regards,
Atish


      reply	other threads:[~2020-06-19 17:23 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
2020-06-19 17:23             ` Atish Patra [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='CAOnJCUKjBTdsv=9N1sGwiOe93CMMMyPcteBCQpqOQZScJwS-_A@mail.gmail.com' \
    --to=atishp@atishpatra.org \
    --cc=Atish.Patra@wdc.com \
    --cc=anup@brainfault.org \
    --cc=david.abdurachmanov@sifive.com \
    --cc=khilman@kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mick@ics.forth.gr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.