[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190511214520.GA3251@andrea>
Date: Sat, 11 May 2019 23:45:20 +0200
From: Andrea Parri <andrea.parri@...rulasolutions.com>
To: "Paul E. McKenney" <paulmck@...ux.ibm.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Morten Rasmussen <morten.rasmussen@....com>, joelaf@...gle.com,
Vincent Guittot <vincent.guittot@...aro.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: Question about sched_setaffinity()
> > The below trace explain the issue. Some Paul person did it, see below.
> > It's broken per construction :-)
>
> *facepalm* Hence the very strange ->cpus_allowed mask. I really
> should have figured that one out.
>
> The fix is straightforward. I just added "rcutorture.shuffle_interval=0"
> to the TRIVIAL.boot file, which stops rcutorture from shuffling its
> kthreads around.
I added the option to the file and I didn't reproduce the issue.
> Please accept my apologies for the hassle, and thank you for tracking
> this down!!!
Peter (echoing Paul): Thank you for pointing that shuffler out!
Andrea
Powered by blists - more mailing lists