From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Athira Jajeev <atrajeev@linux.vnet.ibm.com>,
James Clark <james.clark@linaro.org>,
Dominique Martinet <asmadeus@codewreck.org>,
Yang Li <yang.lee@linux.alibaba.com>,
Colin Ian King <colin.i.king@gmail.com>,
Yang Jihong <yangjihong@bytedance.com>,
"Steinar H. Gunderson" <sesse@google.com>,
Oliver Upton <oliver.upton@linux.dev>,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
Ze Gao <zegao2021@gmail.com>, Weilin Wang <weilin.wang@intel.com>,
Ben Gainey <ben.gainey@arm.com>,
zhaimingbing <zhaimingbing@cmss.chinamobile.com>,
Zixian Cai <fzczx123@gmail.com>, Andi Kleen <ak@linux.intel.com>,
Paran Lee <p4ranlee@gmail.com>,
Thomas Falcon <thomas.falcon@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: Re: [PATCH v2 3/6] perf trace-event: Always build trace-event-info.c
Date: Tue, 5 Nov 2024 14:22:48 -0300 [thread overview]
Message-ID: <ZypUaPH9UjXQyXYz@x1> (raw)
In-Reply-To: <20241102165400.75785-4-irogers@google.com>
On Sat, Nov 02, 2024 at 09:53:57AM -0700, Ian Rogers wrote:
> trace-event-info.c has no libtraceevent depdendencies, always build it
> and use it in builtin-record and perf_event_attr printing.
Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/builtin-record.c | 2 --
> tools/perf/util/Build | 2 +-
> tools/perf/util/perf_event_attr_fprintf.c | 4 ----
> 3 files changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index f83252472921..0b637cea4850 100644
> --- a/tools/perf/builtin-record.c
> +++ b/tools/perf/builtin-record.c
> @@ -1748,10 +1748,8 @@ static void record__init_features(struct record *rec)
> if (rec->no_buildid)
> perf_header__clear_feat(&session->header, HEADER_BUILD_ID);
>
> -#ifdef HAVE_LIBTRACEEVENT
> if (!have_tracepoints(&rec->evlist->core.entries))
> perf_header__clear_feat(&session->header, HEADER_TRACING_DATA);
> -#endif
>
> if (!rec->opts.branch_stack)
> perf_header__clear_feat(&session->header, HEADER_BRANCH_STACK);
> diff --git a/tools/perf/util/Build b/tools/perf/util/Build
> index 1eedead5f2f2..609c69995c51 100644
> --- a/tools/perf/util/Build
> +++ b/tools/perf/util/Build
> @@ -85,7 +85,7 @@ perf-util-y += pmu-flex.o
> perf-util-y += pmu-bison.o
> perf-util-y += tool_pmu.o
> perf-util-y += svghelper.o
> -perf-util-$(CONFIG_LIBTRACEEVENT) += trace-event-info.o
> +perf-util-y += trace-event-info.o
> perf-util-y += trace-event-scripting.o
> perf-util-$(CONFIG_LIBTRACEEVENT) += trace-event.o
> perf-util-$(CONFIG_LIBTRACEEVENT) += trace-event-parse.o
> diff --git a/tools/perf/util/perf_event_attr_fprintf.c b/tools/perf/util/perf_event_attr_fprintf.c
> index 59fbbba79697..a73c74b99a3b 100644
> --- a/tools/perf/util/perf_event_attr_fprintf.c
> +++ b/tools/perf/util/perf_event_attr_fprintf.c
> @@ -212,7 +212,6 @@ static void __p_config_hw_cache_id(char *buf, size_t size, u64 value)
> }
> }
>
> -#ifdef HAVE_LIBTRACEEVENT
> static void __p_config_tracepoint_id(char *buf, size_t size, u64 value)
> {
> char *str = tracepoint_id_to_name(value);
> @@ -220,7 +219,6 @@ static void __p_config_tracepoint_id(char *buf, size_t size, u64 value)
> print_id_hex(str);
> free(str);
> }
> -#endif
>
> static void __p_config_id(struct perf_pmu *pmu, char *buf, size_t size, u32 type, u64 value)
> {
> @@ -238,9 +236,7 @@ static void __p_config_id(struct perf_pmu *pmu, char *buf, size_t size, u32 type
> case PERF_TYPE_HW_CACHE:
> return __p_config_hw_cache_id(buf, size, value);
> case PERF_TYPE_TRACEPOINT:
> -#ifdef HAVE_LIBTRACEEVENT
> return __p_config_tracepoint_id(buf, size, value);
> -#endif
> case PERF_TYPE_RAW:
> case PERF_TYPE_BREAKPOINT:
> default:
> --
> 2.47.0.199.ga7371fff76-goog
next prev parent reply other threads:[~2024-11-05 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 16:53 [PATCH v2 0/6] Avoid parsing tracepoint format just for id Ian Rogers
2024-11-02 16:53 ` [PATCH v2 1/6] tool api fs: Correctly encode errno for read/write open failures Ian Rogers
2024-11-05 17:18 ` Arnaldo Carvalho de Melo
2024-11-02 16:53 ` [PATCH v2 2/6] perf trace-event: Constify print arguments Ian Rogers
2024-11-05 17:18 ` Arnaldo Carvalho de Melo
2024-11-02 16:53 ` [PATCH v2 3/6] perf trace-event: Always build trace-event-info.c Ian Rogers
2024-11-05 17:22 ` Arnaldo Carvalho de Melo [this message]
2024-11-02 16:53 ` [PATCH v2 4/6] perf evsel: Add/use accessor for tp_format Ian Rogers
2024-11-05 17:36 ` Arnaldo Carvalho de Melo
2024-11-05 19:33 ` Ian Rogers
2024-11-05 19:52 ` Arnaldo Carvalho de Melo
2024-11-05 21:04 ` Ian Rogers
2024-11-02 16:53 ` [PATCH v2 5/6] perf evsel: Allow evsel__newtp without libtraceevent Ian Rogers
2024-11-05 17:45 ` Arnaldo Carvalho de Melo
2024-11-02 16:54 ` [PATCH v2 6/6] perf tests: Enable tests disabled due to tracepoint parsing Ian Rogers
2024-11-05 17:47 ` Arnaldo Carvalho de Melo
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=ZypUaPH9UjXQyXYz@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=ben.gainey@arm.com \
--cc=colin.i.king@gmail.com \
--cc=fzczx123@gmail.com \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--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=oliver.upton@linux.dev \
--cc=p4ranlee@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sesse@google.com \
--cc=thomas.falcon@intel.com \
--cc=weilin.wang@intel.com \
--cc=yang.lee@linux.alibaba.com \
--cc=yangjihong@bytedance.com \
--cc=zegao2021@gmail.com \
--cc=zhaimingbing@cmss.chinamobile.com \
/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).