From: Harald Servat <harald.servat@bsc.es>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>, linux-perf-users@vger.kernel.org
Subject: Re: Changing frequency rate to perf mem
Date: Mon, 28 Oct 2013 09:15:35 +0100 [thread overview]
Message-ID: <526E1D27.5070302@bsc.es> (raw)
In-Reply-To: <87sivl99do.fsf@sejong.aot.lge.com>
>> I think that this could be implemented extending the mem_options[] in
>> file builtin-mem.c lines 205-221.
>
> Or else, use 'perf record' directly as Andi suggested.
>
>>
>>> Alternatively you can just specify the command line perf mem record
>>> would specify directly to perf record, plus -c/-F
>
> $ perf record -Wd -e cpu/mem-loads/pp -F 200 -- ls
>
> $ perf mem report
>
Wow, thank you for such details! I'll take a look at this!
Best regards.
> Thanks,
> Namhyung
>
--
WARNING / LEGAL TEXT: This message is intended only for the use of the
individual or entity to which it is addressed and may contain
information which is privileged, confidential, proprietary, or exempt
from disclosure under applicable law. If you are not the intended
recipient or the person responsible for delivering the message to the
intended recipient, you are strictly prohibited from disclosing,
distributing, copying, or in any way using this message. If you have
received this communication in error, please notify the sender and
destroy and delete any copies you may have received.
http://www.bsc.es/disclaimer
prev parent reply other threads:[~2013-10-28 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 15:43 Changing frequency rate to perf mem Harald Servat
2013-10-24 5:12 ` Andi Kleen
2013-10-24 7:48 ` Harald Servat
2013-10-28 6:50 ` Namhyung Kim
2013-10-28 8:15 ` Harald Servat [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=526E1D27.5070302@bsc.es \
--to=harald.servat@bsc.es \
--cc=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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).