From: "Paul E. McKenney" <paulmck@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
valentin.schneider@arm.com, bristot@redhat.com,
frederic@kernel.org
Subject: Re: lockdep splat in v5.11-rc1 involving console_sem and rq locks
Date: Mon, 11 Jan 2021 07:11:20 -0800 [thread overview]
Message-ID: <20210111151120.GD2743@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <X/xj1HL8MuoFc7F+@hirez.programming.kicks-ass.net>
On Mon, Jan 11, 2021 at 03:42:28PM +0100, Peter Zijlstra wrote:
> On Tue, Jan 05, 2021 at 02:01:15PM -0800, Paul E. McKenney wrote:
> > Hello!
> >
> > The RUDE01 rcutorture scenario (and less often, the TASKS01 scenario)
>
> Is:
>
> tools/testing/selftests/rcutorture/bin/kvm.sh --duration 10 --configs RUDE01 --allcpus
>
> the right incantation?
I responded on IRC, but may as well make it official:
tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration 10 --configs '32*RUDE01' --trust-make
This assumes a 64-CPU box, hence for this two-CPU scenario "32*". This
will run 32 concurrent instances of RUDE01, thus reproducing more quickly.
The "--trust-make" is important in your case to avoid clobbering your
tags files.
Thanx, Paul
prev parent reply other threads:[~2021-01-11 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 22:01 lockdep splat in v5.11-rc1 involving console_sem and rq locks Paul E. McKenney
2021-01-06 9:52 ` Peter Zijlstra
2021-01-06 14:46 ` Paul E. McKenney
2021-01-06 15:44 ` Peter Zijlstra
2021-01-06 15:49 ` Valentin Schneider
2021-01-06 17:52 ` Paul E. McKenney
2021-01-11 14:42 ` Peter Zijlstra
2021-01-11 15:11 ` Paul E. McKenney [this message]
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=20210111151120.GD2743@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bristot@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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;
as well as URLs for NNTP newsgroup(s).