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] perf record: We should fork only if a program was specified to run
Date: Fri, 18 Dec 2009 22:13:38 +0100 [thread overview]
Message-ID: <1261170818.20899.657.camel@laptop> (raw)
In-Reply-To: <20091218205853.GD19708@ghostprotocols.net>
On Fri, 2009-12-18 at 18:58 -0200, Arnaldo Carvalho de Melo wrote:
> Em Fri, Dec 18, 2009 at 09:52:41PM +0100, Peter Zijlstra escreveu:
> > On Fri, 2009-12-18 at 18:42 -0200, Arnaldo Carvalho de Melo wrote:
> > > From: Arnaldo Carvalho de Melo <acme@redhat.com>
> > > @@ -422,7 +422,8 @@ static int __cmd_record(int argc __used, const char **argv)
> > > signal(SIGCHLD, sig_handler);
> > > signal(SIGINT, sig_handler);
> > >
> > > - if (pipe(child_ready_pipe) < 0 || pipe(go_pipe) < 0) {
> > > + if (target_pid == -1 && argc > 0 &&
> > > + (pipe(child_ready_pipe) < 0 || pipe(go_pipe) < 0)) {
> > > perror("failed to create pipes");
> > > exit(-1);
> > > }
> >
> > Why bother?
>
> Because we don't need it?
Well its a rare error, and the paranoid in me says bailing asap avoids
funny cases later.
> > > @@ -483,7 +484,7 @@ static int __cmd_record(int argc __used, const char **argv)
> > >
> > > atexit(atexit_header);
> > >
> > > - if (target_pid == -1) {
> > > + if (target_pid == -1 && argc > 0) {
> > > pid = fork();
> > > if (pid < 0) {
> > > perror("failed to fork");
> >
> > I'd write:
> >
> > target_pid == -1 && !system_wide
>
> Because we want this to work:
>
> [root@doppio linux-2.6-tip]# perf record -a -f sleep 2
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.243 MB perf.data (~10599 samples) ]
> [root@doppio linux-2.6-tip]#
>
> See, no hands mother! I.e. it is system wide, but just for 2 seconds,
> its clever, but I like it, and it always worked :-)
Ah, right.. yes, totally forgot about that.
> > > @@ -667,7 +668,7 @@ int cmd_record(int argc, const char **argv, const char *prefix __used)
> > >
> > > argc = parse_options(argc, argv, options, record_usage,
> > > PARSE_OPT_STOP_AT_NON_OPTION);
> > > - if (!argc && target_pid == -1 && (!system_wide || profile_cpu == -1))
> > > + if (!argc && target_pid == -1 && !system_wide)
> > > usage_with_options(record_usage, options);
> > >
> > > symbol__init();
> >
> > Right, so I was thinking -C would be enough to also start profiling..
> > clearly messed up the logic though :/
>
> Yeah, it should, meaning "profile everything on CPU N"
Right, so I tried folding that in and goofed up.
Anyway, patch looks ok, thanks!
next prev parent reply other threads:[~2009-12-18 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 20:42 [PATCH 1/1] perf record: We should fork only if a program was specified to run Arnaldo Carvalho de Melo
2009-12-18 20:52 ` Peter Zijlstra
2009-12-18 20:58 ` Arnaldo Carvalho de Melo
2009-12-18 21:13 ` Peter Zijlstra [this message]
2009-12-18 22:03 ` Ingo Molnar
2009-12-18 21:29 ` Peter Zijlstra
2009-12-20 10:31 ` Xiao Guangrong
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=1261170818.20899.657.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 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.