linux-kernel - Re: [GIT PULL 00/10] perf/urgent fixes

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: <20141030063404.GA29004@gmail.com>
Date:	Thu, 30 Oct 2014 07:34:04 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
	Arun Sharma <asharma@...com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	David Ahern <dsahern@...il.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Hemant Kumar <hemant@...ux.vnet.ibm.com>,
	Jean Pihet <jean.pihet@...aro.org>,
	Jiri Olsa <jolsa@...nel.org>, Li Zefan <lizefan@...wei.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Namhyung Kim <namhyung.kim@....com>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	Wang Nan <wangnan0@...wei.com>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL 00/10] perf/urgent fixes


* Arnaldo Carvalho de Melo <acme@...nel.org> wrote:

> Hi Ingo,
> 
> 	Please consider pulling,
> 
> - Arnaldo
> 
> The following changes since commit 1776b10627e486dd431fe72d8d47e5a865cf65d1:
> 
>   perf/x86/intel: Revert incomplete and undocumented Broadwell client support (2014-10-29 11:07:58 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo
> 
> for you to fetch changes up to 4cdcc33db2f0455f297b4e14e434ba311ec5ca06:
> 
>   perf probe: Trivial typo fix for --demangle (2014-10-29 10:30:18 -0200)
> 
> ----------------------------------------------------------------
> perf/urgent fixes:
> 
> User visible:
> 
> * Fix report -F (abort, in_tx, mispredict, etc) segfaults for sample.data files
>   without branch info (Jiri Olsa)
> 
> * Add patch that should have went in a previous patchkit to use global cache
>   provided by libunwind (Namhyung Kim)
> 
> * Make CPUINFO_PROC an array to support different kernels, problem
>   detected when the information reported via /proc/cpuinfo changed on ARM (Wang Nan)
> 
> * 'perf probe' --demangle typo fix and a new --quiet option (Masami Hiramatsu)
> 
> Signed-off-by: Arnaldo Carvalho de Melo <acme@...hat.com>
> 
> ----------------------------------------------------------------
> Jiri Olsa (7):
>       perf tools: Fix report -F abort for data without branch info
>       perf tools: Fix report -F in_tx for data without branch info
>       perf tools: Fix report -F mispredict for data without branch info
>       perf tools: Fix report -F symbol_to for data without branch info
>       perf tools: Fix report -F symbol_from for data without branch info
>       perf tools: Fix report -F dso_to for data without branch info
>       perf tools: Fix report -F dso_from for data without branch info
> 
> Masami Hiramatsu (1):
>       perf probe: Trivial typo fix for --demangle
> 
> Namhyung Kim (1):
>       perf callchain: Use global caching provided by libunwind
> 
> Wang Nan (1):
>       perf tools: Make CPUINFO_PROC an array to support different kernel versions
> 
>  tools/perf/builtin-probe.c         |   2 +-
>  tools/perf/perf-sys.h              |  30 +++++------
>  tools/perf/util/header.c           |  27 +++++++---
>  tools/perf/util/sort.c             | 102 +++++++++++++++++++++++++++----------
>  tools/perf/util/thread.c           |   3 ++
>  tools/perf/util/unwind-libunwind.c |  12 +++++
>  tools/perf/util/unwind.h           |   3 ++
>  7 files changed, 131 insertions(+), 48 deletions(-)

Pulled, thanks a lot Arnaldo!

	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/