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] [day] [month] [year] [list]
Date:	Tue, 20 Mar 2012 15:27:41 -0500
From:	Ashay Rane <ashay.r@...il.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	David Ahern <dsahern@...il.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	linux-perf-users@...r.kernel.org,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	Ashay Rane <ashay.rane@...c.utexas.edu>
Subject: Re: [PATCH 1/1] Fix number of events displayed in header

Great, thanks! A (corrected) patch coming up...

Ashay


2012/3/20 Peter Zijlstra <a.p.zijlstra@...llo.nl>:
> On Tue, 2012-03-20 at 15:04 -0500, Ashay Rane wrote:
>> Oh, okay. Thanks for the clarification!
>>
>> However, my reasoning behind including the actual count of the events
>> was that (as far as I can tell) it is not displayed in any of the perf
>> report outputs. I understand that the count is not precise (because of
>> sampling errors) but the sampling frequency (-F) can always be
>> adjusted to get a more accurate number.
>>
>> With the inclusion of the count, it then becomes possible to compare
>> multiple different versions of a program. Hence the patch.
>
> I'm okay if you change the wording of the existing message to be
> clearer. I'm also okay if you add this extra information if you find
> this useful.
>
> In that case, also have a look at the data generated by perf record -s,
> this dumps a PERF_RECORD_READ of the actual counter value at the exit of
> every task [doesn't work with per-cpu counters].
>
>
--
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