public inbox for linux-kernel@vger.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: Fri, 1 Nov 2019 09:34:26 +0100	[thread overview]
Message-ID: <20191101083426.GC2172@krava> (raw)
In-Reply-To: <20191030060430.23558-8-yao.jin@linux.intel.com>

On Wed, Oct 30, 2019 at 02:04:30PM +0800, Jin Yao wrote:

SNIP

> +
>  static int perf_evlist__tty_browse_hists(struct evlist *evlist,
>  					 struct report *rep,
>  					 const char *help)
> @@ -605,6 +624,11 @@ static int report__browse_hists(struct report *rep)
>  
>  	switch (use_browser) {
>  	case 1:
> +		if (rep->total_cycles_mode) {
> +			ret = perf_evlist__tui_block_hists_browse(evlist, rep);
> +			break;
> +		}

does this have sense only for cycles event? what if I do:
  # perf record -b -e cycles,cache-misses

jirka

> +
>  		ret = perf_evlist__tui_browse_hists(evlist, help, NULL,
>  						    rep->min_percent,
>  						    &session->header.env,
> @@ -1408,12 +1432,8 @@ int cmd_report(int argc, const char **argv)
>  	if (report.total_cycles_mode) {
>  		if (sort__mode != SORT_MODE__BRANCH)
>  			report.total_cycles_mode = false;
> -		else if (!report.use_stdio) {
> -			pr_err("Error: --total-cycles can be only used together with --stdio\n");
> -			goto error;
> -		} else {
> +		else
>  			sort_order = "sym";
> -		}
>  	}
>  
>  	if (strcmp(input_name, "-") != 0)

SNIP


  reply	other threads:[~2019-11-01  8:34 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 [this message]
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

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=20191101083426.GC2172@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox