linux-kernel - Re: [PATCH] sched: fix tracepoint in scheduler.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <533D6D9E.1020401@redhat.com>
Date:	Thu, 03 Apr 2014 10:18:06 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Dongsheng Yang <yangds.fnst@...fujitsu.com>, mingo@...hat.com,
	peterz@...radead.org
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: fix tracepoint in scheduler.

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 out.
> 
> Signed-off-by: Dongsheng Yang <yangds.fnst@...fujitsu.com>

I don't see any obvious place where set_task_cpu is called
with cpu == new_cpu, but there might be an un-obvious place,
because that if looks like it's there for a reason :)

Acked-by: Rik van Riel <riel@...hat.com>

-- 
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/