From: Jiri Olsa <jolsa@redhat.com>
To: Jin Yao <yao.jin@linux.intel.com>, peterz@infradead.org
Cc: acme@kernel.org, jolsa@kernel.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 0/7] perf report: Show branch type
Date: Fri, 7 Jul 2017 10:09:43 +0200 [thread overview]
Message-ID: <20170707080943.GB3987@krava> (raw)
In-Reply-To: <1492690075-17243-1-git-send-email-yao.jin@linux.intel.com>
On Thu, Apr 20, 2017 at 08:07:48PM +0800, Jin Yao wrote:
> v6:
> Update according to the review comments from
> Jiri Olsa <jolsa@redhat.com>. Major modifications are:
>
> 1. Move that multiline conditional code inside {} brackets.
>
> 2. Move branch_type_stat_display() from builtin-report.c to
> branch.c. Move branch_type_str() from callchain.c to
> branch.c.
>
> 3. Keep the original branch info display order, that is:
> predicted, abort, cycles, iterations
Peter,
are you ok with the kernel side of this?
thanks,
jirka
>
> v5:
> ---
> Mainly the v5 patch series are updated according to
> comments from Jiri Olsa <jolsa@redhat.com>.
>
> The kernel part doesn't have functional change. It just
> solve the merge issue.
>
> In userspace, the functions of branch type counting and
> branch type name resolving are moved to the new files:
> util/branch.c, util/branch.h.
>
> And refactor the branch info printing code for better
> maintenance.
>
> Not changed (or just fix merge issue):
> perf/core: Define the common branch type classification
> perf/x86/intel: Record branch type
> perf record: Create a new option save_type in --branch-filter
>
> New patches:
> perf report: Refactor the branch info printing code
> perf util: Create branch.c/.h for common branch functions
>
> Changed:
> perf report: Show branch type statistics for stdio mode
> perf report: Show branch type in callchain entry
>
> v4:
> ---
> 1. Describe the major changes in patch description.
> Thanks for Peter Zijlstra's reminding.
>
> 2. Initialize branch type to 0 in intel_pmu_lbr_read_32 and
> intel_pmu_lbr_read_64. Remove the invalid else code in
> intel_pmu_lbr_filter.
>
> v3:
> ---
> 1. Move the JCC forward/backward and cross page computing from
> kernel to userspace.
>
> 2. Use lookup table to replace original switch/case processing.
>
> Changed:
> perf/core: Define the common branch type classification
> perf/x86/intel: Record branch type
> perf report: Show branch type statistics for stdio mode
> perf report: Show branch type in callchain entry
>
> Not changed:
> perf record: Create a new option save_type in --branch-filter
>
> v2:
> ---
> 1. Use 4 bits in perf_branch_entry to record branch type.
>
> 2. Pull out some common branch types from FAR_BRANCH. Now the branch
> types defined in perf_event.h:
>
> Jin Yao (7):
> perf/core: Define the common branch type classification
> perf/x86/intel: Record branch type
> perf record: Create a new option save_type in --branch-filter
> perf report: Refactor the branch info printing code
> perf util: Create branch.c/.h for common branch functions
> perf report: Show branch type statistics for stdio mode
> perf report: Show branch type in callchain entry
>
> arch/x86/events/intel/lbr.c | 53 +++++++++-
> include/uapi/linux/perf_event.h | 29 +++++-
> tools/include/uapi/linux/perf_event.h | 29 +++++-
> tools/perf/Documentation/perf-record.txt | 1 +
> tools/perf/builtin-report.c | 25 +++++
> tools/perf/util/Build | 1 +
> tools/perf/util/branch.c | 168 +++++++++++++++++++++++++++++++
> tools/perf/util/branch.h | 25 +++++
> tools/perf/util/callchain.c | 140 ++++++++++++++------------
> tools/perf/util/callchain.h | 5 +-
> tools/perf/util/event.h | 3 +-
> tools/perf/util/hist.c | 5 +-
> tools/perf/util/machine.c | 26 +++--
> tools/perf/util/parse-branch-options.c | 1 +
> 14 files changed, 427 insertions(+), 84 deletions(-)
> create mode 100644 tools/perf/util/branch.c
> create mode 100644 tools/perf/util/branch.h
>
> --
> 2.7.4
>
prev parent reply other threads:[~2017-07-07 8:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 12:07 [PATCH v6 0/7] perf report: Show branch type Jin Yao
2017-04-20 9:36 ` Jiri Olsa
2017-04-23 8:36 ` Jin, Yao
2017-06-02 8:02 ` Jin, Yao
2017-06-26 6:24 ` Jin, Yao
2017-07-06 1:47 ` Jin, Yao
2017-04-20 12:07 ` [PATCH v6 1/7] perf/core: Define the common branch type classification Jin Yao
2017-07-07 8:42 ` Peter Zijlstra
2017-07-10 5:19 ` Michael Ellerman
2017-07-10 6:05 ` Michael Ellerman
2017-07-10 8:16 ` Jin, Yao
2017-07-10 10:32 ` Michael Ellerman
2017-07-10 11:46 ` Jin, Yao
2017-07-10 13:10 ` Segher Boessenkool
2017-07-10 13:28 ` Jin, Yao
2017-07-10 13:46 ` Peter Zijlstra
2017-07-10 14:06 ` Jin, Yao
2017-07-11 2:28 ` Michael Ellerman
2017-07-11 3:00 ` Jin, Yao
2017-07-10 14:37 ` Segher Boessenkool
2017-07-11 2:13 ` Michael Ellerman
2017-04-20 12:07 ` [PATCH v6 2/7] perf/x86/intel: Record branch type Jin Yao
2017-04-23 13:55 ` Jiri Olsa
2017-04-24 0:47 ` Jin, Yao
2017-05-08 0:49 ` Jin, Yao
2017-05-09 8:26 ` Jiri Olsa
2017-05-09 11:57 ` Jin, Yao
2017-05-09 12:39 ` Jiri Olsa
2017-05-10 0:18 ` Jin, Yao
2017-04-20 12:07 ` [PATCH v6 3/7] perf record: Create a new option save_type in --branch-filter Jin Yao
2017-04-20 12:07 ` [PATCH v6 4/7] perf report: Refactor the branch info printing code Jin Yao
2017-04-20 12:07 ` [PATCH v6 5/7] perf util: Create branch.c/.h for common branch functions Jin Yao
2017-04-20 12:07 ` [PATCH v6 6/7] perf report: Show branch type statistics for stdio mode Jin Yao
2017-04-20 12:07 ` [PATCH v6 7/7] perf report: Show branch type in callchain entry Jin Yao
2017-07-07 8:09 ` Jiri Olsa [this message]
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=20170707080943.GB3987@krava \
--to=jolsa@redhat.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=linuxppc-dev@lists.ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).