Skip to contentSkip to conversation

tracing: Add task activate/deactivate tracepoints

PATCH NAK Frederic Weisbecker 5 participants 15 messages May 28, 2010 – Jun 1, 2010 Tracing

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tracing: Add task activate/deactivate tracepoints

We have various tracepoints that tell us when a task is going to be enqueued in a runqueue: fork, wakeup, migrate.

But they don't always provide us the level of information necessary to know what is actually in which runqueue, precisely because the migrate event is only fired if the task is queued on another cpu than its previous one. So we don't always know where a waking up task goes.

And moreover we don't have events that tells a task goes to sleep, and even that wouldn't cover every cases when a task is dequeued.

So bring these two new tracepoints to get informations about the load of each runqueues.

Cc Peter Zijlstra <[email protected]>
Cc Ingo Molnar <[email protected]>
Cc Steven Rostedt <[email protected]>
---
 include/trace/events/sched.h |   36 ++++++++++++++++++++++++++++++++++++
 kernel/sched.c               |    2 ++
 2 files changed, 38 insertions(+), 0 deletions(-)
include/trace/events/sched.h +36 -0
index 4f733ec..f7f94af 100644
@@ -185,6 +185,42 @@ TRACE_EVENT(sched_migrate_task,
 		  __entry->orig_cpu, __entry->dest_cpu)
 );
 
+DECLARE_EVENT_CLASS(sched_activation_template,
+
+	TP_PROTO(struct task_struct *p, int cpu),
+
+	TP_ARGS(p, cpu),
+
+	TP_STRUCT__entry(
+		__field(	pid_t,	pid	)
+		__field(	int,	cpu	)
+	),
+
+	TP_fast_assign(
+		__entry->pid		= p->pid;
+		__entry->cpu		= cpu;
+	),
+
+	TP_printk("pid=%d cpu=%d", __entry->pid, __entry->cpu)
+);
+
+
+/*
+ * Tracepoint for activating a task, pulling it in a runqueue
+ */
+DEFINE_EVENT(sched_activation_template, sched_activate_task,
+	     TP_PROTO(struct task_struct *p, int cpu),
+	     TP_ARGS(p, cpu));
+
+
+/*
+ * Tracepoint for deactivating a task, pushing it out a runqueue
+ */
+DEFINE_EVENT(sched_activation_template, sched_deactivate_task,
+	     TP_PROTO(struct task_struct *p, int cpu),
+	     TP_ARGS(p, cpu));
+
+
 DECLARE_EVENT_CLASS(sched_process_template,
 
 	TP_PROTO(struct task_struct *p),
kernel/sched.c +2 -0
index 1d93cd0..8c0b90d 100644
@@ -1904,6 +1904,7 @@ static void activate_task(struct rq *rq, struct task_struct *p, int flags)
 	if (task_contributes_to_load(p))
 		rq->nr_uninterruptible--;
 
+	trace_sched_activate_task(p, cpu_of(rq));
 	enqueue_task(rq, p, flags);
 	inc_nr_running(rq);
 }
@@ -1916,6 +1917,7 @@ static void deactivate_task(struct rq *rq, struct task_struct *p, int flags)
 	if (task_contributes_to_load(p))
 		rq->nr_uninterruptible++;
 
+	trace_sched_deactivate_task(p, cpu_of(rq));
 	dequeue_task(rq, p, flags);
 	dec_nr_running(rq);
 }
Signature · 1 line
1.6.2.3
#1 lore raw
Quoted 9 lines · Frederic Weisbecker

We have various tracepoints that tell us when a task is going to be enqueued in a runqueue: fork, wakeup, migrate.

But they don't always provide us the level of information necessary to know what is actually in which runqueue, precisely because the migrate event is only fired if the task is queued on another cpu than its previous one. So we don't always know where a waking up task goes.

Quoted 5 lines

And moreover we don't have events that tells a task goes to sleep, and even that wouldn't cover every cases when a task is dequeued.

So bring these two new tracepoints to get informations about the load of each runqueues.

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

#2 lore raw
Quoted 13 lines · Peter Zijlstra
Quoted 12 lines · Frederic Weisbecker

We have various tracepoints that tell us when a task is going to be enqueued in a runqueue: fork, wakeup, migrate.

But they don't always provide us the level of information necessary to know what is actually in which runqueue, precisely because the migrate event is only fired if the task is queued on another cpu than its previous one. So we don't always know where a waking up task goes.

And moreover we don't have events that tells a task goes to sleep, and even that wouldn't cover every cases when a task is dequeued.

Quoted 7 lines
Quoted 2 lines

So bring these two new tracepoints to get informations about the load of each runqueues.

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Ingo

#3 lore raw
Quoted 9 lines · Ingo Molnar
Quoted 5 lines

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Right, so a few of those corner cases I mentioned above are things like re-nice, PI-boosts etc.. Those use deactivate, modify task-state, activate cycles. so if you want to see those, we can add an explicit tracepoint for those actions.

An explicit nice/PI-boost tracepoint is much clearer than trying to figure out wth the deactivate/activate cycle was for.

#4 lore raw
Quoted 11 lines · Peter Zijlstra
Quoted 9 lines · Ingo Molnar
Quoted 5 lines

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Quoted 7 lines

Right, so a few of those corner cases I mentioned above are things like re-nice, PI-boosts etc.. Those use deactivate, modify task-state, activate cycles. so if you want to see those, we can add an explicit tracepoint for those actions.

An explicit nice/PI-boost tracepoint is much clearer than trying to figure out wth the deactivate/activate cycle was for.

Another advantage of explicit tracepoints is that you'd see them even for non-running tasks, because we only do the deactivate/activate thingy for runnable tasks.

#5 lore raw
Quoted 17 lines · Peter Zijlstra
Quoted 16 lines · Peter Zijlstra
Quoted 9 lines · Ingo Molnar
Quoted 5 lines

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Right, so a few of those corner cases I mentioned above are things like re-nice, PI-boosts etc.. Those use deactivate, modify task-state, activate cycles. so if you want to see those, we can add an explicit tracepoint for those actions.

Quoted 6 lines
Quoted 2 lines

An explicit nice/PI-boost tracepoint is much clearer than trying to figure out wth the deactivate/activate cycle was for.

Another advantage of explicit tracepoints is that you'd see them even for non-running tasks, because we only do the deactivate/activate thingy for runnable tasks.

Yeah. So I agree with you that activate/deactivate are too much implementation related, they even don't give much sense as we don't know the cause of the event, could be a simple renice, or could be a sleep.

So agreed, this sucks.

For the corner cases like re-nice and PI-boost or so, we can indeed plug some higher level tracepoints there.

But there is one more important problem these tracepoints were solving and that still need something:

We don't know when a task goes to sleep. We have two wait tracepoints, sched_wait_task() to wait for a task to unschedule, and sched_process_wait() that is a hooks for waitid and wait4 syscalls. So we are missing all the event waiting from inside the kernel. But even with that, wait and sleep doesn't mean the same thing. Sleeping don't always involve using the waiting API.

I think we need such tracepoint:

kernel/sched.c +3 -1
index 8c0b90d..5f67c04 100644
@@ -3628,8 +3628,10 @@ need_resched_nonpreemptible:
 	if (prev->state && !(preempt_count() & PREEMPT_ACTIVE)) {
 		if (unlikely(signal_pending_state(prev->state, prev)))
 			prev->state = TASK_RUNNING;
-		else
+		else {
+			trace_sched_task_sleep(prev);
 			deactivate_task(rq, prev, DEQUEUE_SLEEP);
+		}
 		switch_count = &prev->nvcsw;
 	}
 

And if people need tracepoints in the events waiting API, we can add that later.

And concerning the task waking up, if it is not migrated, it means it stays on its orig cpu. This is something that can be dealt from the post-processing.

#6 lore raw
Quoted 64 lines · Frederic Weisbecker
Quoted 17 lines · Peter Zijlstra
Quoted 16 lines · Peter Zijlstra
Quoted 9 lines · Ingo Molnar
Quoted 5 lines

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Right, so a few of those corner cases I mentioned above are things like re-nice, PI-boosts etc.. Those use deactivate, modify task-state, activate cycles. so if you want to see those, we can add an explicit tracepoint for those actions.

Quoted 6 lines
Quoted 2 lines

An explicit nice/PI-boost tracepoint is much clearer than trying to figure out wth the deactivate/activate cycle was for.

Another advantage of explicit tracepoints is that you'd see them even for non-running tasks, because we only do the deactivate/activate thingy for runnable tasks.

Yeah. So I agree with you that activate/deactivate are too much implementation related, they even don't give much sense as we don't know the cause of the event, could be a simple renice, or could be a sleep.

So agreed, this sucks.

For the corner cases like re-nice and PI-boost or so, we can indeed plug some higher level tracepoints there.

But there is one more important problem these tracepoints were solving and that still need something:

We don't know when a task goes to sleep. We have two wait tracepoints, sched_wait_task() to wait for a task to unschedule, and sched_process_wait() that is a hooks for waitid and wait4 syscalls. So we are missing all the event waiting from inside the kernel. But even with that, wait and sleep doesn't mean the same thing. Sleeping don't always involve using the waiting API.

I think we need such tracepoint:

kernel/sched.c +3 -1
index 8c0b90d..5f67c04 100644
@@ -3628,8 +3628,10 @@ need_resched_nonpreemptible:
 	if (prev->state && !(preempt_count() & PREEMPT_ACTIVE)) {
 		if (unlikely(signal_pending_state(prev->state, prev)))
 			prev->state = TASK_RUNNING;
-		else
+		else {
+			trace_sched_task_sleep(prev);
 			deactivate_task(rq, prev, DEQUEUE_SLEEP);
+		}
 		switch_count = &prev->nvcsw;
 	}
 
Quoted 2 lines

And concerning the task waking up, if it is not migrated, it means it stays on its orig cpu. This is something that can be dealt from the post-processing.

Hurm,.. I was thinking trace_sched_switch(.prev_state != TASK_RUNNING) would be enough, but its not for preemptible kernels.

Should we maybe cure this and rely on sched_switch() to detect sleeps? It seems natural since only the current task can go to sleep, its just that the whole preempt state gets a bit iffy.

#7 lore raw
Quoted 68 lines · Peter Zijlstra
Quoted 64 lines · Frederic Weisbecker
Quoted 17 lines · Peter Zijlstra
Quoted 16 lines · Peter Zijlstra
Quoted 9 lines · Ingo Molnar
Quoted 5 lines

NAK, aside from a few corner cases wakeup and sleep are the important points.

The activate and deactivate functions are implementation details.

Frederic, can you show us a concrete example of where we dont know what is going on due to inadequate instrumentation? Can we fix that be extending the existing tracepoints?

Right, so a few of those corner cases I mentioned above are things like re-nice, PI-boosts etc.. Those use deactivate, modify task-state, activate cycles. so if you want to see those, we can add an explicit tracepoint for those actions.

Quoted 6 lines
Quoted 2 lines

An explicit nice/PI-boost tracepoint is much clearer than trying to figure out wth the deactivate/activate cycle was for.

Another advantage of explicit tracepoints is that you'd see them even for non-running tasks, because we only do the deactivate/activate thingy for runnable tasks.

Yeah. So I agree with you that activate/deactivate are too much implementation related, they even don't give much sense as we don't know the cause of the event, could be a simple renice, or could be a sleep.

So agreed, this sucks.

For the corner cases like re-nice and PI-boost or so, we can indeed plug some higher level tracepoints there.

But there is one more important problem these tracepoints were solving and that still need something:

We don't know when a task goes to sleep. We have two wait tracepoints, sched_wait_task() to wait for a task to unschedule, and sched_process_wait() that is a hooks for waitid and wait4 syscalls. So we are missing all the event waiting from inside the kernel. But even with that, wait and sleep doesn't mean the same thing. Sleeping don't always involve using the waiting API.

I think we need such tracepoint:

kernel/sched.c +3 -1
index 8c0b90d..5f67c04 100644
@@ -3628,8 +3628,10 @@ need_resched_nonpreemptible:
 	if (prev->state && !(preempt_count() & PREEMPT_ACTIVE)) {
 		if (unlikely(signal_pending_state(prev->state, prev)))
 			prev->state = TASK_RUNNING;
-		else
+		else {
+			trace_sched_task_sleep(prev);
 			deactivate_task(rq, prev, DEQUEUE_SLEEP);
+		}
 		switch_count = &prev->nvcsw;
 	}
 
Quoted 2 lines

And concerning the task waking up, if it is not migrated, it means it stays on its orig cpu. This is something that can be dealt from the post-processing.

Quoted 6 lines

Hurm,.. I was thinking trace_sched_switch(.prev_state != TASK_RUNNING) would be enough, but its not for preemptible kernels.

Should we maybe cure this and rely on sched_switch() to detect sleeps? It seems natural since only the current task can go to sleep, its just that the whole preempt state gets a bit iffy.

Sounds good, we have the preempt depth in the common tracepoint headers, I'll try to rebuild a reliable cpu runqueue from post-processing and see if all that is enough.

Thanks.

#8 lore raw
Quoted 3 lines · Frederic Weisbecker
Quoted 3 lines

Should we maybe cure this and rely on sched_switch() to detect sleeps? It seems natural since only the current task can go to sleep, its just that the whole preempt state gets a bit iffy.

How about something like the below?

Steve, is that proper usage of CREATE_TRACE_POINT?

---
Subject: sched, trace: Fix sched_switch() prev_state argument
From: Peter Zijlstra <[email protected]>
Date: Mon May 31 18:13:25 CEST 2010

For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't useful because we can get preempted with current->state != TASK_RUNNING without actually getting removed from the runqueue.

Cure this by treating all preempted tasks as runnable from the tracer's point of view.

---
 include/trace/events/sched.h |   19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)
include/trace/events/sched.h +18 -1
Index: linux-2.6/include/trace/events/sched.h
===================================================================
@@ -115,6 +115,23 @@ DEFINE_EVENT(sched_wakeup_template, sche
 	     TP_PROTO(struct task_struct *p, int success),
 	     TP_ARGS(p, success));
 
+#ifdef CREATE_TRACE_POINTS
+static inline long __trace_sched_switch_state(struct task_struct *p)
+{
+	long state = p->state;
+
+#ifdef CONFIG_PREEMPT
+	/*
+	 * For all intents and purposes a preempted task is a running task.
+	 */
+	if (task_thread_info(p)->preempt_count & PREEMPT_ACTIVE)
+		state = TASK_RUNNING;
+#endif
+
+	return state;
+}
+#endif
+
 /*
  * Tracepoint for task switches, performed by the scheduler:
  */
@@ -139,7 +156,7 @@ TRACE_EVENT(sched_switch,
 		memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
 		__entry->prev_pid	= prev->pid;
 		__entry->prev_prio	= prev->prio;
-		__entry->prev_state	= prev->state;
+		__entry->prev_state	= __trace_sched_switch_state(prev);
 		memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
 		__entry->next_pid	= next->pid;
 		__entry->next_prio	= next->prio;
maintainer
#9 lore raw

Expect slow responses from me today. It's a US Holiday.

Quoted 31 lines · Peter Zijlstra
Quoted 3 lines · Frederic Weisbecker
Quoted 3 lines

Should we maybe cure this and rely on sched_switch() to detect sleeps? It seems natural since only the current task can go to sleep, its just that the whole preempt state gets a bit iffy.

How about something like the below?

Steve, is that proper usage of CREATE_TRACE_POINT?

---
Subject: sched, trace: Fix sched_switch() prev_state argument
From: Peter Zijlstra <[email protected]>
Date: Mon May 31 18:13:25 CEST 2010

For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't useful because we can get preempted with current->state != TASK_RUNNING without actually getting removed from the runqueue.

Cure this by treating all preempted tasks as runnable from the tracer's point of view.

---
 include/trace/events/sched.h |   19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

Index: linux-2.6/include/trace/events/sched.h
===================================================================

include/trace/events/sched.h DEFINE_EVENT(sched_wakeup_template, sche · line 118

Quoted 4 lines
include/trace/events/sched.h +1 -0
@@ -115,6 +115,23 @@ DEFINE_EVENT(sched_wakeup_template, sche
 	     TP_PROTO(struct task_struct *p, int success),
 	     TP_ARGS(p, success));
 
+#ifdef CREATE_TRACE_POINTS

I guess this could work. I can't think of anything that would cause this to fail. But this is not exactly what the CREATE_TRACE_POINTS macro was for.

Maybe we could make a CREATE_UTIL_FUNCTIONS macro that the define_trace.h can unset like it does with CREATE_TRACE_POINTS before recursively including the trace headers.

Maybe I'm a bit paranoid, but I'm a little nervous to extend the CREATE_TRACE_POINTS macro to be used within the header to create utility functions, although, currently I don't think there's anything technically wrong in doing so.

-- Steve

Quoted 29 lines
include/trace/events/sched.h +17 -1
+static inline long __trace_sched_switch_state(struct task_struct *p)
+{
+	long state = p->state;
+
+#ifdef CONFIG_PREEMPT
+	/*
+	 * For all intents and purposes a preempted task is a running task.
+	 */
+	if (task_thread_info(p)->preempt_count & PREEMPT_ACTIVE)
+		state = TASK_RUNNING;
+#endif
+
+	return state;
+}
+#endif
+
 /*
  * Tracepoint for task switches, performed by the scheduler:
  */
@@ -139,7 +156,7 @@ TRACE_EVENT(sched_switch,
 		memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
 		__entry->prev_pid	= prev->pid;
 		__entry->prev_prio	= prev->prio;
-		__entry->prev_state	= prev->state;
+		__entry->prev_state	= __trace_sched_switch_state(prev);
 		memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
 		__entry->next_pid	= next->pid;
 		__entry->next_prio	= next->prio;
#10 lore raw
Quoted 7 lines · Steven Rostedt
Quoted 2 lines

+#ifdef CREATE_TRACE_POINTS

I guess this could work. I can't think of anything that would cause this to fail. But this is not exactly what the CREATE_TRACE_POINTS macro was for.

Quoted 8 lines

Maybe we could make a CREATE_UTIL_FUNCTIONS macro that the define_trace.h can unset like it does with CREATE_TRACE_POINTS before recursively including the trace headers.

Maybe I'm a bit paranoid, but I'm a little nervous to extend the CREATE_TRACE_POINTS macro to be used within the header to create utility functions, although, currently I don't think there's anything technically wrong in doing so.

Right, I can attest to the compile mess that results in not having it :-) Given that, I think we're fairly safe with stretching it like this, the compiler will yell real loud if you mess this up. So I'm not sure you need to be very paranoid about this.

Duplicating the whole CREATE_TRACE_POINT logic just for a different name doesn't seem worth the effort at this time, esp. given the compiler results if you get it wrong.

So do you object if I merge this for now, or would you really rather see something else?

maintainer
#11 lore raw
Quoted 6 lines · Peter Zijlstra
Quoted 1 line · Steven Rostedt
Quoted 1 line

So do you object if I merge this for now, or would you really rather see something else?

No, I don't object.

-- Steve

maintainer
#12 lore raw
In reply to Peter Zijlstra
Quoted 11 lines · Peter Zijlstra
Quoted 4 lines · Steven Rostedt

Maybe I'm a bit paranoid, but I'm a little nervous to extend the CREATE_TRACE_POINTS macro to be used within the header to create utility functions, although, currently I don't think there's anything technically wrong in doing so.

Right, I can attest to the compile mess that results in not having it :-) Given that, I think we're fairly safe with stretching it like this, the compiler will yell real loud if you mess this up. So I'm not sure you need to be very paranoid about this.

Actually, I'm not worried about getting the utility functions right. I'm actually more worried about extending TRACE_EVENT() and having this be a thorn in our side when doing so.

-- Steve

#13 lore raw
In reply to Peter Zijlstra
Quoted 18 lines · Peter Zijlstra
Quoted 3 lines · Frederic Weisbecker
Quoted 3 lines

Should we maybe cure this and rely on sched_switch() to detect sleeps? It seems natural since only the current task can go to sleep, its just that the whole preempt state gets a bit iffy.

How about something like the below?

Steve, is that proper usage of CREATE_TRACE_POINT?

---
Subject: sched, trace: Fix sched_switch() prev_state argument
From: Peter Zijlstra <[email protected]>
Date: Mon May 31 18:13:25 CEST 2010

For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't useful because we can get preempted with current->state != TASK_RUNNING without actually getting removed from the runqueue.

Quoted 5 lines

Cure this by treating all preempted tasks as runnable from the tracer's point of view.

---

Other than Steve's said, the thing looks good.

#14 lore raw

[tip:sched/urgent] sched, trace: Fix sched_switch() prev_state argument

In reply to Peter Zijlstra
Commit-ID:  02f726949f2be0967aa4871dd4e47d3967779b26
Gitweb:     http://git.kernel.org/tip/02f726949f2be0967aa4871dd4e47d3967779b26
Author:     Peter Zijlstra <[email protected]>
AuthorDate: Mon, 31 May 2010 18:13:25 +0200
Committer:  Ingo Molnar <[email protected]>
CommitDate: Tue, 1 Jun 2010 09:27:17 +0200

sched, trace: Fix sched_switch() prev_state argument

For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't useful because we can get preempted with current->state != TASK_RUNNING without actually getting removed from the runqueue.

Cure this by treating all preempted tasks as runnable from the tracer's point of view.

LKML-Reference: <1275322715.27810.23323.camel@twins>

---
 include/trace/events/sched.h |   19 ++++++++++++++++++-
 1 files changed, 18 insertions(+), 1 deletions(-)
include/trace/events/sched.h +18 -1
index 4f733ec..b9e1dd6 100644
@@ -115,6 +115,23 @@ DEFINE_EVENT(sched_wakeup_template, sched_wakeup_new,
 	     TP_PROTO(struct task_struct *p, int success),
 	     TP_ARGS(p, success));
 
+#ifdef CREATE_TRACE_POINTS
+static inline long __trace_sched_switch_state(struct task_struct *p)
+{
+	long state = p->state;
+
+#ifdef CONFIG_PREEMPT
+	/*
+	 * For all intents and purposes a preempted task is a running task.
+	 */
+	if (task_thread_info(p)->preempt_count & PREEMPT_ACTIVE)
+		state = TASK_RUNNING;
+#endif
+
+	return state;
+}
+#endif
+
 /*
  * Tracepoint for task switches, performed by the scheduler:
  */
@@ -139,7 +156,7 @@ TRACE_EVENT(sched_switch,
 		memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
 		__entry->prev_pid	= prev->pid;
 		__entry->prev_prio	= prev->prio;
-		__entry->prev_state	= prev->state;
+		__entry->prev_state	= __trace_sched_switch_state(prev);
 		memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
 		__entry->next_pid	= next->pid;
 		__entry->next_prio	= next->prio;