linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Clark Williams <williams@redhat.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes
Date: Wed, 1 Oct 2025 10:34:32 -0300	[thread overview]
Message-ID: <aN0t6Bcd8MKmeBn7@x1> (raw)
In-Reply-To: <CAP-5=fW6tPRW2qdFE4AbXg+47CzTjDX5HEjenjTxgOZ35fFa8A@mail.gmail.com>

On Tue, Sep 30, 2025 at 01:10:59PM -0700, Ian Rogers wrote:
> On Fri, Sep 19, 2025 at 3:10 PM Ian Rogers <irogers@google.com> wrote:
> >
> > On Fri, Sep 19, 2025 at 2:58 PM Namhyung Kim <namhyung@kernel.org> wrote:
> > >
> > > On Fri, Sep 19, 2025 at 06:06:52PM -0300, Arnaldo Carvalho de Melo wrote:
> > > > Hi,
> > > >
> > > >       Please take a look, noticed after processing a patch from Ian
> > > > for another such issue, on a hurry now, haven't checked when that
> > > > emit_string was introduced.
> >
> > emit_strings was added in Linux v6.17 and libbpf was tagged as version
> > 1.7 prior to that.
> >
> > Thanks,
> > Ian
> 
> Ping.
> 
> When this lands I can rebase:
> https://lore.kernel.org/lkml/20250830053549.1966520-1-irogers@google.com/
> on it.

I'm testing this now.

- Arnaldo
 
> Thanks,
> Ian
> 
> > > >
> > > > - Arnaldo
> > > >
> > > > Arnaldo Carvalho de Melo (2):
> > > >   perf bpf: Move the LIBBPF_CURRENT_VERSION_GEQ macro to bpf-utils.h
> > > >   perf bpf: Check libbpf version to use
> > > >     btf_dump_type_data_opts.emit_strings
> > >
> > > Acked-by: Namhyung Kim <namhyung@kernel.org>
> > >
> > > Thanks,
> > > Namhyung
> > >
> > > >
> > > >  tools/perf/util/bpf-event.c  | 2 ++
> > > >  tools/perf/util/bpf-filter.c | 5 +----
> > > >  tools/perf/util/bpf-utils.h  | 5 +++++
> > > >  3 files changed, 8 insertions(+), 4 deletions(-)
> > > >
> > > > --
> > > > 2.51.0
> > > >

      reply	other threads:[~2025-10-01 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 21:06 [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes Arnaldo Carvalho de Melo
2025-09-19 21:06 ` [PATCH 1/2] perf bpf: Move the LIBBPF_CURRENT_VERSION_GEQ macro to bpf-utils.h Arnaldo Carvalho de Melo
2025-09-19 22:04   ` Ian Rogers
2025-09-19 21:06 ` [PATCH 2/2] perf bpf: Check libbpf version to use btf_dump_type_data_opts.emit_strings Arnaldo Carvalho de Melo
2025-09-19 22:03   ` Ian Rogers
2025-09-19 21:58 ` [PATCH 0/2] LIBBPF_DYNAMIC=1 fixes Namhyung Kim
2025-09-19 22:10   ` Ian Rogers
2025-09-30 20:10     ` Ian Rogers
2025-10-01 13:34       ` Arnaldo Carvalho de Melo [this message]

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=aN0t6Bcd8MKmeBn7@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=andrii@kernel.org \
    --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=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.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).