public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Michael Petlan <mpetlan@redhat.com>,
	Ian Rogers <irogers@google.com>, Paul Khuong <pvk@pvk.ca>
Subject: Re: [PATCH 0/5] perf tools: Pipe fixes
Date: Thu, 7 May 2020 12:49:17 -0300	[thread overview]
Message-ID: <20200507154917.GB32641@kernel.org> (raw)
In-Reply-To: <20200507095024.2789147-1-jolsa@kernel.org>

Em Thu, May 07, 2020 at 11:50:19AM +0200, Jiri Olsa escreveu:
> hi,
> sending changes that allows callchain detection in pipe mode,
> fixing followign use case:
> 
>   # perf record --no-buffering --call-graph dwarf -e sdt_rtld:init_start -a -o - | perf --no-pager script -i -
> 
> plus change that allows to read pipe data from file:
> 
>   # perf record -o - sleep 1 > /tmp/perf.pipe.data
>   # perf report -i /tmp/perf.pipe.data
> 
> plus unrelated build fix.
> 
> Also reachable in here:
>   git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
>   perf/pipe

Thanks a lot, all tested, great improvements for pipe mode!

- Arnaldo
 
> thanks,
> jirka
> 
> 
> ---
> Jiri Olsa (5):
>       perf tools: Do not display extra info when there is nothing to build
>       perf tools: Do not seek in pipe fd during tracing data processing
>       perf session: Try to read pipe data from file
>       perf tools: Setup callchain properly in pipe mode
>       perf script: Enable IP fields for callchains
> 
>  tools/perf/Makefile.perf    |  8 +++++---
>  tools/perf/builtin-report.c | 33 ++++++++++++++++++++++-----------
>  tools/perf/builtin-script.c | 23 +++++++++++++++++++----
>  tools/perf/util/callchain.c | 14 ++++++++++++++
>  tools/perf/util/callchain.h |  1 +
>  tools/perf/util/header.c    | 34 ++++++++++++++++++++++++++--------
>  tools/perf/util/session.c   |  9 +++++++--
>  7 files changed, 94 insertions(+), 28 deletions(-)
> 

-- 

- Arnaldo

      parent reply	other threads:[~2020-05-07 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  9:50 [PATCH 0/5] perf tools: Pipe fixes Jiri Olsa
2020-05-07  9:50 ` [PATCH 1/5] perf tools: Do not display extra info when there is nothing to build Jiri Olsa
2020-05-07 14:52   ` Arnaldo Carvalho de Melo
2020-05-07  9:50 ` [PATCH 2/5] perf tools: Do not seek in pipe fd during tracing data processing Jiri Olsa
2020-05-07  9:50 ` [PATCH 3/5] perf session: Try to read pipe data from file Jiri Olsa
2020-05-07  9:50 ` [PATCH 4/5] perf tools: Setup callchain properly in pipe mode Jiri Olsa
2020-05-07  9:50 ` [PATCH 5/5] perf script: Enable IP fields for callchains Jiri Olsa
2020-05-07 15:49 ` Arnaldo Carvalho de Melo [this message]

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=20200507154917.GB32641@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=pvk@pvk.ca \
    /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