From: Manuel Selva <selva.manuel@gmail.com>
To: caobenzhi <caobenzhi0915@gmail.com>, linux-perf-users@vger.kernel.org
Subject: Re: memory read/write access counts event in perf
Date: Sat, 02 Nov 2013 12:06:09 +0100 [thread overview]
Message-ID: <5274DCA1.2050405@gmail.com> (raw)
In-Reply-To: <loom.20131102T102049-521@post.gmane.org>
Hi,
You can have a look at the "perf mem record" and "perf mem report"
tools. On Intel hardware, the recording of memory latency is done
through the PEBS load latency facility.
Manu
On 11/02/2013 10:25 AM, caobenzhi wrote:
> Hi,everyone~
> Recently I want to use perf to count the memory read/write access times, but
> when I use perf list|help, I can't find corresponding events? Does perf
> cannot be used to count memory access times? Any help will be appreciated,
> thanks a lot~
> Best
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-11-02 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 9:25 memory read/write access counts event in perf caobenzhi
2013-11-02 11:06 ` Manuel Selva [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=5274DCA1.2050405@gmail.com \
--to=selva.manuel@gmail.com \
--cc=caobenzhi0915@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
/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).