From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Michael Jeanson <mjeanson@efficios.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Derek Foreman <derek.foreman@collabora.com>,
Ingo Molnar <mingo@redhat.com>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3] perf data ctf: replace libbabeltrace with babeltrace2-ctf-writer
Date: Thu, 4 Jun 2026 10:29:32 -0300 [thread overview]
Message-ID: <aiF9vEuU2A3m0gUq@x1> (raw)
In-Reply-To: <CAP-5=fUehWvDZB+u1wYGMRa1WD8SUQMqzPqyQB4O78KBa43kOg@mail.gmail.com>
On Wed, May 20, 2026 at 12:26:13PM -0700, Ian Rogers wrote:
> On Wed, May 20, 2026 at 12:15 PM Michael Jeanson <mjeanson@efficios.com> wrote:
> >
> > The 1.x branch of Babeltrace has been superseded by 2.x in 2020 and has
> > been unmaintained since 2022, efforts have started to remove it from
> > popular distributions.
> >
> > Babeltrace 2.x offers a very similar 'ctf-writer' library that can be used
> > with minimal changes for the '--to-ctf' feature and has been packaged
> > since Debian 11 and Fedora 32.
> >
> > This patch replaces the 'libbabeltrace' build feature with
> > 'babeltrace2-ctf-writer' using pkgconfig detection, adjusts the naming of
> > the public headers and applies minor API cleanups.
> >
> > There is no changes to the output ctf traces, the ctf-writer API still
> > implements version 1.8 of the CTF specification that can be read by
> > either Babeltrace 1 / 2 or any CTF compliant reader.
> >
> > Also remove some ifdefs in the cli option parsing to allow printing the
> > helpful error message with '--to-ctf' when built without babeltrace2.
> >
> > Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> > Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> > Cc: Derek Foreman <derek.foreman@collabora.com>
> > Cc: Ian Rogers <irogers@google.com>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: James Clark <james.clark@linaro.org>
> > Cc: Jiri Olsa <jolsa@kernel.org>
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: Peter Zijlstra <peterz@infradead.org>
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Its not applying to perf-tools-next, Michael, can you please take a
look?
Thanks,
- Arnaldo
next prev parent reply other threads:[~2026-06-04 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:47 [PATCH] " Michael Jeanson
2026-05-12 21:54 ` Ian Rogers
2026-05-12 21:56 ` [PATCH 1/2] tools build: Add libbabeltrace2 feature test Ian Rogers
2026-05-12 21:56 ` [PATCH 2/2] perf data convert ctf: Initial babeltrace2 support Ian Rogers
2026-05-13 14:14 ` [PATCH] perf data ctf: replace libbabeltrace with babeltrace2-ctf-writer Michael Jeanson
2026-05-13 16:06 ` Ian Rogers
2026-05-20 16:13 ` Ian Rogers
2026-05-20 17:58 ` Michael Jeanson
2026-05-20 18:12 ` Ian Rogers
2026-05-20 18:52 ` Arnaldo Carvalho de Melo
2026-05-13 16:05 ` [PATCH v2] " Michael Jeanson
2026-05-20 19:14 ` [PATCH v3] " Michael Jeanson
2026-05-20 19:26 ` Ian Rogers
2026-06-04 13:29 ` Arnaldo Carvalho de Melo [this message]
2026-06-04 17:18 ` Michael Jeanson
2026-06-04 17:17 ` [PATCH v4] " Michael Jeanson
2026-06-04 20:20 ` 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=aiF9vEuU2A3m0gUq@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=derek.foreman@collabora.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=mjeanson@efficios.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®