From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932721AbZJHQ37 (ORCPT ); Thu, 8 Oct 2009 12:29:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758737AbZJHQ37 (ORCPT ); Thu, 8 Oct 2009 12:29:59 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:46192 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758662AbZJHQ36 (ORCPT ); Thu, 8 Oct 2009 12:29:58 -0400 Subject: Re: [PATCH] perf tools: Improve thread comm resolution in perf sched From: Peter Zijlstra To: Frederic Weisbecker Cc: Ingo Molnar , LKML , Arnaldo Carvalho de Melo , Mike Galbraith , Paul Mackerras In-Reply-To: <1255012632-7882-1-git-send-email-fweisbec@gmail.com> References: <1255012632-7882-1-git-send-email-fweisbec@gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 08 Oct 2009 18:33:02 +0200 Message-Id: <1255019582.26976.314.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.