lists.openwall.net   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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJh9x3rxK42wFXqCASex1YwMKofWdZ=g-OnH43BHDtUjeMabbA@mail.gmail.com>
Date:	Fri, 24 Feb 2012 17:41:04 -0500
From:	Yuanfang Chen <cyfmxc@...il.com>
To:	David Ahern <dsahern@...il.com>
Cc:	linux-kernel@...r.kernel.org, Namhyung Kim <namhyung@...il.com>
Subject: Re: perf record: can I specify multiple events and use different
 sample-after value

On Thu, Feb 23, 2012 at 2:08 PM, David Ahern <dsahern@...il.com> wrote:
> On 2/23/12 11:52 AM, Yuanfang Chen wrote:
>>>
>>>
>>> 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. :-)
>
>
> you are looking for something like this?
> http://www.spinics.net/lists/linux-perf-users/msg00211.html

Exactly !!

I think I'll settle with perf record for now. Still, unlike trace
event, sample count is not meaningful for PMU event. Output of "perf
script" does not include period value. One line of code will do the
work.

lude 17342 750118.202915: raw 0x3c: 86754      ffffffff8115f6b9
__mem_cgroup_commit_char
lude 17342 750118.203025: raw 0x3c: 1027634   ffffffff811344b9
__mem_cgroup_commit_char

86754, 1027634 is the period value. But I'm not sure which is the PMU
value, is it just period value, or period x sample after. If so, what
is the sample after value?

thank you,
yuanfang

>
> David
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ