lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Feb 2012 13:52:09 -0500
From:	Yuanfang Chen <>
To:	Namhyung Kim <>
Subject: Re: perf record: can I specify multiple events and use different
 sample-after value

On Thu, Feb 23, 2012 at 1:51 PM, Yuanfang Chen <> wrote:
> On Thu, Feb 23, 2012 at 2:24 AM, Namhyung Kim <> wrote:
>> 2012-02-23 4:03 AM, Yuanfang Chen wrote:
>>> On Wed, Feb 22, 2012 at 6:40 AM, Namhyung Kim <> wrote:
>>>> Namhyung Kim <> wrote:
>>>>> 2012-02-22 10:59 AM, Yuanfang Chen wrote:
>>>>>> I'm trying use perf tool from the linux kernel package to measure
>>>>>> several raw PMU events. In the manpage of perf-record there is an "-l"
>>>>>> option (Scale counter values), which is useful for my case because I
>>>>>> want to know the total counter value, not just sample count. However
>>>>>> it seems the -l is not recognized, is this expected? How can I get a
>>>>>> total count?
>>>>> "perf report --show-total-period" will be your friend.
>>>> Or else, why not simply run "perf stat"?
>>> My purpose is to get some PMU counter value during each time interval,
>>> only perf record can do this. When using perf record -F, I have to add
>>> up all period value for some event in a some interval to get that
>>> value. When perf record -c, things get a easier, just (sample count x
>>> sample after value) will do, only hassle is to get sample count in
>>> some time interval. However, perf record don't have an option to do
>>> this.
>> I still don't get it. Why "perf stat -e <events> -p <pid> -- sleep
>> <interval>"
>> doesn't work for you? It will show you the value, won't it?
> say my application(not an existing process, so -p <pid> does not
> work.) run for 10 seconds. I want the r03c, r2d4 value during each
> second.  So there will be two values for each event in one second.

oops, forgot to forward. :-)

>> Thanks,
>> Namhyung
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists