Re: [PATCH] sched: fix tracepoint in scheduler.

2014-05-21 Thread Peter Zijlstra
On Wed, May 21, 2014 at 06:03:53PM +0800, Dongsheng Yang wrote: > Hi Peter, did you forget to take this patch? :-) No, I skipped it on purpose, its useful to be able to see if code tries to do superfluous migrations. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-05-21 Thread Dongsheng Yang
Hi Peter, did you forget to take this patch? :-) On Fri, Apr 4, 2014 at 8:52 PM, Peter Zijlstra wrote: > On Thu, Apr 03, 2014 at 08:12:48PM +0800, Dongsheng Yang wrote: >> In function set_task_cpu(), if cpu == new_cpu, >> there is no migration happen. But current trace point >> will raise a

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-05-21 Thread Dongsheng Yang
Hi Peter, did you forget to take this patch? :-) On Fri, Apr 4, 2014 at 8:52 PM, Peter Zijlstra pet...@infradead.org wrote: On Thu, Apr 03, 2014 at 08:12:48PM +0800, Dongsheng Yang wrote: In function set_task_cpu(), if cpu == new_cpu, there is no migration happen. But current trace point will

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-05-21 Thread Peter Zijlstra
On Wed, May 21, 2014 at 06:03:53PM +0800, Dongsheng Yang wrote: Hi Peter, did you forget to take this patch? :-) No, I skipped it on purpose, its useful to be able to see if code tries to do superfluous migrations. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-04-04 Thread Peter Zijlstra
On Thu, Apr 03, 2014 at 08:12:48PM +0800, Dongsheng Yang wrote: > In function set_task_cpu(), if cpu == new_cpu, > there is no migration happen. But current trace point > will raise a migration trace event. > > This patch change trace point to right place, > only when migration really happen, an

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-04-04 Thread Peter Zijlstra
On Thu, Apr 03, 2014 at 08:12:48PM +0800, Dongsheng Yang wrote: In function set_task_cpu(), if cpu == new_cpu, there is no migration happen. But current trace point will raise a migration trace event. This patch change trace point to right place, only when migration really happen, an event

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-04-03 Thread Rik van Riel
On 04/03/2014 08:12 AM, Dongsheng Yang wrote: > In function set_task_cpu(), if cpu == new_cpu, > there is no migration happen. But current trace point > will raise a migration trace event. > > This patch change trace point to right place, > only when migration really happen, an event will > be

[PATCH] sched: fix tracepoint in scheduler.

2014-04-03 Thread Dongsheng Yang
In function set_task_cpu(), if cpu == new_cpu, there is no migration happen. But current trace point will raise a migration trace event. This patch change trace point to right place, only when migration really happen, an event will be threw out. Signed-off-by: Dongsheng Yang ---

Re: [PATCH] sched: fix tracepoint in scheduler.

2014-04-03 Thread Rik van Riel
On 04/03/2014 08:12 AM, Dongsheng Yang wrote: In function set_task_cpu(), if cpu == new_cpu, there is no migration happen. But current trace point will raise a migration trace event. This patch change trace point to right place, only when migration really happen, an event will be threw

[PATCH] sched: fix tracepoint in scheduler.

2014-04-03 Thread Dongsheng Yang
In function set_task_cpu(), if cpu == new_cpu, there is no migration happen. But current trace point will raise a migration trace event. This patch change trace point to right place, only when migration really happen, an event will be threw out. Signed-off-by: Dongsheng Yang