From: Daniel Borkmann <daniel@iogearbox.net>
To: Pu Lehui <pulehui@huaweicloud.com>,
bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org
Cc: "Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Mykola Lysenko" <mykolal@fb.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Puranjay Mohan" <puranjay@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"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@fomichev.me>,
"Hao Luo" <haoluo@google.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Pu Lehui" <pulehui@huawei.com>
Subject: Re: [PATCH bpf-next v3 00/10] Local vmtest enhancement and RV64 enabled
Date: Thu, 5 Sep 2024 20:52:12 +0200 [thread overview]
Message-ID: <e9816f7c-a603-c73e-5fcc-71bbcf6c6ca3@iogearbox.net> (raw)
In-Reply-To: <20240905081401.1894789-1-pulehui@huaweicloud.com>
On 9/5/24 10:13 AM, Pu Lehui wrote:
> Patch 1-3 fix some problem about bpf selftests. Patch 4 add local rootfs
> image support for vmtest. Patch 5 enable cross-platform testing for
> vmtest. Patch 6-10 enable vmtest on RV64.
>
> We can now perform cross platform testing for riscv64 bpf using the
> following command:
>
> PLATFORM=riscv64 CROSS_COMPILE=riscv64-linux-gnu- \
> tools/testing/selftests/bpf/vmtest.sh \
> -l <path of local rootfs image> -- \
> ./test_progs -d \
> \"$(cat tools/testing/selftests/bpf/DENYLIST.riscv64 \
> | cut -d'#' -f1 \
> | sed -e 's/^[[:space:]]*//' \
> -e 's/[[:space:]]*$//' \
> | tr -s '\n' ',' \
> )\"
>
> For better regression, we rely on commit [0]. And since the work of riscv
> ftrace to remove stop_machine atomic replacement is in progress, we also
> need to revert commit [1] [2].
>
> The test platform is x86_64 architecture, and the versions of relevant
> components are as follows:
> QEMU: 8.2.0
> CLANG: 17.0.6 (align to BPF CI)
> ROOTFS: ubuntu noble (generated by [3])
>
> Link: https://lore.kernel.org/all/20240831071520.1630360-1-pulehui@huaweicloud.com/ [0]
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3308172276db [1]
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7caa9765465f [2]
> Link: https://github.com/libbpf/ci/blob/main/rootfs/mkrootfs_debian.sh [3]
Nice work! Next step is upstream BPF CI integration? :)
Fwiw, all still works for me on x86-64 (*), so:
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
Tested-by: Daniel Borkmann <daniel@iogearbox.net>
(*) fresh Equinix Ubuntu instance still requires this one for vmtest.sh, but
that is independent of this series (and for others it seems not required)
diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
index 04716a5e43f1..02dd161e5185 100644
--- a/tools/testing/selftests/bpf/Makefile
+++ b/tools/testing/selftests/bpf/Makefile
@@ -693,7 +693,7 @@ $(OUTPUT)/$(TRUNNER_BINARY): $(TRUNNER_TEST_OBJS) \
$(TRUNNER_BPFTOOL) \
| $(TRUNNER_BINARY)-extras
$$(call msg,BINARY,,$$@)
- $(Q)$$(CC) $$(CFLAGS) $$(filter %.a %.o,$$^) $$(LDLIBS) $$(LDFLAGS) -o $$@
+ $(Q)$$(CC) $$(CFLAGS) $(TRUNNER_LDFLAGS) $$(filter %.a %.o,$$^) $$(LDLIBS) $$(LDFLAGS) -o $$@
$(Q)$(RESOLVE_BTFIDS) --btf $(TRUNNER_OUTPUT)/btf_data.bpf.o $$@
$(Q)ln -sf $(if $2,..,.)/tools/build/bpftool/$(USE_BOOTSTRAP)bpftool \
$(OUTPUT)/$(if $2,$2/)bpftool
diff --git a/tools/testing/selftests/bpf/vmtest.sh b/tools/testing/selftests/bpf/vmtest.sh
index 79505d294c44..afbd6b785064 100755
--- a/tools/testing/selftests/bpf/vmtest.sh
+++ b/tools/testing/selftests/bpf/vmtest.sh
@@ -189,7 +189,7 @@ update_selftests()
local selftests_dir="${kernel_checkout}/tools/testing/selftests/bpf"
cd "${selftests_dir}"
- ${make_command}
+ TRUNNER_LDFLAGS=-static ${make_command}
# Mount the image and copy the selftests to the image.
mount_image
next prev parent reply other threads:[~2024-09-05 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 8:13 [PATCH bpf-next v3 00/10] Local vmtest enhancement and RV64 enabled Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 01/10] selftests/bpf: Adapt OUTPUT appending logic to lower versions of Make Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 02/10] selftests/bpf: Rename fallback in bpf_dctcp to avoid naming conflict Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 03/10] selftests/bpf: Prefer static linking for LLVM libraries Pu Lehui
2024-09-05 15:29 ` Daniel Borkmann
2024-09-05 8:13 ` [PATCH bpf-next v3 04/10] selftests/bpf: Limit URLS parsing logic to actual scope in vmtest Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 05/10] selftests/bpf: Support local rootfs image for vmtest Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 06/10] selftests/bpf: Enable cross platform testing " Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 07/10] selftests/bpf: Add config.riscv64 Pu Lehui
2024-09-05 8:13 ` [PATCH bpf-next v3 08/10] selftests/bpf: Add DENYLIST.riscv64 Pu Lehui
2024-09-05 8:14 ` [PATCH bpf-next v3 09/10] selftests/bpf: Add riscv64 configurations to local vmtest Pu Lehui
2024-09-05 8:14 ` [PATCH bpf-next v3 10/10] selftests/bpf: Add description for running vmtest on RV64 Pu Lehui
2024-09-05 18:52 ` Daniel Borkmann [this message]
2024-09-06 3:56 ` [PATCH bpf-next v3 00/10] Local vmtest enhancement and RV64 enabled😁 Pu Lehui
2024-09-06 14:08 ` Björn Töpel
2024-09-05 20:20 ` [PATCH bpf-next v3 00/10] Local vmtest enhancement and RV64 enabled patchwork-bot+netdevbpf
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=e9816f7c-a603-c73e-5fcc-71bbcf6c6ca3@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=puranjay@kernel.org \
--cc=sdf@fomichev.me \
--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