From: Robert Elliott <elliott@hpe.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
paulmck@kernel.org, frederic@kernel.org,
quic_neeraju@quicinc.com, josh@joshtriplett.org
Cc: linux-crypto@vger.kernel.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org, Robert Elliott <elliott@hpe.com>
Subject: [PATCH 0/3] crypto/rcu: suppress unnecessary CPU stall warnings
Date: Mon, 19 Dec 2022 14:29:07 -0600 [thread overview]
Message-ID: <20221219202910.3063036-1-elliott@hpe.com> (raw)
Suppress RCU CPU stall warnings during tcrypt speed tests.
Robert Elliott (3):
rcu: genericize RCU stall suppression functions
rcu: print first CPU on expedited stall line
crypto: tcrypt - suppress RCU stall warnings during speed tests
.../RCU/Design/Requirements/Requirements.rst | 6 +-
Documentation/RCU/stallwarn.rst | 19 ++-
arch/parisc/kernel/process.c | 2 +-
crypto/tcrypt.c | 113 +++++++++++++++---
drivers/tty/sysrq.c | 4 +-
include/linux/rcupdate.h | 8 +-
kernel/rcu/rcu.h | 11 +-
kernel/rcu/tree_exp.h | 22 ++--
kernel/rcu/tree_stall.h | 18 +--
kernel/rcu/update.c | 11 +-
10 files changed, 160 insertions(+), 54 deletions(-)
--
2.38.1
next reply other threads:[~2022-12-19 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 20:29 Robert Elliott [this message]
2022-12-19 20:29 ` [PATCH 1/3] rcu: genericize RCU stall suppression functions Robert Elliott
2022-12-21 18:56 ` Paul E. McKenney
2023-01-10 6:07 ` Joel Fernandes
2023-01-10 6:12 ` Joel Fernandes
2022-12-19 20:29 ` [PATCH 2/3] rcu: print first CPU on expedited stall line Robert Elliott
2022-12-21 19:02 ` Paul E. McKenney
2022-12-19 20:29 ` [PATCH 3/3] crypto: tcrypt - suppress RCU stall warnings during speed tests Robert Elliott
2022-12-30 8:39 ` Herbert Xu
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=20221219202910.3063036-1-elliott@hpe.com \
--to=elliott@hpe.com \
--cc=davem@davemloft.net \
--cc=frederic@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=josh@joshtriplett.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@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.