mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, Linux-kernel@vger.kernel.org,
	kan.liang@intel.com
Subject: Re: [PATCH v3 0/6] perf report: Show branch flags/cycles in --branch-history callgraph view
Date: Wed, 26 Oct 2016 09:23:41 +0800	[thread overview]
Message-ID: <254e310b-5130-489a-916f-7118b7b11fb7@linux.intel.com> (raw)
In-Reply-To: <20161026011929.GG1075@tassilo.jf.intel.com>

If I change it to, for example: removed iterations: 20%

Is that OK?

Thanks
Jin Yao

On 10/26/2016 9:19 AM, Andi Kleen wrote:
>>                 |          |
>>                 |          |--29.93%--main div.c:39 (predicted:50.6%, cycles:1, removed loops:12954)
>
> Removed loops should be divided by the number of samples to normalize it.
>
> Also I would call it "iterations"
>
> -Andi

  reply	other threads:[~2016-10-26  1:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  1:14 Jin Yao
2016-10-26  1:14 ` [PATCH v3 1/6] perf report: Add branch flag to callchain cursor node Jin Yao
2016-10-26  1:14 ` [PATCH v3 2/6] perf report: Caculate and return the branch flag counting Jin Yao
2016-10-26  1:15 ` [PATCH v3 3/6] perf report: Create a symbol_conf flag for showing " Jin Yao
2016-10-26  1:15 ` [PATCH v3 4/6] perf report: Show branch info in callchain entry for stdio mode Jin Yao
2016-10-26  1:15 ` [PATCH v3 5/6] perf report: Show branch info in callchain entry for browser mode Jin Yao
2016-10-26  1:15 ` [PATCH v3 6/6] perf report: Display columns Predicted/Abort/Cycles in --branch-history Jin Yao
2016-10-26  1:19 ` [PATCH v3 0/6] perf report: Show branch flags/cycles in --branch-history callgraph view Andi Kleen
2016-10-26  1:23   ` Jin, Yao [this message]
2016-10-26 16:35     ` Andi Kleen

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=254e310b-5130-489a-916f-7118b7b11fb7@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@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
all inboxes | Powered by JetHome®