From: Stafford Horne <shorne@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: openrisc@lists.librecores.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireguard: selftests: support OpenRISC
Date: Wed, 29 Jun 2022 05:44:59 +0900 [thread overview]
Message-ID: <YrtoS7ZUnKUg8Soz@antec> (raw)
In-Reply-To: <20220628000210.763674-1-Jason@zx2c4.com>
On Tue, Jun 28, 2022 at 02:02:10AM +0200, Jason A. Donenfeld wrote:
> Stafford and I have been using this to shake out OpenRISC bugs, and it's
> been a great help, so it's time OpenRISC support for the WireGuard test
> suite is made into a proper commit. The QEMU changes necessary for this
> to work should also be around the corner now, and they seem some what
> stationary in their interface too.
>
> Cc: Stafford Horne <shorne@gmail.com>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Hello,
I am not sure what happened to my reply on this yesterday, but I did have this
queued for 5.19 fixes. However, as we just discussed there are still some soft
lockup issues that cause 'rcu: INFO: rcu_preempt detected stalls' noise.
I will hold off sending this upstream for now.
Example isssues:
- https://א.cc/x3Vt402T
- https://xn--4db.cc/bKiNzmFE
-Stafford
next prev parent reply other threads:[~2022-06-28 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 0:02 [PATCH] wireguard: selftests: support OpenRISC Jason A. Donenfeld
2022-06-28 20:44 ` Stafford Horne [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-28 20:36 Joe R
2022-06-28 21:01 ` Stafford Horne
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=YrtoS7ZUnKUg8Soz@antec \
--to=shorne@gmail.com \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).