From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf script: Simplify auxiliary event printing functions
Date: Mon, 6 Apr 2020 10:39:31 -0300 [thread overview]
Message-ID: <20200406133931.GB29826@kernel.org> (raw)
In-Reply-To: <20200403104802.GJ2784502@krava>
Em Fri, Apr 03, 2020 at 12:48:02PM +0200, Jiri Olsa escreveu:
> On Thu, Apr 02, 2020 at 05:15:48PM +0300, Adrian Hunter wrote:
> > This simplifies the print functions for the following perf script
> > options:
> >
> > --show-task-events
> > --show-namespace-events
> > --show-cgroup-events
> > --show-mmap-events
> > --show-switch-events
> > --show-lost-events
> > --show-bpf-events
> >
> > Example:
> > # perf record --switch-events -a -e cycles -c 10000 sleep 1
> > Before:
> > # perf script --show-task-events --show-namespace-events --show-cgroup-events --show-mmap-events --show-switch-events --show-lost-events --show-bpf-events >out-before.txt
> > After:
> > # perf script --show-task-events --show-namespace-events --show-cgroup-events --show-mmap-events --show-switch-events --show-lost-events --show-bpf-events >out-after.txt
> > # diff -s out-before.txt out-after.txt
> > Files out-before.txt and out-after.tx are identical
> >
> > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2020-04-06 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 14:15 [PATCH] perf script: Simplify auxiliary event printing functions Adrian Hunter
2020-04-03 10:01 ` Jiri Olsa
2020-04-03 10:31 ` Adrian Hunter
2020-04-03 10:48 ` Jiri Olsa
2020-04-06 13:39 ` Arnaldo Carvalho de Melo [this message]
2020-04-22 12:17 ` [tip: perf/core] " tip-bot2 for Adrian Hunter
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=20200406133931.GB29826@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox