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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120309094804.GA1781@elte.hu>
Date:	Fri, 9 Mar 2012 10:48:04 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, peterz@...radead.org,
	acme@...hat.com, asharma@...com, ravitillo@....gov,
	vweaver1@...s.utk.edu, khandual@...ux.vnet.ibm.com,
	dsahern@...il.com
Subject: Re: [PATCH 0/4] perf tools: improve branch stack sampling


* Stephane Eranian <eranian@...gle.com> wrote:

> This patch set improves upon my LBR v6 patch series posted on
> LKML several weeks ago. It needs to be applied on top of it.
> 
> This series improves perf report and perf record when used
> with taken branch stack sampling.
> 
> For perf record, and based on users' feedback, it is possible
> to omit the branch type with the -b option. In that case,
> the filter is set to the default value of any branch type.
> The branch-filter option is now used to specify more precise
> branch types and privilege levels:
> 
>    $ perf record -b foo
>    equivalent to:
>    $ perf record --branch-filter any foo
> 
>    To filter on specific branch types:
>    $ perf record --branch-filter any_call foo
> 
> For perf report, it is now possible to omit the -b option
> and yet get branch view mode. Perf report is able to auto-detect
> if the perf.data file contains samples with branch stack and
> to switch to the branch mode. It is possible to override this
> by passing --no-branch-stack.
> 
> Furthermore, perf report now supports TUI in branch mode.
> It is possible to naviguate to both the source and destination
> functions of branches.
> 
> Signed-off-by: Stephane Eranian <eranian@...gle.com>
> 
> Stephane Eranian (4):
>   perf record: provide default branch stack sampling mode option
>   perf record: add HEADER_BRANCH_STACK tag
>   perf report: auto-detect branch stack sampling mode
>   perf report: enable TUI in branch view mode
> 
>  tools/perf/Documentation/perf-record.txt |   23 ++++--
>  tools/perf/Documentation/perf-report.txt |    7 +-
>  tools/perf/builtin-record.c              |   71 +++++++++++------
>  tools/perf/builtin-report.c              |  121 ++++++++++++++++++++---------
>  tools/perf/util/header.c                 |   13 +++
>  tools/perf/util/header.h                 |    2 +-
>  tools/perf/util/session.c                |    1 +
>  tools/perf/util/sort.c                   |    2 +-
>  tools/perf/util/sort.h                   |    8 +-
>  tools/perf/util/symbol.h                 |    7 ++-
>  tools/perf/util/ui/browsers/hists.c      |   62 ++++++++++++---
>  11 files changed, 225 insertions(+), 92 deletions(-)

Ok, I tried it out and this is now very usable. I particularly 
liked the detail how the TUI now allows annotation of both the 
source and the target symbols.

I've noticed two small usability glitches:

1) when annotating a symbol and typing 'q' to go back one level, 
   it goes back *two* levels. This is intuitive when just one 
   symbol is annotated, but confusing when there are two 
   symbols: I frequently want to go back to annotate the other 
   symbol as well.

2) two symbols are offered for annotation even when the source
   RIP and target RIP is within the same symbol.

Anyway, I've applied all your patches to 
tip:perf/hw-branch-sampling branch, and if the remaining issues 
are resolved will merge them into tip:perf/core for upstream 
merging. Depending on when the fixes arrive this could be v3.4 
or v3.5.

Thanks,

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