From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] perf tools: Improve thread comm resolution in perf sched
Date: Thu, 08 Oct 2009 18:33:02 +0200 [thread overview]
Message-ID: <1255019582.26976.314.camel@twins> (raw)
In-Reply-To: <1255012632-7882-1-git-send-email-fweisbec@gmail.com>
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.
next prev parent reply other threads:[~2009-10-08 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 14:37 [PATCH] perf tools: Improve thread comm resolution in perf sched Frederic Weisbecker
2009-10-08 15:12 ` [tip:perf/core] " tip-bot for Frederic Weisbecker
2009-10-08 16:33 ` Peter Zijlstra [this message]
2009-10-08 17:18 ` [PATCH] " Frederic Weisbecker
2009-10-08 18:34 ` Frederic Weisbecker
2009-10-08 18:48 ` [PATCH] perf tools: Fix " Frederic Weisbecker
2009-10-08 19:04 ` Frederic Weisbecker
2009-10-08 19:13 ` [tip:perf/core] " tip-bot for Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1255019582.26976.314.camel@twins \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.