From: Jiri Olsa <jolsa@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: [PATCH 00/10] perf tools: Assorted fixes
Date: Wed, 13 Feb 2019 13:32:36 +0100 [thread overview]
Message-ID: <20190213123246.4015-1-jolsa@kernel.org> (raw)
hi,
sending assorted general fixes that queued
up in my other branches.
Also available in here:
https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
perf/fixes
thanks,
jirka
---
Jiri Olsa (10):
perf tools: Compile perf with libperf-in.o instead of libperf.a
perf tools: Rename LIB_FILE to LIBPERF_A
perf tools: Rename build libperf to perf
perf tools: Fix legacy events symbol separator parsing
perf list: Display metric expressions for --details option
perf header: Fix wrong node write in NUMA_TOPOLOGY feature
perf header: Get rid of write_it label
perf header: Remove cpu_nr from struct cpu_topo
perf tools: Add perf_topo_cpu object
perf tools: Add perf_topo_numa object
tools/perf/Build | 10 +++---
tools/perf/Makefile.perf | 22 ++++++------
tools/perf/arch/Build | 4 +--
tools/perf/arch/arm/Build | 4 +--
tools/perf/arch/arm/tests/Build | 8 ++---
tools/perf/arch/arm/util/Build | 8 ++---
tools/perf/arch/arm64/Build | 4 +--
tools/perf/arch/arm64/tests/Build | 6 ++--
tools/perf/arch/arm64/util/Build | 12 +++----
tools/perf/arch/nds32/Build | 2 +-
tools/perf/arch/nds32/util/Build | 2 +-
tools/perf/arch/powerpc/Build | 4 +--
tools/perf/arch/powerpc/tests/Build | 6 ++--
tools/perf/arch/powerpc/util/Build | 18 +++++-----
tools/perf/arch/s390/Build | 2 +-
tools/perf/arch/s390/util/Build | 12 +++----
tools/perf/arch/sh/Build | 2 +-
tools/perf/arch/sh/util/Build | 2 +-
tools/perf/arch/sparc/Build | 2 +-
tools/perf/arch/sparc/util/Build | 2 +-
tools/perf/arch/x86/Build | 4 +--
tools/perf/arch/x86/tests/Build | 14 ++++----
tools/perf/arch/x86/util/Build | 30 ++++++++--------
tools/perf/arch/xtensa/Build | 2 +-
tools/perf/arch/xtensa/util/Build | 2 +-
tools/perf/builtin-list.c | 8 ++---
tools/perf/scripts/Build | 4 +--
tools/perf/scripts/perl/Perf-Trace-Util/Build | 2 +-
tools/perf/scripts/python/Perf-Trace-Util/Build | 2 +-
tools/perf/tests/parse-events.c | 30 ++++++++++++++++
tools/perf/trace/beauty/Build | 26 +++++++-------
tools/perf/ui/Build | 18 +++++-----
tools/perf/ui/browsers/Build | 10 +++---
tools/perf/ui/tui/Build | 8 ++---
tools/perf/util/Build | 277 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------------------------------------------------------------------
tools/perf/util/c++/Build | 4 +--
tools/perf/util/cputopo.c | 264 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tools/perf/util/cputopo.h | 33 +++++++++++++++++
tools/perf/util/cs-etm-decoder/Build | 2 +-
tools/perf/util/header.c | 277 +++++++++++++++++------------------------------------------------------------------------------------------------------------------------------
tools/perf/util/intel-pt-decoder/Build | 2 +-
tools/perf/util/metricgroup.c | 8 ++++-
tools/perf/util/metricgroup.h | 3 +-
tools/perf/util/parse-events.c | 2 +-
tools/perf/util/parse-events.y | 4 +--
tools/perf/util/scripting-engines/Build | 4 +--
46 files changed, 647 insertions(+), 525 deletions(-)
create mode 100644 tools/perf/util/cputopo.c
create mode 100644 tools/perf/util/cputopo.h
next reply other threads:[~2019-02-13 12:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 12:32 Jiri Olsa [this message]
2019-02-13 12:32 ` [PATCH 01/10] perf tools: Compile perf with libperf-in.o instead of libperf.a Jiri Olsa
2019-02-15 9:47 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 02/10] perf tools: Rename LIB_FILE to LIBPERF_A Jiri Olsa
2019-02-15 9:48 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 03/10] perf tools: Rename build libperf to perf Jiri Olsa
2019-02-15 9:49 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 04/10] perf tools: Fix legacy events symbol separator parsing Jiri Olsa
2019-02-15 9:49 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 05/10] perf list: Display metric expressions for --details option Jiri Olsa
2019-02-15 9:50 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 06/10] perf header: Fix wrong node write in NUMA_TOPOLOGY feature Jiri Olsa
[not found] ` <20190213210943.GF1904@kernel.org>
[not found] ` <20190213211428.GG1904@kernel.org>
2019-02-15 18:12 ` Jiri Olsa
2019-02-13 12:32 ` [PATCH 07/10] perf header: Get rid of write_it label Jiri Olsa
2019-02-15 9:51 ` [tip:perf/core] " tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 08/10] perf header: Remove cpu_nr from struct cpu_topo Jiri Olsa
2019-02-15 9:51 ` [tip:perf/core] perf header: Remove unused 'cpu_nr' field from 'struct cpu_topo' tip-bot for Jiri Olsa
2019-02-13 12:32 ` [PATCH 09/10] perf tools: Add perf_topo_cpu object Jiri Olsa
[not found] ` <20190213211935.GH1904@kernel.org>
2019-02-15 18:12 ` Jiri Olsa
2019-02-13 12:32 ` [PATCH 10/10] perf tools: Add perf_topo_numa object Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190213123246.4015-1-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).