From: Aurelien Jarno <aurelien@aurel32.net>
To: David Abdurachmanov <david.abdurachmanov@sifive.com>
Cc: Atish Patra <Atish.Patra@wdc.com>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"drew@beagleboard.org" <drew@beagleboard.org>,
Alistair Francis <Alistair.Francis@wdc.com>,
"lakshmipathi.ganapathi@collabora.co.uk"
<lakshmipathi.ganapathi@collabora.co.uk>,
"kernelci@groups.io" <kernelci@groups.io>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"raj.khem@gmail.com" <raj.khem@gmail.com>,
"clabbe@baylibre.com" <clabbe@baylibre.com>,
Manuel Montecelo <mafm@debian.org>,
Karsten Merker <merker@debian.org>,
Colin Ian King <colin.king@canonical.com>
Subject: Re: Improve kernelci setup for RISC-V
Date: Thu, 2 Jul 2020 16:50:08 +0200 [thread overview]
Message-ID: <20200702145008.GA1155320@aurel32.net> (raw)
In-Reply-To: <CAPSAq_zLQrw-EK70fHj-Kz3Xp+WP4TzFBOOmYY7e3OB+JHnE6w@mail.gmail.com>
On 2020-07-02 16:19, David Abdurachmanov wrote:
> Almost forgot. I suggest we also run stress-ng for CI. It's a single
> binary and it already found a number of kernel related issues on
> Unleashed which usually result in board hanging.
>
> I have added Colin from Canonical who is the author of the stress tool.
stress-ng is already available as a package in the riscv64 port, so it
should just be a matter of installing it:
https://packages.debian.org/unstable/stress-ng
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2020-07-02 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3c2cba2849caa6ea0116611c1da3268b41432b76.camel@wdc.com>
2020-07-02 0:17 ` Improve kernelci setup for RISC-V Kevin Hilman
2020-07-02 7:02 ` Atish Patra
2020-07-02 7:12 ` David Abdurachmanov
2020-07-02 13:19 ` David Abdurachmanov
2020-07-02 14:50 ` Aurelien Jarno [this message]
2020-07-02 14:55 ` Colin Ian King
2020-07-02 14:49 ` Aurelien Jarno
2020-07-02 18:15 ` Karsten Merker
2020-07-02 18:25 ` Kevin Hilman
2020-07-02 20:15 ` Manuel A. Fernandez Montecelo
2020-07-08 23:31 ` Manuel A. Fernandez Montecelo
2020-07-09 6:52 ` Lakshmipathi Ganapathi
2020-07-02 20:19 ` Alistair Francis
2020-07-02 15:49 ` Khem Raj
2020-07-02 11:24 ` Mark Brown
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=20200702145008.GA1155320@aurel32.net \
--to=aurelien@aurel32.net \
--cc=Alistair.Francis@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=clabbe@baylibre.com \
--cc=colin.king@canonical.com \
--cc=david.abdurachmanov@sifive.com \
--cc=drew@beagleboard.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
--cc=lakshmipathi.ganapathi@collabora.co.uk \
--cc=mafm@debian.org \
--cc=merker@debian.org \
--cc=palmer@dabbelt.com \
--cc=raj.khem@gmail.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