All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: mingo@elte.hu, Arnaldo Carvalho de Melo <acme@redhat.com>,
	paulus@samba.org, linux-kernel@vger.kernel.org,
	Anton Blanchard <anton@samba.org>,
	Arjan van de Ven <arjan@infradead.org>
Subject: [PATCH] perf_counter: Report the cloning task as parent on perf_counter_fork()
Date: Thu, 13 Aug 2009 16:14:42 +0200	[thread overview]
Message-ID: <1250172882.5241.62.camel@twins> (raw)
In-Reply-To: <1250155708.6052.2.camel@penberg-laptop>

A bug in (9f498cc: perf_counter: Full task tracing) makes profiling
multi-threaded apps it go belly up.

[ output as: (PID:TID):(PPID:PTID) ]

# ./perf report -D | grep FORK
0x4b0 [0x18]: PERF_EVENT_FORK: (3237:3237):(3236:3236)
0xa10 [0x18]: PERF_EVENT_FORK: (3237:3238):(3236:3236)
0xa70 [0x18]: PERF_EVENT_FORK: (3237:3239):(3236:3236)
0xad0 [0x18]: PERF_EVENT_FORK: (3237:3240):(3236:3236)
0xb18 [0x18]: PERF_EVENT_FORK: (3237:3241):(3236:3236)

Shows us that the test (27d028d perf report: Update for the new
FORK/EXIT events) in builtin-report.c:

        /*
         * A thread clone will have the same PID for both
         * parent and child.
         */
        if (thread == parent)
                return 0;

Will clearly fail.

The problem is that perf_counter_fork() reports the actual parent,
instead of the cloning thread.

Fixing that (with the below patch), yields:

# ./perf report -D | grep FORK
0x4c8 [0x18]: PERF_EVENT_FORK: (1590:1590):(1589:1589)
0xbd8 [0x18]: PERF_EVENT_FORK: (1590:1591):(1590:1590)
0xc80 [0x18]: PERF_EVENT_FORK: (1590:1592):(1590:1590)
0x3338 [0x18]: PERF_EVENT_FORK: (1590:1593):(1590:1590)
0x66b0 [0x18]: PERF_EVENT_FORK: (1590:1594):(1590:1590)

Which both makes more sense and doesn't confuse perf report anymore.

Reported-by: Pekka Enberg <penberg@cs.helsinki.fi>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
---
 perf_counter.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-2.6/kernel/perf_counter.c
===================================================================
--- linux-2.6.orig/kernel/perf_counter.c
+++ linux-2.6/kernel/perf_counter.c
@@ -3024,10 +3024,10 @@ static void perf_counter_task_output(str
 		return;
 
 	task_event->event.pid = perf_counter_pid(counter, task);
-	task_event->event.ppid = perf_counter_pid(counter, task->real_parent);
+	task_event->event.ppid = perf_counter_pid(counter, current);
 
 	task_event->event.tid = perf_counter_tid(counter, task);
-	task_event->event.ptid = perf_counter_tid(counter, task->real_parent);
+	task_event->event.ptid = perf_counter_tid(counter, current);
 
 	perf_output_put(&handle, task_event->event);
 	perf_output_end(&handle);


  parent reply	other threads:[~2009-08-13 14:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13  9:28 [PROBLEM] perf report is broken in latest linus git Pekka Enberg
2009-08-13  9:36 ` Ingo Molnar
2009-08-13  9:47   ` Pekka Enberg
2009-08-13 11:33     ` Peter Zijlstra
2009-08-13 12:02       ` Pekka Enberg
2009-08-13 12:24         ` Pekka Enberg
2009-08-13 14:14 ` Peter Zijlstra [this message]
2009-08-13 14:18   ` [tip:perfcounters/urgent] perf_counter: Report the cloning task as parent on perf_counter_fork() tip-bot for Peter Zijlstra
2009-08-15  8:58   ` [PATCH] " Pekka Enberg
2009-08-15  9:13     ` Ingo Molnar

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=1250172882.5241.62.camel@twins \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=anton@samba.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=penberg@cs.helsinki.fi \
    /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.