linux-kernel - [PATCH 4/4] events: sched_stat_template saves call chains of a target 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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1317052535-1765247-5-git-send-email-avagin@openvz.org>
Date:	Mon, 26 Sep 2011 19:55:35 +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 4/4] events: sched_stat_template saves call chains of a target task

It's more useful, because

sched:sched_stat_iowait:
Before we can see that block layer notifies that i/o request completed.
Now we can see which code wanted to read/write data.

sched:sched_stat_sleep:
Before we can see that delayed_work_timer_fn wakes up a task.
Now we see where a task sleeps.

Signed-off-by: Andrew Vagin <avagin@...nvz.org>
---
 include/trace/events/sched.h |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/include/trace/events/sched.h b/include/trace/events/sched.h
index f633478..7468c7a 100644
--- a/include/trace/events/sched.h
+++ b/include/trace/events/sched.h
@@ -296,6 +296,7 @@ DECLARE_EVENT_CLASS(sched_stat_template,
 		__entry->delay	= delay;
 	)
 	TP_perf_assign(
+		__perf_task(tsk);
 		__perf_count(delay);
 	),
 
-- 
1.7.1

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