From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, namhyung@kernel.org, eranian@google.com,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 05/11] perf, tools, report: Add processing for cycle histograms
Date: Mon, 1 Jun 2015 16:10:46 +0200 [thread overview]
Message-ID: <20150601141046.GA14379@krava.redhat.com> (raw)
In-Reply-To: <1432749114-904-6-git-send-email-andi@firstfloor.org>
On Wed, May 27, 2015 at 10:51:48AM -0700, Andi Kleen wrote:
SNIP
> +void hist__account_cycles(struct branch_stack *bs, struct addr_location *al,
> + struct perf_sample *sample, bool nonany_branch_mode)
> +{
> + struct branch_info *bi;
> +
> + /* If we have branch cycles always annotate them. */
> + if (bs && bs->nr && bs->entries[0].flags.cycles) {
> + int i;
> +
> + bi = sample__resolve_bstack(sample, al);
> + if (bi) {
> + struct addr_map_symbol *prev = NULL;
> +
> + /*
> + * Ignore errors, still want to process the
> + * other entries.
> + *
> + * For non standard branch modes always
> + * force no IPC (prev == NULL)
> + *
> + * Note that perf stores branches reversed from
> + * program order!
> + */
> + for (i = bs->nr - 1; i >= 0; i--) {
> + addr_map_symbol__account_cycles(&bi[i].from,
> + nonany_branch_mode ? NULL : prev,
> + bi[i].flags.cycles);
it's only ERANGE you want to ignore here
jirka
next prev parent reply other threads:[~2015-06-01 14:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 17:51 Cycles annotation support for perf tools v2 Andi Kleen
2015-05-27 17:51 ` [PATCH 01/11] perf, tools: Add tools support for cycles, weight branch_info field Andi Kleen
2015-06-01 14:16 ` Jiri Olsa
2015-05-27 17:51 ` [PATCH 02/11] perf, tools, report: Add flag for non ANY branch mode Andi Kleen
2015-06-01 14:16 ` Jiri Olsa
2015-05-27 17:51 ` [PATCH 03/11] perf, tools: Add symbol__get_annotation Andi Kleen
2015-05-28 9:32 ` [tip:perf/core] perf annotation: " tip-bot for Andi Kleen
2015-06-01 14:17 ` [PATCH 03/11] perf, tools: " Jiri Olsa
2015-05-27 17:51 ` [PATCH 04/11] perf, tools, report: Add infrastructure for a cycles histogram Andi Kleen
2015-06-01 14:19 ` Jiri Olsa
2015-05-27 17:51 ` [PATCH 05/11] perf, tools, report: Add processing for cycle histograms Andi Kleen
2015-06-01 14:10 ` Jiri Olsa [this message]
2015-05-27 17:51 ` [PATCH 06/11] perf, tools: Compute IPC and basic block cycles for annotate Andi Kleen
2015-05-27 17:51 ` [PATCH 07/11] perf, tools, annotate: Finally display IPC and cycle accounting Andi Kleen
2015-05-27 17:51 ` [PATCH 08/11] perf, tools, report: Move branch option parsing to own file Andi Kleen
2015-05-28 9:32 ` [tip:perf/core] perf tools: " tip-bot for Andi Kleen
2015-06-01 14:20 ` [PATCH 08/11] perf, tools, report: " Jiri Olsa
2015-05-27 17:51 ` [PATCH 09/11] perf, tools, top: Add branch annotation code to top Andi Kleen
2015-05-27 17:51 ` [PATCH 10/11] perf, tools, report: Display cycles in branch sort mode Andi Kleen
2015-05-27 17:51 ` [PATCH 11/11] test patch: Add fake branch cycles to input data in report/top Andi Kleen
2015-06-01 14:21 ` Cycles annotation support for perf tools v2 Jiri Olsa
2015-06-01 14:43 ` Arnaldo Carvalho de Melo
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=20150601141046.GA14379@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox