Re: [GIT PULL 00/17] perf/core improvements and fixes

From: Ingo Molnar
Date: Fri May 15 2015 - 02:40:05 EST



* Arnaldo Carvalho de Melo <acme@xxxxxxxxxx> wrote:

> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit a41f3c8cd4e28dcbebd8ec27a9602c86cfa5f009:
>
> perf/x86/intel/uncore: Add Broadwell-U uncore IMC PMU support (2015-05-11 11:57:47 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-core-for-mingo
>
> for you to fetch changes up to 70923bd26c732ac2d9e248d80214df6dfd75f78c:
>
> perf tools: Make flex/bison calls honour V=1 (2015-05-14 19:27:47 -0300)
>
> ----------------------------------------------------------------
> perf/core improvements and fixes:
>
> User visible:
>
> - Add --range option to show a variable's location range in 'perf probe',
> helping in collecting variables in probes when there is a mismatch
> between assembly and source code (He Kuang)
>
> - Show better error message when failed to find variable in 'perf probe' (He Kuang)
>
> - Fix 'perf report --thread' handling and document it better (Namhyung Kim)
>
> Infrastructure:
>
> - Fix to get negative exit codes in 'perf test' test routines (He Kuang)
>
> - Make flex/bison calls honour V=1 (Jiri Olsa)
>
> - Ignore tail calls to probed functions in 'perf probe' (Naveen N. Rao)
>
> - Fix refcount expectations in map_group share 'perf test' (Arnaldo Carvalho de Melo)
>
> Build Fixes:
>
> - Fix 'perf kmem' build due to compiler thinking uninitialized var is
> being accessed (Arnaldo Carvalho de Melo)
>
> - Provide le16toh if not defined, to fix the libtraceevent build on
> older distros (Arnaldo Carvalho de Melo)
>
> - Fix 'perf trace' build on older distros by providing some CLOEXEC, NONBLOCK
> defines (Arnaldo Carvalho de Melo)
>
> Signed-off-by: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
>
> ----------------------------------------------------------------
> Arnaldo Carvalho de Melo (6):
> perf kmem: Fix compiler warning about may be accessing uninitialized variable
> perf tests: Show refcounting broken expectations in thread-mg-share test
> perf machine: No need to keep a refcnt for last_match
> perf tests: Fix map_groups refcount test
> tools lib traceevent: Provide le16toh define for older systems
> perf trace: Fix the build on older distros
>
> He Kuang (5):
> perf trace: Removed duplicated NULL test
> perf probe: Remove length limitation for showing available variables
> perf probe: Add --range option to show a variable's location range
> perf probe: Show better error message when failed to find variable
> perf tests: Fix to get negative exit codes
>
> Jiri Olsa (1):
> perf tools: Make flex/bison calls honour V=1
>
> Namhyung Kim (4):
> perf tools: Document relation of per-thread event count feature
> perf report: Force tty output if -T/--thread option is given
> perf report: Do not restrict -T option by other options
> perf report: Fix some option handling on --stdio
>
> Naveen N. Rao (1):
> perf probe: Ignore tail calls to probed functions
>
> tools/lib/traceevent/plugin_cfg80211.c | 13 ++
> tools/perf/Documentation/perf-record.txt | 3 +-
> tools/perf/Documentation/perf-report.txt | 3 +-
> tools/perf/builtin-kmem.c | 2 +-
> tools/perf/builtin-probe.c | 2 +
> tools/perf/builtin-report.c | 17 ++-
> tools/perf/builtin-trace.c | 32 ++++-
> tools/perf/tests/builtin-test.c | 2 +-
> tools/perf/tests/tests.h | 9 ++
> tools/perf/tests/thread-mg-share.c | 29 +++--
> tools/perf/util/Build | 8 +-
> tools/perf/util/cache.h | 1 -
> tools/perf/util/dwarf-aux.c | 204 +++++++++++++++++++++++++++----
> tools/perf/util/dwarf-aux.h | 10 +-
> tools/perf/util/environment.c | 1 -
> tools/perf/util/machine.c | 8 +-
> tools/perf/util/pager.c | 5 -
> tools/perf/util/probe-event.h | 1 +
> tools/perf/util/probe-finder.c | 90 ++++++++++----
> 19 files changed, 346 insertions(+), 94 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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/