From: Eric Biggers <ebiggers@kernel.org>
To: Demi Marie Obenour <demiobenour@gmail.com>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-arm-msm@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] drivers/crypto: Mark QCE as BROKEN
Date: Wed, 22 Jul 2026 16:33:31 +0000 [thread overview]
Message-ID: <20260722163331.GA2865613@google.com> (raw)
In-Reply-To: <8e9101ce-e9ec-4111-a1a6-7a9a07788818@gmail.com>
On Wed, Jul 22, 2026 at 11:46:16AM -0400, Demi Marie Obenour wrote:
> With your patch, does the driver also pass stress tests, such as
> multiple threads using it in parallel with varying algorithms and
> message sizes?
As I've mentioned before, the self-tests (crypto/testmgr.c) don't issue
more than one request concurrently. They are really designed for
testing the software implementations, not the hardware drivers. None of
the hardware driver authors has ever caused enough about quality to make
any significant improvements to the tests. Inevitably it's just push
the driver in, *maybe* run the existing incomplete tests once (for QCE
it's finally getting done just now), and job done I guess.
- Eric
next prev parent reply other threads:[~2026-07-22 16:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 21:31 [PATCH v2] drivers/crypto: Mark QCE as BROKEN Demi Marie Obenour via B4 Relay
2026-07-13 2:57 ` Eric Biggers
2026-07-13 4:47 ` Greg KH
2026-07-13 13:07 ` Eric Biggers
2026-07-13 13:19 ` Greg KH
2026-07-13 14:42 ` Demi Marie Obenour
2026-07-13 15:31 ` Greg KH
2026-07-13 19:49 ` Demi Marie Obenour
2026-07-13 19:56 ` Demi Marie Obenour
2026-07-17 8:18 ` Herbert Xu
2026-07-21 8:24 ` Bartosz Golaszewski
2026-07-21 18:29 ` Demi Marie Obenour
2026-07-22 8:33 ` Bartosz Golaszewski
2026-07-22 15:46 ` Demi Marie Obenour
2026-07-22 16:33 ` Eric Biggers [this message]
2026-07-22 16: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=20260722163331.GA2865613@google.com \
--to=ebiggers@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=davem@davemloft.net \
--cc=demiobenour@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox