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]
Message-ID: <20100305155150.GB20213@ghostprotocols.net>
Date:	Fri, 5 Mar 2010 12:51:50 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Eric B Munson <ebmunson@...ibm.com>
Cc:	a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Add multiple event support to perf report V2

Em Wed, Mar 03, 2010 at 03:38:22PM +0000, Eric B Munson escreveu:
> Currently perf report is unable to handle multiple events even though
> perf record is capable of capturing such a stream.  For instance if we run
> 'perf record -e dtlb-misses -e cache-misses sleep 5'
> today and then ask report to show the results we get:
> 
> # Samples: 18866
> #
> # Overhead  Command      Shared Object  Symbol
> # ........  .......  .................  ......
> #
>     47.52%    sleep  [kernel.kallsyms]  [k] page_fault
>     32.93%    sleep  [kernel.kallsyms]  [k] locks_remove_posix
>      8.52%    sleep  [kernel.kallsyms]  [k] acl_permission_check
>      3.46%    sleep  [kernel.kallsyms]  [k] __wake_up_bit
>      3.31%    sleep  [kernel.kallsyms]  [k] vfs_read
>      3.23%    sleep  [kernel.kallsyms]  [k] kmem_cache_alloc
>      0.56%    sleep  [kernel.kallsyms]  [k] get_page_from_freelist
>      0.15%    sleep  [kernel.kallsyms]  [k] pipe_read
>      0.13%    sleep  [kernel.kallsyms]  [k] pipe_lock_nested
>      0.13%    sleep  [kernel.kallsyms]  [k] mm_alloc
>      0.06%    sleep  [kernel.kallsyms]  [k] mm_init
> #
> # (For a higher level overview, try: perf report --sort comm,dso)
> #
> 
> Worse than only reporting on one of the events, perf report has
> summed the two events. i.e. There is no distinguishing between
> dtlb-misses and cache-misses.
> 
> This set of patches addresses this problem and now when perf report
> is run with the same event stream that produced the above report, the
> output is this:

Thanks a lot, pulled and pushed out!

- Arnaldo
--
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