From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
bpf@vger.kernel.org
Cc: Stephane Eranian <eranian@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH 0/3] libtraceevent from system and build fix
Date: Mon, 5 Dec 2022 14:59:37 -0800 [thread overview]
Message-ID: <20221205225940.3079667-1-irogers@google.com> (raw)
A combination of patches previously sent here:
https://lore.kernel.org/all/20221130062935.2219247-1-irogers@google.com/
https://lore.kernel.org/all/20221202045743.2639466-6-irogers@google.com/
and rebased on acme/tmp.perf/core. A fix is added to "perf build:
Fixes for LIBTRACEEVENT_DYNAMIC" for the case where install is invoked
without a DESTDIR.
Ian Rogers (3):
perf build: Fixes for LIBTRACEEVENT_DYNAMIC
perf build: Use libtraceevent from the system
perf build: Fix python/perf.so library's name
tools/perf/Build | 11 ++-
tools/perf/Makefile.config | 41 ++++----
tools/perf/Makefile.perf | 97 ++-----------------
tools/perf/arch/x86/util/Build | 2 +-
tools/perf/arch/x86/util/intel-pt.c | 4 +
tools/perf/builtin-annotate.c | 2 +
tools/perf/builtin-inject.c | 8 ++
tools/perf/builtin-kmem.c | 1 +
tools/perf/builtin-kvm.c | 12 +--
tools/perf/builtin-kwork.c | 1 +
tools/perf/builtin-record.c | 2 +
tools/perf/builtin-report.c | 9 +-
tools/perf/builtin-script.c | 19 +++-
tools/perf/builtin-timechart.c | 1 +
tools/perf/builtin-trace.c | 5 +-
tools/perf/builtin-version.c | 1 +
tools/perf/perf.c | 24 +++--
.../perf/scripts/python/Perf-Trace-Util/Build | 2 +-
tools/perf/tests/Build | 12 +--
tools/perf/tests/builtin-test.c | 6 ++
tools/perf/tests/parse-events.c | 20 ++++
tools/perf/util/Build | 10 +-
tools/perf/util/data-convert-bt.c | 5 +-
tools/perf/util/data-convert-json.c | 9 +-
tools/perf/util/evlist.c | 6 +-
tools/perf/util/evlist.h | 4 +
tools/perf/util/evsel.c | 11 ++-
tools/perf/util/evsel.h | 12 ++-
tools/perf/util/evsel_fprintf.c | 7 +-
tools/perf/util/header.c | 19 ++++
tools/perf/util/header.h | 2 +
tools/perf/util/intel-pt.c | 7 +-
tools/perf/util/parse-events.c | 15 +++
tools/perf/util/parse-events.h | 1 -
tools/perf/util/python.c | 4 +
tools/perf/util/scripting-engines/Build | 6 +-
.../scripting-engines/trace-event-python.c | 1 +
tools/perf/util/session.c | 2 +
tools/perf/util/session.h | 2 +
tools/perf/util/sort.c | 60 ++++++++++--
tools/perf/util/synthetic-events.c | 6 ++
tools/perf/util/trace-event-parse.c | 2 +
tools/perf/util/trace-event-read.c | 1 +
tools/perf/util/trace-event-scripting.c | 1 +
tools/perf/util/trace-event.c | 1 -
tools/perf/util/trace-event.h | 11 ++-
46 files changed, 316 insertions(+), 169 deletions(-)
--
2.39.0.rc0.267.gcb52ba06e7-goog
next reply other threads:[~2022-12-05 23:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 22:59 Ian Rogers [this message]
2022-12-05 22:59 ` [PATCH 1/3] perf build: Fixes for LIBTRACEEVENT_DYNAMIC Ian Rogers
2022-12-05 22:59 ` [PATCH 2/3] perf build: Use libtraceevent from the system Ian Rogers
2022-12-06 16:15 ` Arnaldo Carvalho de Melo
2022-12-06 16:20 ` Arnaldo Carvalho de Melo
2022-12-06 16:23 ` Arnaldo Carvalho de Melo
2022-12-06 16:30 ` Arnaldo Carvalho de Melo
2022-12-06 16:37 ` Arnaldo Carvalho de Melo
2022-12-06 16:41 ` Arnaldo Carvalho de Melo
2022-12-06 17:01 ` Arnaldo Carvalho de Melo
2022-12-06 17:07 ` Arnaldo Carvalho de Melo
2022-12-06 17:13 ` Arnaldo Carvalho de Melo
2022-12-06 17:31 ` Arnaldo Carvalho de Melo
2022-12-06 22:22 ` Ian Rogers
2022-12-07 14:21 ` [ALMOST ready] " Arnaldo Carvalho de Melo
2022-12-07 14:31 ` Arnaldo Carvalho de Melo
2022-12-07 14:33 ` Arnaldo Carvalho de Melo
2022-12-07 14:39 ` Steven Rostedt
2022-12-07 16:02 ` Arnaldo Carvalho de Melo
2022-12-07 16:56 ` Arnaldo Carvalho de Melo
2022-12-07 17:00 ` Ian Rogers
2022-12-07 14:37 ` Arnaldo Carvalho de Melo
2022-12-07 13:38 ` Athira Rajeev
2022-12-07 17:27 ` Arnaldo Carvalho de Melo
2022-12-07 17:31 ` Arnaldo Carvalho de Melo
2022-12-07 17:43 ` Arnaldo Carvalho de Melo
2022-12-08 6:51 ` Athira Rajeev
2022-12-08 22:04 ` Arnaldo Carvalho de Melo
2022-12-08 22:32 ` Arnaldo Carvalho de Melo
2022-12-08 23:00 ` Ian Rogers
2022-12-08 23:05 ` Ian Rogers
2022-12-12 14:13 ` Arnaldo Carvalho de Melo
2022-12-12 14:28 ` Arnaldo Carvalho de Melo
2022-12-09 6:34 ` Athira Rajeev
2022-12-12 13:51 ` Arnaldo Carvalho de Melo
2022-12-13 9:53 ` Athira Rajeev
2022-12-13 22:09 ` Ian Rogers
2022-12-13 22:33 ` Arnaldo Carvalho de Melo
2022-12-13 22:47 ` Ian Rogers
2022-12-15 7:10 ` Athira Rajeev
2022-12-07 13:33 ` Athira Rajeev
2022-12-07 13:46 ` Athira Rajeev
2022-12-07 16:16 ` Ian Rogers
2022-12-07 16:52 ` Arnaldo Carvalho de Melo
2022-12-05 22:59 ` [PATCH 3/3] perf build: Fix python/perf.so library's name Ian Rogers
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=20221205225940.3079667-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=eranian@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.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