From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
mingo@elte.hu, "Paul Mackerras" <paulus@samba.org>,
"David S. Miller" <davem@davemloft.net>,
perfmon2-devel@lists.sf.net
Subject: Re: [RFC] perf: perf record sets inherit by default
Date: Tue, 11 May 2010 12:59:46 -0300 [thread overview]
Message-ID: <20100511155946.GH19192@ghostprotocols.net> (raw)
In-Reply-To: <AANLkTin5a3ghAUzFiQFoWNA1g9v-yFFC7uwyJEQ3zzu0@mail.gmail.com>
Em Tue, May 11, 2010 at 05:55:44PM +0200, Stephane Eranian escreveu:
> On Tue, May 11, 2010 at 5:52 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Tue, 2010-05-11 at 12:50 -0300, Arnaldo Carvalho de Melo wrote:
> >
> >> Nope, see above.
> >
> > Ah, -p/-t might make sense to default to inherit off indeed.
> >
> >
> I would rather think that -p would inherit but not -t.
> If I attach to a multi-threaded app with -p, I'd like all threads monitored.
> But if I use -t to point to a specific thread within a process, then most
> likely I care only about that thread.
Ok, so fine tuning of the inherit flag is needed, i.e. we need both a
--inherit and a --no-inherit, well, good thing is that I think that the
option parsing stuff we, erm, inherited from git does just that, lemme
check how it works in this case more precisely...
- Arnaldo
next prev parent reply other threads:[~2010-05-11 16:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 14:04 [RFC] perf: perf record sets inherit by default Stephane Eranian
2010-05-11 14:48 ` Peter Zijlstra
2010-05-17 14:25 ` Stephane Eranian
2010-05-17 16:48 ` Peter Zijlstra
2010-05-18 17:16 ` [tip:perf/core] perf: Optimize buffer placement by allocating buffers NUMA aware tip-bot for Peter Zijlstra
2010-05-11 15:00 ` [RFC] perf: perf record sets inherit by default Arnaldo Carvalho de Melo
2010-05-11 15:13 ` Peter Zijlstra
2010-05-11 15:17 ` Stephane Eranian
2010-05-11 15:50 ` Arnaldo Carvalho de Melo
2010-05-11 15:52 ` Peter Zijlstra
2010-05-11 15:55 ` Stephane Eranian
2010-05-11 15:59 ` Arnaldo Carvalho de Melo [this message]
2010-05-11 15:56 ` Arnaldo Carvalho de Melo
2010-05-11 16:01 ` Stephane Eranian
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=20100511155946.GH19192@ghostprotocols.net \
--to=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=perfmon2-devel@lists.sf.net \
--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