linux-kernel - Re: [PATCH 1/2] perf tools: Import trace saved cmdlines to threads base

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: <20090828055132.GA22240@elte.hu>
Date:	Fri, 28 Aug 2009 07:51:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH 1/2] perf tools: Import trace saved cmdlines to threads
	base


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> Currently, perf has its own base of threads objects that resolve a 
> pid to a thread.
>
> This tables is built by the PERF_EVENT_COMM events.
> 
> But ftrace events may need more than this table: they sometimes 
> require to store task comms that are not profiled by perf.

What would be examples of such? Shouldnt we extend their tracing 
accordingly, so that we have all the comms we are interested in?

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