linux-kernel - Re: [PATCH] perf tools: Improve thread comm resolution in perf sched

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: <1255019582.26976.314.camel@twins>
Date:	Thu, 08 Oct 2009 18:33:02 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH] perf tools: Improve thread comm resolution in perf
 sched

On Thu, 2009-10-08 at 16:37 +0200, Frederic Weisbecker wrote:
> When we get sched traces that involve a task that was already
> created before opening the event, we won't have the comm event
> for it.

pid_synthesize_comm_event() should have taken care of that..

> So if we can't find the comm event for a given thread, we look at the
> traces that may contain these informations.

Sure, but it would be good to find out why the synthesize bits didn't
work as expected.
--
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/