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
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
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
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
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
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
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
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
---
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
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
10 matches
Mail list logo