[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b8f2e454-f188-4603-b410-9b28fcbb148c@paulmck-laptop>
Date: Wed, 4 Oct 2023 14:54:57 -0700
From: "Paul E. McKenney" <paulmck@...nel.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Yong He <zhuangel570@...il.com>,
Neeraj upadhyay <neeraj.iitr10@...il.com>,
Joel Fernandes <joel@...lfernandes.org>,
Boqun Feng <boqun.feng@...il.com>,
Uladzislau Rezki <urezki@...il.com>, RCU <rcu@...r.kernel.org>
Subject: Re: [PATCH 0/5] srcu fixes
On Wed, Oct 04, 2023 at 11:27:29PM +0200, Frederic Weisbecker wrote:
> Le Wed, Oct 04, 2023 at 09:47:04AM -0700, Paul E. McKenney a écrit :
> > > The 10-hour 40-CPU SRCU-P run and pair of 10-hour 16-CPU SRCU-N runs
> > > completed without failure. The others had some failures, but I need
> > > to look and see if any were unexpected. In the meantime, I started a
> > > two-hour 40-CPU SRCU-P run and a pair of one-hour 16-CPU SRCU-N runs on
> > > just that first commit. Also servicing SIGSHOWER and SIGFOOD. ;-)
> >
> > And the two-hour 40-CPU SRCU-P run and a pair of two-hour 16-CPU SRCU-N
> > runs (on only the first commit) completed without incident.
> >
> > The other set of overnight full-stack runs had only tick-stop errors,
> > so I started a two-hour set on the first commit.
> >
> > So far so good!
>
> Very nice!
>
> As for the tick-stop error, see the upstream fix:
>
> 1a6a46477494 ("timers: Tag (hr)timer softirq as hotplug safe")
Got it, thank you!
And the two-hour set of 200*SRCU-N and 100*SRCU-P had only tick-stop
errors. I am refreshing the test grid, and will run overnight.
Here is hoping!
Thanx, Paul
Powered by blists - more mailing lists