All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] perf report TUI: Remove needless 'dummy' event from menu
Date: Mon, 6 Jul 2020 08:54:52 -0300	[thread overview]
Message-ID: <20200706115452.GA2772@redhat.com> (raw)
In-Reply-To: <CAM9d7cgGcpnX+cSY0UvYjRkG9PF8X3Yyf_AOy+nGxbPjtjDvxw@mail.gmail.com>

Em Fri, Jul 03, 2020 at 10:44:28PM +0900, Namhyung Kim escreveu:
> Hi Arnaldo,
> 
> On Fri, Jul 3, 2020 at 9:34 PM Arnaldo Carvalho de Melo <acme@redhat.com> wrote:
> >
> > Please Ack,
> >
> > - Arnaldo
> >
> > ----
> >
> > Fixing the common case of:
> >
> >   perf record
> >   perf report
> >
> > And getting just the cycles events.
> >
> > We now have a 'dummy' event to get perf metadata events that take place
> > while we synthesize metadata records for pre-existing processes by
> > traversing procfs, so we always have this extra 'dummy' evsel, but we
> > don't have to offer it as there will be no samples on it, remove this
> > distraction.
> >
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Ian Rogers <irogers@google.com>
> > Cc: Jiri Olsa <jolsa@kernel.org>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> > ---
> >  tools/perf/ui/browsers/hists.c | 19 ++++++++++++++++++-
> >  1 file changed, 18 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/ui/browsers/hists.c b/tools/perf/ui/browsers/hists.c
> > index 4cd556c1276f..be9c4c0549bc 100644
> > --- a/tools/perf/ui/browsers/hists.c
> > +++ b/tools/perf/ui/browsers/hists.c
> > @@ -3603,6 +3603,23 @@ static int __perf_evlist__tui_browse_hists(struct evlist *evlist,
> >                                     hbt, warn_lost_event);
> >  }
> >
> > +static bool perf_evlist__single_entry(struct evlist *evlist)
> > +{
> > +       int nr_entries = evlist->core.nr_entries;
> > +
> > +       if (nr_entries == 1)
> > +              return true;
> > +
> > +       if (nr_entries == 2) {
> > +               struct evsel *last = evlist__last(evlist);
> > +
> > +               if (evsel__is_dummy_event(last))
> > +                       return true;
> > +       }
> > +
> > +       return false;
> > +}
> > +
> >  int perf_evlist__tui_browse_hists(struct evlist *evlist, const char *help,
> >                                   struct hist_browser_timer *hbt,
> >                                   float min_pcnt,
> > @@ -3613,7 +3630,7 @@ int perf_evlist__tui_browse_hists(struct evlist *evlist, const char *help,
> >         int nr_entries = evlist->core.nr_entries;
> >
> >  single_entry:
> > -       if (nr_entries == 1) {
> > +       if (perf_evlist__single_entry(evlist)) {
> 
> But I think it cannot cover the event group case below..

Right, we can fix that later, I think, my worry at this point was that
the simplest case, which is:

   # perf record
   ^C
   # perf report

Would get that annoyance :-)

- Arnaldo
 
> Thanks
> Namhyung
> 
> 
> >                 struct evsel *first = evlist__first(evlist);
> >
> >                 return perf_evsel__hists_browse(first, nr_entries, help,
> > --
> > 2.21.3
> >


  reply	other threads:[~2020-07-06 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200703123431.GG1320@kernel.org>
2020-07-03 13:44 ` [PATCH 1/1] perf report TUI: Remove needless 'dummy' event from menu Namhyung Kim
2020-07-06 11:54   ` Arnaldo Carvalho de Melo [this message]
2020-07-06 15:12     ` Namhyung Kim

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=20200706115452.GA2772@redhat.com \
    --to=acme@redhat.com \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.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 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.