From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: hupu <hupu.gm@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
james.clark@linaro.org, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [RFC 1/2] perf build: Allow passing extra Clang flags via EXTRA_BPF_FLAGS
Date: Wed, 11 Feb 2026 13:27:04 -0300 [thread overview]
Message-ID: <aYyt2KD3pPu4alvT@x1> (raw)
In-Reply-To: <CADHxFxRprUvRzorxe00HmwG0o73VQJNf=yzM40fkiWjjqu7PZQ@mail.gmail.com>
On Tue, Feb 10, 2026 at 01:54:49PM +0800, hupu wrote:
> On Wed, Dec 24, 2025 at 2:20 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hello,
> >
> > On Tue, Dec 23, 2025 at 04:43:34PM +0800, hupu wrote:
> > > Add support for EXTRA_BPF_FLAGS in the eBPF skeleton build, allowing
> > > users to pass additional Clang options such as --sysroot or custom
> > > include paths when cross-compiling perf.
> > >
> > > This is primarily intended for cross-build scenarios where the default
> > > host include paths do not match the target kernel version.
> > >
> > > Example usage:
> > > make perf ARCH="arm64" EXTRA_BPF_FLAGS="--sysroot=..."
> > >
> > > Change history:
> > > v5:
> > > - Update commit message
> > > v4:
> > > - Apply EXTRA_BPF_FLAGS directly to BPF skeleton build command
> > > instead of modifying CLANG_OPTIONS
> > > v3:
> > > - Move the variable description comment to the top of Makefile.perf
> > > - Update commit message
> > > v2:
> > > - Rename EXTRA_CLANG_FLAGS to EXTRA_BPF_FLAGS
> > > - Update commit message
> > > v1:
> > > - Introduce EXTRA_CLANG_FLAGS to allow passing extra Clang options
> > >
> > > Signed-off-by: hupu <hupu.gm@gmail.com>
> >
> > Reviewed-by: Namhyung Kim <namhyung@kernel.org>
> >
>
> Hi Namhyung,
>
> Sorry to bother you.
>
> I noticed that the patch adding support for EXTRA_BPF_FLAGS, which was
> previously reviewed by you, does not seem to be included in the latest
> released version. I just wanted to follow up and check on the current
> status of this patch, in case it was missed or delayed for some
> reason.
>
> Thanks a lot for your time and review.
Applied this one,
- Arnaldo
next prev parent reply other threads:[~2026-02-11 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 8:43 [RFC 0/2] perf build: Improve header handling for BPF skeleton cross-builds hupu
2025-12-23 8:43 ` [RFC 1/2] perf build: Allow passing extra Clang flags via EXTRA_BPF_FLAGS hupu
2025-12-23 18:20 ` Namhyung Kim
2026-02-10 5:54 ` hupu
2026-02-11 16:27 ` Arnaldo Carvalho de Melo [this message]
2025-12-23 8:43 ` [RFC 2/2] perf build: Prefer kernel source headers for BPF skeletons hupu
2026-01-12 1:46 ` hupu
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=aYyt2KD3pPu4alvT@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hupu.gm@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.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