From: "Jin, Yao" <yao.jin@linux.intel.com>
To: 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
Subject: Re: [PATCH v3 0/2] perf report: Implement visual marker for macro fusion in annotate
Date: Thu, 6 Jul 2017 08:42:54 +0800 [thread overview]
Message-ID: <66e5087a-fb11-6970-e48c-edec3017f7ea@linux.intel.com> (raw)
In-Reply-To: <1497961330-3666-1-git-send-email-yao.jin@linux.intel.com>
Hi Arnaldo,
Is this series OK?
Thanks
Jin Yao
On 6/20/2017 8:22 PM, Jin Yao wrote:
> Macro fusion merges two instructions to a single micro-op. Intel
> core platform performs this hardware optimization under limited
> circumstances. For example, CMP + JCC can be "fused" and executed
> /retired together. While with sampling this can result in the
> sample sometimes being on the JCC and sometimes on the CMP.
> So for the fused instruction pair, they could be considered
> together.
>
> On Nehalem, fused instruction pairs:
> cmp/test + jcc.
>
> On other new CPU:
> cmp/test/add/sub/and/inc/dec + jcc.
>
> This patch series marks the case clearly by joining the fused
> instruction pair in the arrow of the jump.
>
> For example:
>
> │ ┌──cmpl $0x0,argp_program_version_hook
> 81.93 │ ├──je 20
> │ │ lock cmpxchg %esi,0x38a9a4(%rip)
> │ │↓ jne 29
> │ │↓ jmp 43
> 11.47 │20:└─→cmpxch %esi,0x38a999(%rip)
>
> Change-log:
> -----------
> v3: 1. Add checking for Nehalem (CMP, TEST). For other newer
> Intel CPUs just check it by default (CMP, TEST, ADD,
> SUB, AND, INC, DEC).
>
> 2. Use Arnaldo's fix to let the display be better
>
> v2: According to Arnaldo's comments, remove the weak function and
> use an arch-specific function instead to check fused instruction
> pair.
>
> v1: Inital post
>
> Jin Yao (2):
> perf util: Check for fused instruction
> perf report: Implement visual marker for macro fusion in annotate
>
> tools/perf/arch/x86/annotate/instructions.c | 37 +++++++++++++++++++++++++++++
> tools/perf/ui/browser.c | 29 ++++++++++++++++++++++
> tools/perf/ui/browser.h | 2 ++
> tools/perf/ui/browsers/annotate.c | 32 +++++++++++++++++++++++++
> tools/perf/util/annotate.c | 17 +++++++++++++
> tools/perf/util/annotate.h | 3 +++
> 6 files changed, 120 insertions(+)
>
prev parent reply other threads:[~2017-07-06 0:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 12:22 Jin Yao
2017-06-20 12:22 ` [PATCH v3 1/2] perf util: Check for fused instruction Jin Yao
2017-07-06 16:24 ` Arnaldo Carvalho de Melo
2017-07-07 1:09 ` Jin, Yao
2017-06-20 12:22 ` [PATCH v3 2/2] perf report: Implement visual marker for macro fusion in annotate Jin Yao
2017-07-06 0:42 ` Jin, Yao [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=66e5087a-fb11-6970-e48c-edec3017f7ea@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=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