From: Eric Biggers <ebiggers@kernel.org>
To: Nathaniel Roach <nroach44@nroach44.id.au>
Cc: Andreas Larsson <andreas@gaisler.com>,
"David S. Miller" <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: Does the SPARC optimized crypto and CRC code actually work?
Date: Tue, 17 Mar 2026 03:45:39 +0000 [thread overview]
Message-ID: <20260317034539.GA2705965@google.com> (raw)
In-Reply-To: <ca9ba2ec-849c-4f86-8ac9-274ac4b5f885@nroach44.id.au>
On Tue, Mar 17, 2026 at 10:48:52AM +0800, Nathaniel Roach wrote:
> I've been testing some of the PCI changes that have come through on my T5-2.
> I'll happily add some tests for the crypto functions, I've just got no idea
> how to do so.
Well, try enabling all KUnit tests in lib/crc/ and lib/crypto/, as well
as CONFIG_CRYPTO_SELFTESTS=y and CONFIG_CRYPTO_SELFTESTS_FULL=y.
However, will this be a regular testing run, or only a one-off run? If
it will only be one-off, we'll quickly be back to where we started.
We need regular testing on either hardware or QEMU.
- Eric
next prev parent reply other threads:[~2026-03-17 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 20:42 Does the SPARC optimized crypto and CRC code actually work? Eric Biggers
2026-03-17 2:48 ` Nathaniel Roach
2026-03-17 3:45 ` Eric Biggers [this message]
2026-03-17 7:16 ` John Paul Adrian Glaubitz
2026-03-17 14:06 ` Theodore Tso
2026-03-17 14:14 ` John Paul Adrian Glaubitz
2026-03-22 14:59 ` Eric Biggers
2026-03-23 5:58 ` John Paul Adrian Glaubitz
2026-03-23 10:36 ` Nathaniel Roach
2026-03-23 18:20 ` Eric Biggers
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=20260317034539.GA2705965@google.com \
--to=ebiggers@kernel.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=nroach44@nroach44.id.au \
--cc=sparclinux@vger.kernel.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 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.