Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-28 Thread Paul E. McKenney
On Fri, Jul 28, 2017 at 08:18:18AM -0400, Steven Rostedt wrote: > On Thu, 27 Jul 2017 20:22:32 -0700 > "Paul E. McKenney" wrote: > > > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > > On Mon, 24 Jul 2017 14:44:36 -0700 > > > "Paul E. McKenney"

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-28 Thread Paul E. McKenney
On Fri, Jul 28, 2017 at 08:18:18AM -0400, Steven Rostedt wrote: > On Thu, 27 Jul 2017 20:22:32 -0700 > "Paul E. McKenney" wrote: > > > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > > On Mon, 24 Jul 2017 14:44:36 -0700 > > > "Paul E. McKenney" wrote: > > > > > > > There

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-28 Thread Steven Rostedt
On Thu, 27 Jul 2017 20:22:32 -0700 "Paul E. McKenney" wrote: > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > On Mon, 24 Jul 2017 14:44:36 -0700 > > "Paul E. McKenney" wrote: > > > > > There is currently event

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-28 Thread Steven Rostedt
On Thu, 27 Jul 2017 20:22:32 -0700 "Paul E. McKenney" wrote: > On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > > On Mon, 24 Jul 2017 14:44:36 -0700 > > "Paul E. McKenney" wrote: > > > > > There is currently event tracing to track when a task is preempted > > > within a

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-27 Thread Paul E. McKenney
On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > On Mon, 24 Jul 2017 14:44:36 -0700 > "Paul E. McKenney" wrote: > > > There is currently event tracing to track when a task is preempted > > within a preemptible RCU read-side critical section, and also

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-27 Thread Paul E. McKenney
On Thu, Jul 27, 2017 at 09:38:10PM -0400, Steven Rostedt wrote: > On Mon, 24 Jul 2017 14:44:36 -0700 > "Paul E. McKenney" wrote: > > > There is currently event tracing to track when a task is preempted > > within a preemptible RCU read-side critical section, and also when that > > task

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-27 Thread Steven Rostedt
On Mon, 24 Jul 2017 14:44:36 -0700 "Paul E. McKenney" wrote: > There is currently event tracing to track when a task is preempted > within a preemptible RCU read-side critical section, and also when that > task subsequently reaches its outermost rcu_read_unlock(), but

Re: [PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-27 Thread Steven Rostedt
On Mon, 24 Jul 2017 14:44:36 -0700 "Paul E. McKenney" wrote: > There is currently event tracing to track when a task is preempted > within a preemptible RCU read-side critical section, and also when that > task subsequently reaches its outermost rcu_read_unlock(), but none > indicating when a

[PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-24 Thread Paul E. McKenney
There is currently event tracing to track when a task is preempted within a preemptible RCU read-side critical section, and also when that task subsequently reaches its outermost rcu_read_unlock(), but none indicating when a new grace period starts when that grace period must wait on pre-existing

[PATCH tip/core/rcu 07/15] rcu: Add event tracing to ->gp_tasks update at GP start

2017-07-24 Thread Paul E. McKenney
There is currently event tracing to track when a task is preempted within a preemptible RCU read-side critical section, and also when that task subsequently reaches its outermost rcu_read_unlock(), but none indicating when a new grace period starts when that grace period must wait on pre-existing