From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
mpe@ellerman.id.au, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v9 2/7] perf/x86/intel: Record branch type
Date: Mon, 17 Jul 2017 16:28:38 +0800 [thread overview]
Message-ID: <a5a5d2a0-e900-6cb0-ba65-911e939dcdcb@linux.intel.com> (raw)
In-Reply-To: <20170717081112.GC22046@krava>
On 7/17/2017 4:11 PM, Jiri Olsa wrote:
> On Mon, Jul 17, 2017 at 07:06:38PM +0800, Jin Yao wrote:
>
> SNIP
>
>> +#define X86_BR_TYPE_MAP_MAX 16
>> +
>> +static int
>> +common_branch_type(int type)
>> +{
>> + int i;
>> + const int branch_map[X86_BR_TYPE_MAP_MAX] = {
>> + PERF_BR_CALL, /* X86_BR_CALL */
>> + PERF_BR_RET, /* X86_BR_RET */
>> + PERF_BR_SYSCALL, /* X86_BR_SYSCALL */
>> + PERF_BR_SYSRET, /* X86_BR_SYSRET */
>> + PERF_BR_UNKNOWN, /* X86_BR_INT */
>> + PERF_BR_UNKNOWN, /* X86_BR_IRET */
>> + PERF_BR_COND, /* X86_BR_JCC */
>> + PERF_BR_UNCOND, /* X86_BR_JMP */
>> + PERF_BR_UNKNOWN, /* X86_BR_IRQ */
>> + PERF_BR_IND_CALL, /* X86_BR_IND_CALL */
>> + PERF_BR_UNKNOWN, /* X86_BR_ABORT */
>> + PERF_BR_UNKNOWN, /* X86_BR_IN_TX */
>> + PERF_BR_UNKNOWN, /* X86_BR_NO_TX */
>> + PERF_BR_CALL, /* X86_BR_ZERO_CALL */
>> + PERF_BR_UNKNOWN, /* X86_BR_CALL_STACK */
>> + PERF_BR_IND, /* X86_BR_IND_JMP */
>> + };
> should the branch_map array be static? having it on stack makes
> the compiler to create it every time we call the function
>
> jirka
OK, agree to let branch_map array be static. I will add this in v10.
I'm also waiting for Peter's review comments for this patch update.
Thanks
Jin Yao
>
>> +
>> + type >>= 2; /* skip X86_BR_USER and X86_BR_KERNEL */
>> +
>> + if (type) {
>> + i = __ffs(type);
>> + if (i < X86_BR_TYPE_MAP_MAX)
>> + return branch_map[i];
>> + }
>> +
>> + return PERF_BR_UNKNOWN;
>> +}
>> +
>> /*
>> * implement actual branch filter based on user demand.
>> * Hardware may not exactly satisfy that request, thus
>> @@ -942,7 +987,8 @@ intel_pmu_lbr_filter(struct cpu_hw_events *cpuc)
>> bool compress = false;
>>
>> /* if sampling all branches, then nothing to filter */
>> - if ((br_sel & X86_BR_ALL) == X86_BR_ALL)
>> + if (((br_sel & X86_BR_ALL) == X86_BR_ALL) &&
>> + ((br_sel & X86_BR_TYPE_SAVE) != X86_BR_TYPE_SAVE))
>> return;
>>
>> for (i = 0; i < cpuc->lbr_stack.nr; i++) {
>> @@ -963,6 +1009,9 @@ intel_pmu_lbr_filter(struct cpu_hw_events *cpuc)
>> cpuc->lbr_entries[i].from = 0;
>> compress = true;
>> }
>> +
>> + if ((br_sel & X86_BR_TYPE_SAVE) == X86_BR_TYPE_SAVE)
>> + cpuc->lbr_entries[i].type = common_branch_type(type);
>> }
>>
>> if (!compress)
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2017-07-17 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 11:06 [PATCH v9 0/7] perf report: Show branch type Jin Yao
2017-07-17 8:19 ` Jiri Olsa
2017-07-17 11:06 ` [PATCH v9 1/7] perf/core: Define the common branch type classification Jin Yao
2017-07-17 11:06 ` [PATCH v9 2/7] perf/x86/intel: Record branch type Jin Yao
2017-07-17 8:11 ` Jiri Olsa
2017-07-17 8:28 ` Jin, Yao [this message]
2017-07-18 9:23 ` Peter Zijlstra
2017-07-17 11:06 ` [PATCH v9 3/7] perf record: Create a new option save_type in --branch-filter Jin Yao
2017-07-17 11:06 ` [PATCH v9 4/7] perf report: Refactor the branch info printing code Jin Yao
2017-07-17 11:06 ` [PATCH v9 5/7] perf util: Create branch.c/.h for common branch functions Jin Yao
2017-07-17 11:06 ` [PATCH v9 6/7] perf report: Show branch type statistics for stdio mode Jin Yao
2017-07-17 11:06 ` [PATCH v9 7/7] perf report: Show branch type in callchain entry Jin Yao
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=a5a5d2a0-e900-6cb0-ba65-911e939dcdcb@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=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=yao.jin@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