linux-kernel - Re: [PATCH] sched: Distinguish sched_wakeup event when wake up a task which did schedule out or not.

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: <20140512111748.1c2f6cd9@gandalf.local.home>
Date:	Mon, 12 May 2014 11:17:48 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Dongsheng Yang <dongsheng081251@...il.com>,
	"yangds.fnst" <yangds.fnst@...fujitsu.com>,
	linux-kernel@...r.kernel.org, mingo@...hat.com, bsegall@...gle.com
Subject: Re: [PATCH] sched: Distinguish sched_wakeup event when wake up a
 task which did schedule out or not.

On Mon, 12 May 2014 17:09:50 +0200
Peter Zijlstra <peterz@...radead.org> wrote:

> > Point being, this is useful information, why not pass it to userspace?
> 
> Because it adds code to one of the hottest code paths in the kernel and
> so far nobody had a sane explanation of WTF they were doing.
> 

Is there a measurable difference with these extra tracepoints?

-- Steve

--
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/