All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v5 7/7] perf report: Sort by sampled cycles percent per block for tui
Date: Mon, 4 Nov 2019 14:53:33 +0100	[thread overview]
Message-ID: <20191104135333.GH8251@krava> (raw)
In-Reply-To: <2bbc0a0d-639b-7a88-71d5-6c022f46134c@linux.intel.com>

On Fri, Nov 01, 2019 at 10:07:33PM +0800, Jin, Yao wrote:
> 
> 
> On 11/1/2019 4:34 PM, Jiri Olsa wrote:
> > On Wed, Oct 30, 2019 at 02:04:30PM +0800, Jin Yao wrote:
> > 
> > SNIP
> > 
> > > diff --git a/tools/perf/ui/browsers/hists.h b/tools/perf/ui/browsers/hists.h
> > > index 91d3e18b50aa..078f2f2c7abd 100644
> > > --- a/tools/perf/ui/browsers/hists.h
> > > +++ b/tools/perf/ui/browsers/hists.h
> > > @@ -5,6 +5,7 @@
> > >   #include "ui/browser.h"
> > >   struct annotation_options;
> > > +struct evsel;
> > >   struct hist_browser {
> > >   	struct ui_browser   b;
> > > @@ -15,6 +16,7 @@ struct hist_browser {
> > >   	struct pstack	    *pstack;
> > >   	struct perf_env	    *env;
> > >   	struct annotation_options *annotation_opts;
> > > +	struct evsel	    *block_evsel;
> > 
> > you should be able to get the evsel from hists_to_evsel function
> > 
> > jirka
> > 
> 
> Maybe we can't. The hists in hist_browser is set to block_hists (not the
> hists for evsel).
> 
> See block_hists_tui_browse,
> 
> int block_hists_tui_browse(struct block_hist *bh, struct evsel *evsel,
>                           float min_percent)
> {
>        struct hists *hists = &bh->block_hists;
>        struct hist_browser *browser;
>        ......
>        browser = hist_browser__new(hists);
>        ......
> }
> 
> So I have to pass the evsel in.

I see, ok

jirka


      reply	other threads:[~2019-11-04 13:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30  6:04 [PATCH v5 0/7] perf report: Support sorting all blocks by cycles Jin Yao
2019-10-30  6:04 ` [PATCH v5 1/7] perf diff: Don't use hack to skip column length calculation Jin Yao
2019-10-30  6:04 ` [PATCH v5 2/7] perf util: Cleanup and refactor block info functions Jin Yao
2019-10-30  6:04 ` [PATCH v5 3/7] perf util: Count the total cycles of all samples Jin Yao
2019-10-30  6:04 ` [PATCH v5 4/7] perf util: Support block formats with compare/sort/display Jin Yao
2019-10-30  6:04 ` [PATCH v5 5/7] perf report: Sort by sampled cycles percent per block for stdio Jin Yao
2019-11-04 14:04   ` Jiri Olsa
2019-11-05  3:41     ` Jin, Yao
2019-10-30  6:04 ` [PATCH v5 6/7] perf report: Support --percent-limit for --total-cycles Jin Yao
2019-10-30  6:04 ` [PATCH v5 7/7] perf report: Sort by sampled cycles percent per block for tui Jin Yao
2019-11-01  8:34   ` Jiri Olsa
2019-11-01 13:05     ` Jin, Yao
2019-11-01  8:34   ` Jiri Olsa
2019-11-01 14:07     ` Jin, Yao
2019-11-04 13:53       ` Jiri Olsa [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=20191104135333.GH8251@krava \
    --to=jolsa@redhat.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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.