From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf stat: Do not show stats if workload fails
Date: Thu, 26 Dec 2013 11:26:34 -0300 [thread overview]
Message-ID: <20131226142634.GF30980@ghostprotocols.net> (raw)
In-Reply-To: <52BC3AA9.1020404@gmail.com>
Em Thu, Dec 26, 2013 at 09:18:17AM -0500, David Ahern escreveu:
> On 12/26/13, 9:15 AM, Arnaldo Carvalho de Melo wrote:
> >Right, but I can't apply that patch, as it makes 'perf stat
> >whatever-workload' to fail, as I realized when doing a demo to someone
> >interested in using perf ;-\
> >
> >So for now I'm not applying that one.
>
> right, so you want one with < 0 check or wait for something else? I
> was not expecting to find it in your perf/core branch, yet there it
> is.
I'll remove it from there, but try it, IIRC there will be some other
problem :-\
I'd have to reread the messages I sent, but from what I recall the
return from perf_evlist__start_workload() will _always_ be valid, i.e.
what you're testing there is just if the parent wrote a byte to a pipe
to signal the waiting child to call exec, and that _will_ work, the
exec()? perhaps not, you'd have to setup the signal error reporting
mechanism, etc.
Perhaps this should be somehow done by perf_evlist__start_workload, so
that what it reports is the result of the exec in the child, and not
merely if it managed to tell it to try to exec...
- Arnaldo
> >
> >Ah, at this point elves are everywhere, dammit! ;-)
>
> An elf put it there?
Right, dwarves may be involved, didn't had the time to figure that
out...
> David
next prev parent reply other threads:[~2013-12-26 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 5:52 [PATCH] perf stat: Do not show stats if workload fails David Ahern
2013-12-20 7:57 ` Ingo Molnar
2013-12-23 19:37 ` Arnaldo Carvalho de Melo
2013-12-24 0:29 ` David Ahern
2013-12-24 12:53 ` Arnaldo Carvalho de Melo
2013-12-24 13:30 ` Arnaldo Carvalho de Melo
2013-12-26 14:11 ` David Ahern
2013-12-26 14:15 ` Arnaldo Carvalho de Melo
2013-12-26 14:18 ` David Ahern
2013-12-26 14:26 ` Arnaldo Carvalho de Melo [this message]
2013-12-26 14:55 ` Arnaldo Carvalho de Melo
2014-01-02 14:44 ` 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=20131226142634.GF30980@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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.