From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Paul Mackerras" <paulus@samba.org>
Subject: Re: [PATCH 1/1 v2] perf record: We should fork only if a program was specified to run
Date: Sat, 19 Dec 2009 23:03:27 +0100 [thread overview]
Message-ID: <1261260207.4314.4.camel@laptop> (raw)
In-Reply-To: <20091219215834.GE19708@ghostprotocols.net>
On Sat, 2009-12-19 at 19:58 -0200, Arnaldo Carvalho de Melo wrote:
> Em Sat, Dec 19, 2009 at 10:39:01PM +0100, Peter Zijlstra escreveu:
> > On Sat, 2009-12-19 at 19:22 -0200, Arnaldo Carvalho de Melo wrote:
> > > @@ -550,7 +551,7 @@ static int __cmd_record(int argc __used, const char **argv)
> > > return err;
> > > }
> > >
> > > - if (!system_wide)
> > > + if (!system_wide && profile_cpu == -1)
> > > event__synthesize_thread(pid, process_synthesized_event,
> > > session);
> >
> > Not actually sure about this bit though, since we now have
> > per-task-per-cpu things, the profile_cpu is also used to !system_wide.
>
> this actually means: if it is not system wide and not for an specific
> cpu, it must be for an specific pid.
But it can be for a specific pid and specific cpu.
> Not clear, right, you may want to profile an specific pid but only when
> it is running on an specific CPU... But at least this patch allows for
> specifiying either an specific CPU or an specific pid or systemwide.
Ah, right, not enough state to tell what we meant, fair enough.
next prev parent reply other threads:[~2009-12-19 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 21:22 [PATCH 1/1 v2] perf record: We should fork only if a program was specified to run Arnaldo Carvalho de Melo
2009-12-19 21:39 ` Peter Zijlstra
2009-12-19 21:58 ` Arnaldo Carvalho de Melo
2009-12-19 22:03 ` Peter Zijlstra [this message]
2009-12-19 21:59 ` Peter Zijlstra
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=1261260207.4314.4.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@infradead.org \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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