[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190512010539.GA8167@andrea>
Date: Sun, 12 May 2019 03:05:39 +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 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.
>
> Thank you! May I add your Tested-by?
Please feel free to do so. But it may be worth to squash "the commits"
(and adjust the changelogs accordingly). And you might want to remove
some of those debug checks/prints?
Andrea
Powered by blists - more mailing lists