From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Milian Wolff <mail@milianw.de>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [PATCH 001/001] perf: let trace write to stderr by default
Date: Wed, 5 Aug 2015 16:50:06 -0300 [thread overview]
Message-ID: <20150805195006.GB32553@kernel.org> (raw)
In-Reply-To: <3494762.Lck5LtIdUB@milian-kdab2>
Em Tue, Aug 04, 2015 at 07:14:22PM +0200, Milian Wolff escreveu:
> On Tuesday 04 August 2015 13:50:14 Arnaldo Carvalho de Melo wrote:
> > Le 4 août 2015 1:46 PM, "Milian Wolff" <mail@milianw.de> a écrit :
> > > See attached trivial patch which brings trace a bit closer to strace.
> > >
> > > I've never published a patch to the Kernel yet, I hope it's OK as-is. I
> >
> > can
> >
> > > amend it at will if you have any requests to the style
> >
> > Start by not using attachments :-)
>
> :)
Second step, read Documentation/email-clients.txt, you are using Kmail
and it is mangling the patches, I'll apply the patch by hand this time.
- Arnaldo
> >From 188476d65bab17ad99f5bdf65294160ef2d5f49b Mon Sep 17 00:00:00 2001
> From: Milian Wolff <milian.wolff@kdab.com>
> Date: Tue, 4 Aug 2015 18:30:52 +0200
> Subject: [PATCH] perf: let trace write to stderr by default
>
> Without this patch, it is cumbersome to read the trace output
> but ignoring the normal, potentially verbose, output of the debuggee.
> One common example is doing something like the following:
>
> perf trace -s find /tmp > /dev/null
>
> Without this patch, the trace summary will be lost. Now, it will
> still be printed at the end. This behavior is also applied by strace.
> ---
> tools/perf/builtin-trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index 39ad4d0..d183d88 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -2778,7 +2778,7 @@ int cmd_trace(int argc, const char **argv, const char
> *prefix __maybe_unused)
> .mmap_pages = UINT_MAX,
> .proc_map_timeout = 500,
> },
> - .output = stdout,
> + .output = stderr,
> .show_comm = true,
> .trace_syscalls = true,
> };
> --
> 2.5.0
>
> --
> Milian Wolff
> mail@milianw.de
> http://milianw.de
next prev parent reply other threads:[~2015-08-05 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 16:39 [PATCH 001/001] perf: let trace write to stderr by default Milian Wolff
[not found] ` <CA+JHD92yJxikRUQ57Hb+C4pZ12gcFAn6paWenbAY5FbwtgQFDg@mail.gmail.com>
2015-08-04 17:14 ` Milian Wolff
2015-08-05 19:50 ` Arnaldo Carvalho de Melo [this message]
2015-08-05 19:52 ` 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=20150805195006.GB32553@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mail@milianw.de \
/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;
as well as URLs for NNTP newsgroup(s).