From: Namhyung Kim <namhyung@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: kan.liang@intel.com, acme@kernel.org, a.p.zijlstra@chello.nl,
eranian@google.com, linux-kernel@vger.kernel.org,
mingo@redhat.com, paulus@samba.org, ak@linux.intel.com
Subject: Re: [PATCH V3 3/3] perf tools: Construct LBR call chain
Date: Tue, 18 Nov 2014 15:14:12 +0900 [thread overview]
Message-ID: <87h9xxqbm3.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20141117155553.GC21532@krava.brq.redhat.com> (Jiri Olsa's message of "Mon, 17 Nov 2014 16:55:53 +0100")
On Mon, 17 Nov 2014 16:55:53 +0100, Jiri Olsa wrote:
> On Fri, Nov 14, 2014 at 08:44:12AM -0500, kan.liang@intel.com wrote:
>
> SNIP
>
>> + if (lbr) {
>> + for (i = 0; i < chain_nr; i++) {
>> + if (chain->ips[i] == PERF_CONTEXT_USER)
>> + break;
>> + }
>> +
>> + /* LBR only affects the user callchain */
>> + if (i != chain_nr) {
>> + struct branch_stack *lbr_stack = sample->branch_stack;
>> + int lbr_nr = lbr_stack->nr;
>> + /*
>> + * LBR callstack can only get user call chain.
>> + * The mix_chain_nr is kernel call chain
>> + * number plus LBR user call chain number.
>> + * i is kernel call chain number,
>> + * 1 is PERF_CONTEXT_USER,
>> + * lbr_nr + 1 is the user call chain number.
>> + * For details, please refer to the comments
>> + * in callchain__printf
>> + */
>> + int mix_chain_nr = i + 1 + lbr_nr + 1;
>> +
>> + if (mix_chain_nr > PERF_MAX_STACK_DEPTH) {
>> + pr_warning("corrupted callchain. skipping...\n");
>> + return 0;
>> + }
>> +
>> + for (j = 0; j < mix_chain_nr; j++) {
>> + if (callchain_param.order == ORDER_CALLEE) {
>> + if (j < i + 1)
>> + ip = chain->ips[j];
>> + else if (j > i + 1)
>> + ip = lbr_stack->entries[j - i - 2].from;
>> + else
>> + ip = lbr_stack->entries[0].to;
>> + } else {
>> + if (j < lbr_nr)
>> + ip = lbr_stack->entries[lbr_nr - j - 1].from;
>> + else if (j > lbr_nr)
>> + ip = chain->ips[i + 1 - (j - lbr_nr)];
>> + else
>> + ip = lbr_stack->entries[0].to;
>> + }
>> +
>> + err = add_callchain_ip(thread, parent, root_al,
>> + cpumode, ip);
>> + if (err)
>> + goto exit;
>> + }
>> + return 0;
>> + }
>> + }
>
> also could you please move whole block above into separated function?
> Andi has another change for this function and it's becoming really big.
Agreed.
Thanks,
Namhyung
next prev parent reply other threads:[~2014-11-18 6:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 13:44 [PATCH V3 0/3] perf tool: Haswell LBR call stack support (user) kan.liang
2014-11-14 13:44 ` [PATCH V3 1/3] perf tools: enable LBR call stack support kan.liang
2014-11-18 5:54 ` Namhyung Kim
2014-11-18 13:57 ` Liang, Kan
2014-11-14 13:44 ` [PATCH V3 2/3] perf tool: Move cpumode resolve code to add_callchain_ip kan.liang
2014-11-17 13:57 ` Jiri Olsa
2014-11-17 14:00 ` Jiri Olsa
2014-11-18 8:24 ` Jiri Olsa
2014-11-21 15:06 ` Liang, Kan
2014-11-21 15:19 ` Arnaldo Carvalho de Melo
2014-11-14 13:44 ` [PATCH V3 3/3] perf tools: Construct LBR call chain kan.liang
2014-11-17 15:54 ` Jiri Olsa
2014-11-17 17:41 ` Liang, Kan
2014-11-18 6:13 ` Namhyung Kim
2014-11-18 7:55 ` Jiri Olsa
2014-11-18 14:37 ` Liang, Kan
2014-11-18 19:40 ` Liang, Kan
2014-11-19 5:57 ` Namhyung Kim
2014-11-17 15:55 ` Jiri Olsa
2014-11-18 6:14 ` Namhyung Kim [this message]
2014-11-18 6:25 ` Namhyung Kim
2014-11-18 14:01 ` Liang, Kan
2014-11-19 6:01 ` Namhyung Kim
2014-11-19 13:37 ` Liang, Kan
2014-11-17 16:01 ` [PATCH V3 0/3] perf tool: Haswell LBR call stack support (user) 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=87h9xxqbm3.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®