From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] perf: Do not send exit event twice
Date: Thu, 26 Nov 2015 20:37:59 +0100 [thread overview]
Message-ID: <20151126193759.GA25474@krava.brq.redhat.com> (raw)
In-Reply-To: <20151104160348.GO17308@twins.programming.kicks-ass.net>
On Wed, Nov 04, 2015 at 05:03:48PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 04, 2015 at 04:53:58PM +0100, Jiri Olsa wrote:
> > On Wed, Nov 04, 2015 at 04:46:04PM +0100, Peter Zijlstra wrote:
> > > On Wed, Nov 04, 2015 at 04:00:05PM +0100, Jiri Olsa wrote:
> > > > This does not affect other auxiliary events, as they don't
> > > > use task_ctx at all.
> > >
> > > FORK does..
> >
> > hum, I don't see that, it passes NULL as task_ctx:
> >
> > void perf_event_fork(struct task_struct *task)
> > {
> > perf_event_task(task, NULL, 1);
> > }
>
> Bah, I'll go sit in a corner, or rather, have a nap. Clearly I cannot
> even read anymore.
heya,
can't see this one being in any queue so far.. could you please
take it together with:
perf x86 intel: Fix INTEL_FLAGS_UEVENT_CONSTRAINT_DATALA_NA macro
thanks,
jirka
next prev parent reply other threads:[~2015-11-26 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 15:00 Jiri Olsa
2015-11-04 15:46 ` Peter Zijlstra
2015-11-04 15:53 ` Jiri Olsa
2015-11-04 16:03 ` Peter Zijlstra
2015-11-26 19:37 ` Jiri Olsa [this message]
2015-12-04 11:51 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-12-06 13:17 ` tip-bot for Jiri Olsa
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=20151126193759.GA25474@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®