From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jin Yao <yao.jin@linux.intel.com>
Cc: jolsa@kernel.org, peterz@infradead.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
Subject: Re: [PATCH v1 0/2] perf report: Implement visual marker for macro fusion in annotate
Date: Fri, 16 Jun 2017 13:17:45 -0300 [thread overview]
Message-ID: <20170616161745.GH3645@kernel.org> (raw)
In-Reply-To: <20170616161655.GG3645@kernel.org>
Em Fri, Jun 16, 2017 at 01:16:55PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Jun 14, 2017 at 10:53:39AM +0800, Jin Yao escreveu:
> > 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.
> >
> > In general, the fused instruction pairs are:
> >
> > 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)
>
> Try to have these example outputs in the changesets, not just in the
> patch series header.
Ok, I went trigger happy, sorry, it is in the second patch, I had looked
just at the first :-\
- Arnaldo
> - Arnaldo
>
> > Jin Yao (2):
> > perf report: Check for fused instruction pair
> > perf report: Implement visual marker for macro fusion in annotate
> >
> > tools/perf/arch/x86/util/Build | 1 +
> > tools/perf/arch/x86/util/fused.c | 20 ++++++++++++++++++++
> > tools/perf/ui/browser.c | 27 +++++++++++++++++++++++++++
> > tools/perf/ui/browser.h | 2 ++
> > tools/perf/ui/browsers/annotate.c | 30 ++++++++++++++++++++++++++++++
> > tools/perf/util/Build | 1 +
> > tools/perf/util/annotate.c | 5 +++++
> > tools/perf/util/annotate.h | 1 +
> > tools/perf/util/fused.c | 11 +++++++++++
> > tools/perf/util/fused.h | 8 ++++++++
> > 10 files changed, 106 insertions(+)
> > create mode 100644 tools/perf/arch/x86/util/fused.c
> > create mode 100644 tools/perf/util/fused.c
> > create mode 100644 tools/perf/util/fused.h
> >
> > --
> > 2.7.4
prev parent reply other threads:[~2017-06-16 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 2:53 [PATCH v1 0/2] perf report: Implement visual marker for macro fusion in annotate Jin Yao
2017-06-14 2:53 ` [PATCH v1 1/2] perf report: Check for fused instruction pair Jin Yao
2017-06-16 16:21 ` Arnaldo Carvalho de Melo
2017-06-19 2:58 ` Jin, Yao
2017-06-14 2:53 ` [PATCH v1 2/2] perf report: Implement visual marker for macro fusion in annotate Jin Yao
2017-06-16 16:16 ` [PATCH v1 0/2] " Arnaldo Carvalho de Melo
2017-06-16 16:17 ` Arnaldo Carvalho de Melo [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=20170616161745.GH3645@kernel.org \
--to=acme@kernel.org \
--cc=Linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.