From: ahmadkhorrami <ahmadkhorrami@ut.ac.ir>
To: Andi Kleen <andi@firstfloor.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Jin Yao <yao.jin@linux.intel.com>,
Linux-trace Users <linux-trace-users@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-trace-users-owner@vger.kernel.org
Subject: Re: Perf Reports Jump Instructions as Memory Access Instructions
Date: Wed, 03 Jun 2020 08:19:34 +0430 [thread overview]
Message-ID: <1113a5891fcccce6cfe59e6da59eee95@ut.ac.ir> (raw)
In-Reply-To: <3043c6c2f878ad3419e350867903cb0a@ut.ac.ir>
Thanks everybody, specially, Steven, Arnaldo and Andi.
On 2020-05-27 00:25, ahmadkhorrami wrote:
> Thanks! This seems reasonable. But as Arnaldo says, why is there a skid
> in the access address while PEBS is used? Both RIP and Access Address
> should match, Right?
> Regards.
>
> On 2020-05-26 21:12, Andi Kleen wrote:
>
>> The access point is at offset 0 of the following disassembly:
>> Dump of assembler code for function
>> cairo_surface_get_device_scale@plt:
>
> 0x000000000002a310 <+0>: jmpq *0x2c8b3a(%rip) # 0x2f2e50
> 0x000000000002a316 <+6>: pushq $0x1c7
> 0x000000000002a31b <+11>: jmpq 0x28690
>
> This is an unconditional jump which will not lead to macrofusion.
But that will access memory, no? The instruction at offset 0.
Instruction fetches are not sampled by the MEM_INST_RETIRED event.
This is an indirect jump through memory, so it accesses the memory at
0x2c8b3a(%rip). These kind of accesses are sampled by the event.
Other memory accesses as part of other instructions may be sampled too.
-Andi
next prev parent reply other threads:[~2020-06-03 3:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 13:38 Perf Reports Jump Instructions as Memory Access Instructions Arnaldo Carvalho de Melo
2020-05-26 16:42 ` Andi Kleen
2020-05-26 19:55 ` ahmadkhorrami
2020-06-03 3:49 ` ahmadkhorrami [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-17 15:10 ahmadkhorrami
2020-05-23 18:07 ` ahmadkhorrami
2020-05-25 14:52 ` Steven Rostedt
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=1113a5891fcccce6cfe59e6da59eee95@ut.ac.ir \
--to=ahmadkhorrami@ut.ac.ir \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-users-owner@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--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.