linux-kernel - [PATCH 0/4] trace: add ability to collect call chains of non-current task.

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-next>] [day] [month] [year] [list]

Date:	Mon, 26 Sep 2011 19:55:31 +0400
From:	Andrew Vagin <avagin@...nvz.org>
To:	linux-kernel@...r.kernel.org
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	avagin@...nvz.org
Subject: [PATCH 0/4] trace: add ability to collect call chains of non-current task.

Without these patches, an event may only save call chain of a current
task, but some events may require call chains of non-current task.

E.g. You may want to know where and how long a task is sleeping. A time
slice is known when the task wakes up.  We send event in this moment,
but a target task isn't "current".

Usually when the system begin stuttering, it often waits a lock or an
operation for a long time. For investigation such situation you probaly
send sysrq-t and analyze backtraces, but perf may do it more effectively.

A macto __perf_task() is set task for wich a call chain will be collected.

Now this functionality is suitable for sched_stat_sleep and sched_stat_iowait.
--
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/