public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Mackerras <paulus@samba.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH] perf_events: Fix FORK events
Date: Mon, 8 Feb 2010 08:44:38 +0100	[thread overview]
Message-ID: <20100208074438.GC24721@elte.hu> (raw)
In-Reply-To: <1265384243.30057.42.camel@laptop>


* Peter Zijlstra <peterz@infradead.org> wrote:

> Hi,
> 
> While looking into a problem reported by Pekka, I noticed that I wasn't
> receiving any FORK events for a workload that did fork (see attachment).

ah yes, my old testcase for forks.

> After making the below change, stuff started working again, thing is, I'm 
> not sure why.

In case it matters: that workload of 4x fork (and the whole fork events 
mechanism) was always very sensitive to the precise timing of when a child 
and a parent does what, in the final dance of wait(), do_exit(), 
release_task(), etc. when a task exits. Especially on SMP systems.

> The main change is sending the FORK event to the parent instead of the 
> child thread, however perf_event_fork() is at the end of copy_process(), 
> which is after perf_event_init_task() which inherits all the counters, so 
> it should all have worked as it was.
> 
> We could of course just slam the commit in and not worry about it, but
> that just doesn't feel right.

Would be nice to figure it out ...

	Ingo

  reply	other threads:[~2010-02-08  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 15:37 [RFC][PATCH] perf_events: Fix FORK events Peter Zijlstra
2010-02-08  7:44 ` Ingo Molnar [this message]
2010-02-08 15:57   ` Peter Zijlstra
2010-02-13 13:53     ` Arnaldo Carvalho de Melo

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=20100208074438.GC24721@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@ghostprotocols.net \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox