From: Michael Ellerman <mpe@ellerman.id.au>
To: Jin Yao <yao.jin@linux.intel.com>,
acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com
Cc: Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com,
Jin Yao <yao.jin@linux.intel.com>
Subject: Re: [PATCH v7 1/7] perf/core: Define the common branch type classification
Date: Wed, 12 Jul 2017 20:46:18 +1000 [thread overview]
Message-ID: <87iniykk5h.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1499785263-17383-2-git-send-email-yao.jin@linux.intel.com>
Jin Yao <yao.jin@linux.intel.com> writes:
> It is often useful to know the branch types while analyzing branch
> data. For example, a call is very different from a conditional branch.
>
> Currently we have to look it up in binary while the binary may later
> not be available and even the binary is available but user has to take
> some time. It is very useful for user to check it directly in perf
> report.
>
> Perf already has support for disassembling the branch instruction
> to get the x86 branch type.
>
> To keep consistent on kernel and userspace and make the classification
> more common, the patch adds the common branch type classification
> in perf_event.h.
>
> The patch only defines a minimum but most common set of branch types.
>
> PERF_BR_NONE : 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
This series looks good to me, I agree with Peter that UNKNOWN would be
better than NONE.
I'll add it to my list of things we need to implement on powerpc.
cheers
next prev parent reply other threads:[~2017-07-12 10:46 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
2017-07-12 10:46 ` Michael Ellerman [this message]
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=87iniykk5h.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--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=peterz@infradead.org \
--cc=yao.jin@intel.com \
--cc=yao.jin@linux.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®