linux-kernel - Re: [PATCH] tracing: Add task activate/deactivate tracepoints

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 31 May 2010 10:12:24 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] tracing: Add task activate/deactivate tracepoints

On Mon, 2010-05-31 at 10:00 +0200, Ingo Molnar wrote:
> > 
> > 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.
--
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/