From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
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 1/2] perf report: Check for fused instruction pair
Date: Mon, 19 Jun 2017 10:58:55 +0800 [thread overview]
Message-ID: <9cc30de7-826d-1bfc-944d-aa9eb9b6803b@linux.intel.com> (raw)
In-Reply-To: <20170616162152.GI3645@kernel.org>
On 6/17/2017 12:21 AM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jun 14, 2017 at 10:53:40AM +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.
> doing it as a weak function that will be overriden by the host arch
> doesn't work, as we also support cross-annotation. So you have to take
> into account perf_evsel__env_arch(evsel), etc.
>
> Please search for perf_evsel__env_arch(evsel) in the annotation source
> files to see how it is used.
>
> - Arnaldo
>
Hi Arnaldo,
Thanks so much for pointing out that the weak function doesn't work.
I have changed it to arch-specific function and just send out v2 series
for reviewing.
Thanks
Jin Yao
next prev parent reply other threads:[~2017-06-19 2:59 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 [this message]
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
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=9cc30de7-826d-1bfc-944d-aa9eb9b6803b@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;
as well as URLs for NNTP newsgroup(s).