From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf tools: Synthesize GROUP_DESC feature in pipe mode
Date: Thu, 19 Jul 2018 11:28:54 -0300 [thread overview]
Message-ID: <20180719142854.GB4070@kernel.org> (raw)
In-Reply-To: <CABPqkBRObtG6ODH4N9psNKsknGYAJxgEKXGU3h84qyUvOB5iWw@mail.gmail.com>
Em Thu, Jul 12, 2018 at 11:18:05PM -0700, Stephane Eranian escreveu:
> Hi Jiri,
> On Thu, Jul 12, 2018 at 9:49 AM Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > On Thu, Jul 12, 2018 at 09:34:45AM -0700, Stephane Eranian wrote:
> > > Hi Jiri,
> > > On Thu, Jul 12, 2018 at 6:52 AM Jiri Olsa <jolsa@kernel.org> wrote:
> > > >
> > > > Stephan reported, that pipe mode does not carry the group
> > > > information and thus the piped report won't display the
> > > > grouped output for following command:
> > > >
> > > Thanks for fixing this quickly.
> >
> > could I have your tested/acked by?
> Acked-by: Stephane Eranian <eranian@google.com>
Applying, Stephane, please consider providing a
Tested-by: Stephane Eranian <eranian@google.com>
When you actually applied the patch, built and tested, so that we can
have this reflect better what actually was done.
Acked-by is more like hey, I briefly looked at the patch, looks good.
I.e. no actual test was performed, which I think wasn't the case here,
but will keep what you provided (Acked-by) as I'm not sure you actually
tested.
Thanks,
- Arnaldo
> > > I think we should have more testing on the pipe mode, in general.
> >
> > yea, we should
> >
> > jirka
> >
> > >
> > > > # perf record -e '{cycles,instructions,branches}' -a sleep 4 | perf report
> > > >
> > > > It has no idea about the group setup, so it will display
> > > > events separately:
> > > >
> > > > # Overhead Command Shared Object ...
> > > > # ........ ............... .......................
> > > > #
> > > > 6.71% swapper [kernel.kallsyms]
> > > > 2.28% offlineimap libpython2.7.so.1.0
> > > > 0.78% perf [kernel.kallsyms]
> > > > ...
> > > >
> > > > Fixing GROUP_DESC feature record to be synthesized in pipe mode,
> > > > so the report output is grouped if there's group defined in record:
> > > >
> > > > # Overhead Command Shared ...
> > > > # ........................ ............... .......
> > > > #
> > > > 7.57% 0.16% 0.30% swapper [kernel
> > > > 1.87% 3.15% 2.46% offlineimap libpyth
> > > > 1.33% 0.00% 0.00% perf [kernel
> > > > ...
> > > >
> > > > Cc: David Carrillo-Cisneros <davidcc@google.com>
> > > > Reported-by: Stephane Eranian <eranian@google.com>
> > > > Link: http://lkml.kernel.org/n/tip-ybqyh8ac4g173iy3xt4pxnlo@git.kernel.org
> > > > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > > > ---
> > > > tools/perf/util/header.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > > > index 59fcc790c865..af9aaf28f976 100644
> > > > --- a/tools/perf/util/header.c
> > > > +++ b/tools/perf/util/header.c
> > > > @@ -2587,7 +2587,7 @@ static const struct feature_ops feat_ops[HEADER_LAST_FEATURE] = {
> > > > FEAT_OPR(NUMA_TOPOLOGY, numa_topology, true),
> > > > FEAT_OPN(BRANCH_STACK, branch_stack, false),
> > > > FEAT_OPR(PMU_MAPPINGS, pmu_mappings, false),
> > > > - FEAT_OPN(GROUP_DESC, group_desc, false),
> > > > + FEAT_OPR(GROUP_DESC, group_desc, false),
> > > > FEAT_OPN(AUXTRACE, auxtrace, false),
> > > > FEAT_OPN(STAT, stat, false),
> > > > FEAT_OPN(CACHE, cache, true),
> > > > --
> > > > 2.17.1
> > > >
next prev parent reply other threads:[~2018-07-19 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 13:52 [PATCH] perf tools: Synthesize GROUP_DESC feature in pipe mode Jiri Olsa
2018-07-12 16:34 ` Stephane Eranian
2018-07-12 16:49 ` Jiri Olsa
2018-07-13 6:18 ` Stephane Eranian
2018-07-19 14:28 ` Arnaldo Carvalho de Melo [this message]
2018-07-19 15:17 ` Stephane Eranian
2018-07-19 15:56 ` Arnaldo Carvalho de Melo
2018-07-25 20:49 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=20180719142854.GB4070@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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;
as well as URLs for NNTP newsgroup(s).