[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210111151120.GD2743@paulmck-ThinkPad-P72>
Date: Mon, 11 Jan 2021 07:11:20 -0800
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: tglx@...utronix.de, linux-kernel@...r.kernel.org,
valentin.schneider@....com, bristot@...hat.com, frederic@...nel.org
Subject: Re: lockdep splat in v5.11-rc1 involving console_sem and rq locks
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
Powered by blists - more mailing lists