Messages in this thread | | | From | Joel Fernandes <> | Date | Mon, 4 May 2020 14:18:50 -0400 | Subject | Re: [PATCH v3 0/5] RCU dyntick nesting counter cleanups for rcu -dev |
| |
On Mon, May 4, 2020 at 1:44 PM Paul E. McKenney <paulmck@kernel.org> wrote: > > On Mon, May 04, 2020 at 10:15:32AM -0700, Paul E. McKenney wrote: > > On Mon, May 04, 2020 at 08:05:00AM -0400, Joel Fernandes (Google) wrote: > > > These patches clean up the usage of dynticks nesting counters simplifying the > > > code, while preserving the usecases. > > > > > > It is a much needed simplification, makes the code less confusing, and prevents > > > future bugs such as those that arise from forgetting that the > > > dynticks_nmi_nesting counter is not a simple counter and can be "crowbarred" in > > > common situations. > > > > > > rcutorture testing with all TREE RCU configurations succeed with > > > CONFIG_RCU_EQS_DEBUG=y and CONFIG_PROVE_LOCKING=y. > > > > > > v1->v2: > > > - Rebase on v5.6-rc6 > > > > > > v2->v3: > > > - Rebase on rcu/dev with adjustments for tasks-RCU. > > > > Thank you! > > > > But this does not apply to any of v5.6-rc6, v5.7-rc1, or v5.7-rc2. > > > > Where should I be trying to apply it? > > OK, morning blindness overcome. I new see the "rcu/dev" in v2->v3. > > Please accept my apologies for the noise.
No problem, glad it got resolved. Thanks!
- Joel
| |