From: Tony Ambardar <tony.ambardar@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Mykola Lysenko <mykolal@fb.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH bpf-next v1] selftests/bpf: Fix wrong binary in Makefile log output
Date: Mon, 22 Jul 2024 18:35:25 -0700 [thread overview]
Message-ID: <Zp8I3aN/bZnka4I+@kodidev-ubuntu> (raw)
In-Reply-To: <ZptJ1dsnKbjTZ6iH@kodidev-ubuntu>
On Fri, Jul 19, 2024 at 10:23:33PM -0700, Tony Ambardar wrote:
> On Fri, Jul 19, 2024 at 07:57:09PM -0700, Andrii Nakryiko wrote:
> > On Fri, Jul 19, 2024 at 4:22 PM Tony Ambardar <tony.ambardar@gmail.com> wrote:
> > >
[...]
> > > --- a/tools/testing/selftests/bpf/Makefile
> > > +++ b/tools/testing/selftests/bpf/Makefile
> > > @@ -425,27 +425,28 @@ $(OUTPUT)/flow_dissector_load.o: flow_dissector_load.h
> > > $(OUTPUT)/cgroup_getset_retval_hooks.o: cgroup_getset_retval_hooks.h
> > >
> > > # Build BPF object using Clang
> > > -# $1 - input .c file
> > > -# $2 - output .o file
> > > -# $3 - CFLAGS
> > > +# $1 - binary name
> > > +# $2 - input .c file
> > > +# $3 - output .o file
> > > +# $4 - CFLAGS
> > > define CLANG_BPF_BUILD_RULE
> > > - $(call msg,CLNG-BPF,$(TRUNNER_BINARY),$2)
> > > - $(Q)$(CLANG) $3 -O2 --target=bpf -c $1 -mcpu=v3 -o $2
> > > + $(call msg,CLNG-BPF,$1,$3)
> > > + $(Q)$(CLANG) $4 -O2 --target=bpf -c $2 -mcpu=v3 -o $3
> >
> > this works, but did you have to renumber all parameters? Let's maybe
> > pass this binary name as the 4th argument?
> >
>
> OK, I'll update as requested and minimize the diff.
>
Hi Andrii,
I sent out a v2 based on your suggestions but omitted Eduard's Acked-by:
by mistake. Should I resubmit or is that something you can update?
Thanks,
Tony
> > pw-bot: cr
> >
> > > endef
> > > # Similar to CLANG_BPF_BUILD_RULE, but with disabled alu32
> > > define CLANG_NOALU32_BPF_BUILD_RULE
> > > - $(call msg,CLNG-BPF,$(TRUNNER_BINARY),$2)
> > > - $(Q)$(CLANG) $3 -O2 --target=bpf -c $1 -mcpu=v2 -o $2
> > > + $(call msg,CLNG-BPF,$1,$3)
> > > + $(Q)$(CLANG) $4 -O2 --target=bpf -c $2 -mcpu=v2 -o $3
> > > endef
> > > # Similar to CLANG_BPF_BUILD_RULE, but with cpu-v4
> > > define CLANG_CPUV4_BPF_BUILD_RULE
> > > - $(call msg,CLNG-BPF,$(TRUNNER_BINARY),$2)
> > > - $(Q)$(CLANG) $3 -O2 --target=bpf -c $1 -mcpu=v4 -o $2
> > > + $(call msg,CLNG-BPF,$1,$3)
> > > + $(Q)$(CLANG) $4 -O2 --target=bpf -c $2 -mcpu=v4 -o $3
> > > endef
> > > # Build BPF object using GCC
> > > define GCC_BPF_BUILD_RULE
> > > - $(call msg,GCC-BPF,$(TRUNNER_BINARY),$2)
> > > - $(Q)$(BPF_GCC) $3 -DBPF_NO_PRESERVE_ACCESS_INDEX -Wno-attributes -O2 -c $1 -o $2
> > > + $(call msg,GCC-BPF,$1,$3)
> > > + $(Q)$(BPF_GCC) $4 -DBPF_NO_PRESERVE_ACCESS_INDEX -Wno-attributes -O2 -c $2 -o $3
> > > endef
> > >
> > > SKEL_BLACKLIST := btf__% test_pinning_invalid.c test_sk_assign.c
> > > @@ -534,7 +535,7 @@ $(TRUNNER_BPF_OBJS): $(TRUNNER_OUTPUT)/%.bpf.o: \
> > > $(wildcard $(BPFDIR)/bpf_*.h) \
> > > $(wildcard $(BPFDIR)/*.bpf.h) \
> > > | $(TRUNNER_OUTPUT) $$(BPFOBJ)
> > > - $$(call $(TRUNNER_BPF_BUILD_RULE),$$<,$$@, \
> > > + $$(call $(TRUNNER_BPF_BUILD_RULE),$(TRUNNER_BINARY),$$<,$$@, \
> > > $(TRUNNER_BPF_CFLAGS) \
> > > $$($$<-CFLAGS) \
> > > $$($$<-$2-CFLAGS))
> > > --
> > > 2.34.1
> > >
next prev parent reply other threads:[~2024-07-23 1:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 22:57 [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects Ihor Solodrai
2024-07-19 18:18 ` Andrii Nakryiko
2024-07-19 19:03 ` Ihor Solodrai
2024-07-19 21:54 ` Tony Ambardar
2024-07-19 22:25 ` Andrii Nakryiko
2024-07-19 23:21 ` [PATCH bpf-next v1] selftests/bpf: Fix wrong binary in Makefile log output Tony Ambardar
2024-07-20 0:14 ` bot+bpf-ci
2024-07-20 1:23 ` Eduard Zingerman
2024-07-20 2:57 ` Andrii Nakryiko
2024-07-20 5:23 ` Tony Ambardar
2024-07-23 1:35 ` Tony Ambardar [this message]
2024-07-23 1:37 ` Eduard Zingerman
2024-07-23 20:28 ` Andrii Nakryiko
2024-07-20 5:25 ` [PATCH bpf-next v2] " Tony Ambardar
2024-07-20 5:49 ` bot+bpf-ci
2024-07-22 15:17 ` bot+bpf-ci
2024-07-22 19:58 ` bot+bpf-ci
2024-07-23 1:40 ` bot+bpf-ci
2024-07-23 2:46 ` bot+bpf-ci
2024-07-23 20:30 ` patchwork-bot+netdevbpf
2024-07-19 18:20 ` [PATCH bpf-next v4] selftests/bpf: use auto-dependencies for test objects patchwork-bot+netdevbpf
2024-07-23 0:39 ` Alexei Starovoitov
2024-07-23 0:57 ` Eduard Zingerman
2024-07-23 1:49 ` Eduard Zingerman
2024-07-23 1:50 ` Ihor Solodrai
2024-07-23 19:25 ` Ihor Solodrai
2024-07-23 20:02 ` Andrii Nakryiko
2024-07-23 20:11 ` Ihor Solodrai
2024-09-13 14:51 ` Björn Töpel
2024-09-13 22:33 ` Ihor Solodrai
2024-09-14 10:54 ` Björn Töpel
2024-09-15 4:47 ` Ihor Solodrai
2024-09-15 15:41 ` Björn Töpel
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=Zp8I3aN/bZnka4I+@kodidev-ubuntu \
--to=tony.ambardar@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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