From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Borislav Petkov <bp@amd64.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: specifying raw perf events
Date: Tue, 25 Sep 2012 10:02:01 -0700 [thread overview]
Message-ID: <20120925170201.GD14405@ghostprotocols.net> (raw)
In-Reply-To: <20120925155235.GA6982@aftab.osrc.amd.com>
Em Tue, Sep 25, 2012 at 05:52:35PM +0200, Borislav Petkov escreveu:
> I'm trying to use raw events and to read how exactly they're specified.
> Here's what do:
>
> $ perf list -h
>
> ...
> rNNN [Raw hardware event descriptor]
> cpu/t1=v1[,t2=v2,t3 ...]/modifier [Raw hardware event descriptor]
> (see 'perf list --help' on how to encode it)
> ...
>
> $ perf list --help
> $
>
> No help. :-(
>
> $ perf --version
> perf version 3.6.rc7.1723.g226ea0
>
> That's latest Linus + tip/auto-latest.
$ make -C tools/perf/Documentation install
?
- Arnaldo
next prev parent reply other threads:[~2012-09-25 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 15:52 specifying raw perf events Borislav Petkov
2012-09-25 17:02 ` Arnaldo Carvalho de Melo [this message]
2012-09-25 17:03 ` Arnaldo Carvalho de Melo
2012-09-25 17:11 ` Borislav Petkov
2012-09-25 17:45 ` Arnaldo Carvalho de Melo
2012-09-25 17:46 ` Borislav Petkov
2012-09-28 17:47 ` [PATCH] perf: Build install-man target when installing Borislav Petkov
2012-10-20 11:16 ` Borislav Petkov
2012-10-20 15:37 ` Arnaldo Carvalho de Melo
2012-10-22 7:25 ` Namhyung Kim
2012-10-22 10:07 ` Borislav Petkov
2012-10-22 14:03 ` Arnaldo Carvalho de Melo
2012-10-22 23:13 ` Borislav Petkov
2012-10-23 13:39 ` Arnaldo Carvalho de Melo
2012-10-24 17:03 ` Arnaldo Carvalho de Melo
2012-10-24 17:20 ` Arnaldo Carvalho de Melo
2012-10-24 19:30 ` Borislav Petkov
2012-10-24 19:41 ` 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=20120925170201.GD14405@ghostprotocols.net \
--to=acme@infradead.org \
--cc=bp@amd64.org \
--cc=linux-kernel@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).