mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@kernel.org, jolsa@kernel.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 v7 1/7] perf/core: Define the common branch type classification
Date: Tue, 11 Jul 2017 20:29:21 +0800	[thread overview]
Message-ID: <63ad127b-4a61-bf56-500f-98bca633998b@linux.intel.com> (raw)
In-Reply-To: <20170711120647.mmds5wd3if7u7d7j@hirez.programming.kicks-ass.net>



On 7/11/2017 8:06 PM, Peter Zijlstra wrote:
> On Tue, Jul 11, 2017 at 11:00:57PM +0800, Jin Yao wrote:
>> PERF_BR_NONE            : unknown
> I would suggest PERF_BR_UNKNOWN or PERF_BR_MISC, since PERF_BR_NONE
> reads like it wasn't a branch at all.

OK, I will change it to PERF_BR_UNKNOWN.

>> PERF_BR_COND            :conditional
>> PERF_BR_UNCOND          : unconditional
>> PERF_BR_IND             : indirect
>> PERF_BR_CALL            : function call
>> PERF_BR_IND_CALL        : indirect function call
>> PERF_BR_RET             : function return
>> PERF_BR_SYSCALL         : syscall
>> PERF_BR_SYSRET          : syscall return
>> PERF_BR_COND_CALL       : conditional function call
>> PERF_BR_COND_RET        : conditional function return
>>
>> The patch also adds a new field type (4 bits) in perf_branch_entry
>> to record the branch type (reserve 5 for future branch types)
> What's up with that 5 ? I can't see anything like that in the patch
> itself:

Sorry, I don't say this clearly.

We has defined 11 branch types (from PERF_BR_UNKNOWN to 
PERF_BR_COND_RET), so we can define 5 new types in future.

Thanks
Jin Yao

>> @@ -1024,7 +1048,8 @@ struct perf_branch_entry {
>>   		in_tx:1,    /* in transaction */
>>   		abort:1,    /* transaction abort */
>>   		cycles:16,  /* cycle count to last branch */
>> -		reserved:44;
>> +		type:4,     /* branch type */
>> +		reserved:40;
>>   };
>

  reply	other threads:[~2017-07-11 12:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 15:00 [PATCH v7 0/7] perf report: Show branch type Jin Yao
2017-07-11 15:00 ` [PATCH v7 1/7] perf/core: Define the common branch type classification Jin Yao
2017-07-11 12:06   ` Peter Zijlstra
2017-07-11 12:29     ` Jin, Yao [this message]
2017-07-12 10:46   ` Michael Ellerman
2017-07-11 15:00 ` [PATCH v7 2/7] perf/x86/intel: Record branch type Jin Yao
2017-07-11 15:00 ` [PATCH v7 3/7] perf record: Create a new option save_type in --branch-filter Jin Yao
2017-07-11 15:01 ` [PATCH v7 4/7] perf report: Refactor the branch info printing code Jin Yao
2017-07-11 15:01 ` [PATCH v7 5/7] perf util: Create branch.c/.h for common branch functions Jin Yao
2017-07-11 15:01 ` [PATCH v7 6/7] perf report: Show branch type statistics for stdio mode Jin Yao
2017-07-11 15:01 ` [PATCH v7 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=63ad127b-4a61-bf56-500f-98bca633998b@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=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

Powered by JetHome