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>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: Stephane Eranian <eranian@google.com>, Ian Rogers <irogers@google.com>
Subject: [PATCH v3 0/2] perf parse-events: Break out tracepoint and printing
Date: Fri, 29 Jul 2022 13:42:15 -0700 [thread overview]
Message-ID: <20220729204217.250166-1-irogers@google.com> (raw)
parse-events.c is a large piece of code that doesn't need to contain the
printing (perf list) and tracepoint functionality. Split apart.
v3. Split removal of #define to its own change as suggested by Jiri
Olsa <jolsa@kernel.org>.
v2. Rebase in particular after hybrid PMU changes.
Ian Rogers (2):
perf parse-events: Don't #define YY_EXTRA_TYPE
perf parse-events: Break out tracepoint and printing.
tools/perf/builtin-list.c | 2 +-
tools/perf/builtin-lock.c | 1 +
tools/perf/builtin-timechart.c | 1 +
tools/perf/builtin-trace.c | 1 +
tools/perf/util/Build | 2 +
tools/perf/util/parse-events.c | 714 +----------------------------
tools/perf/util/parse-events.h | 31 --
tools/perf/util/print-events.c | 571 +++++++++++++++++++++++
tools/perf/util/print-events.h | 22 +
tools/perf/util/trace-event-info.c | 96 ++++
tools/perf/util/tracepoint.c | 63 +++
tools/perf/util/tracepoint.h | 25 +
12 files changed, 790 insertions(+), 739 deletions(-)
create mode 100644 tools/perf/util/print-events.c
create mode 100644 tools/perf/util/print-events.h
create mode 100644 tools/perf/util/tracepoint.c
create mode 100644 tools/perf/util/tracepoint.h
--
2.37.1.455.g008518b4e5-goog
next reply other threads:[~2022-07-29 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 20:42 Ian Rogers [this message]
2022-07-29 20:42 ` [PATCH v3 1/2] perf parse-events: Don't #define YY_EXTRA_TYPE Ian Rogers
2022-07-29 20:42 ` [PATCH v3 2/2] perf parse-events: Break out tracepoint and printing 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=20220729204217.250166-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--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=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
all inboxes | Powered by JetHome®