linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Runzhen Wang <icycoder@gmail.com>
To: Yuanfang Chen <tabloid.adroit@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf record: per-event sampling period
Date: Tue, 18 Jun 2013 14:39:16 +0800	[thread overview]
Message-ID: <20130618063914.GA25372@gmail.com> (raw)
In-Reply-To: <CAN1HeCdeoNs4rPcLVcJGbcrJhmzjhd9AkJfx2WSPAwJJ_XugMQ@mail.gmail.com>

Hi, Yuanfang,

Usually, the package from fedora offical repo is stable but not
includes some new feature, so, maybe you can download the latest 
linux kernel source code from kernel.org, change directory to 
tools/perf .

Then, be a root to 'make', and try ./perf record .......

the perf tool is small, compile it needs no more than 1min, please 
have a try. ;-)

Thanks
Runzhen

On Mon, Jun 17, 2013 at 02:18:52PM -0400, Yuanfang Chen wrote:
> Hi all,
> 
> Is the per-event sampling period supported now? I'm searching around,
> found [1] using "-c 100,1000" method, [2] using
> "cpu/----/period=1000". However, neither of these work in my box
> (fedora 18, 3.8.11-200.fc18.x86_64, with perf package from fedora 18
> repo ).
> 
> thanks,
> yuanfang
> 
> [1]https://lkml.org/lkml/2010/11/23/122
> [2]http://cscads.rice.edu/workshops/summer-2012/slides/performance-tools/CSCADS_2012_perf_events_status_update.pdf
> --
> 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

      reply	other threads:[~2013-06-18  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 18:18 perf record: per-event sampling period Yuanfang Chen
2013-06-18  6:39 ` Runzhen Wang [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=20130618063914.GA25372@gmail.com \
    --to=icycoder@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=tabloid.adroit@gmail.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).