From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: George Guo <dongtai.guo@linux.dev>,
Huacai Chen <chenhuacai@kernel.org>,
Hengqi Chen <hengqi.chen@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
Jiri Olsa <jolsa@kernel.org>, George Guo <guodongtai@kylinos.cn>,
bpf@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 11/11] selftests/bpf: Add LoongArch deny list
Date: Mon, 6 Jul 2026 14:37:58 +0800 [thread overview]
Message-ID: <eb26a22c-7c64-6d4b-da22-297917702849@loongson.cn> (raw)
In-Reply-To: <20260702022322.51033-12-dongtai.guo@linux.dev>
On 2026/7/2 上午10:23, George Guo wrote:
> From: George Guo <guodongtai@kylinos.cn>
>
> Add an empty test_progs deny list for LoongArch, mirroring the other
> architectures, so BPF CI and local vmtest have a place to record cases
> that cannot pass on LoongArch.
>
> Signed-off-by: George Guo <guodongtai@kylinos.cn>
> ---
> tools/testing/selftests/bpf/DENYLIST.loongarch | 1 +
> 1 file changed, 1 insertion(+)
> create mode 100644 tools/testing/selftests/bpf/DENYLIST.loongarch
>
> diff --git a/tools/testing/selftests/bpf/DENYLIST.loongarch b/tools/testing/selftests/bpf/DENYLIST.loongarch
> new file mode 100644
> index 000000000000..70cc007e396e
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/DENYLIST.loongarch
> @@ -0,0 +1 @@
> +# loongarch64 deny list for BPF CI and local vmtest
LoongArch doesn't have an active BPF CI yet,
there is no need to add an empty DENYLIST.
If there are already known test failures on LoongArch,
it would be much more valuable to either:
1. Fix those failures directly, or
2. Report those failures.
We should only consider adding CI after all current
test failures are resolved.
Thanks,
Tiezhu
next prev parent reply other threads:[~2026-07-06 6:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 2:23 [PATCH bpf-next v2 00/11] LoongArch: BPF: arena features, exceptions, private stack and may_goto George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 01/11] LoongArch: BPF: Fix tail call count pointer offset for arena programs George Guo
2026-07-06 4:55 ` Tiezhu Yang
2026-07-07 9:43 ` George Guo
2026-07-07 10:12 ` Tiezhu Yang
2026-07-02 2:23 ` [PATCH bpf-next v2 02/11] LoongArch: BPF: Support internal-only MOV to resolve per-CPU addrs George Guo
2026-07-06 6:46 ` Tiezhu Yang
2026-07-07 10:22 ` George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 03/11] LoongArch: BPF: Add timed may_goto support George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 04/11] LoongArch: BPF: Add private stack support George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 05/11] LoongArch: BPF: Add exceptions (bpf_throw) support George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 06/11] LoongArch: BPF: Support sign-extending loads from arena George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 07/11] LoongArch: BPF: Support atomics on arena pointers George Guo
2026-07-06 7:06 ` Tiezhu Yang
2026-07-07 10:55 ` George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 08/11] selftests/bpf: Enable struct_ops private stack test for LoongArch George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 09/11] selftests/bpf: Enable arena LDSX tests on LoongArch George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 10/11] selftests/bpf: Enable arena atomics " George Guo
2026-07-02 2:23 ` [PATCH bpf-next v2 11/11] selftests/bpf: Add LoongArch deny list George Guo
2026-07-06 6:37 ` Tiezhu Yang [this message]
2026-07-03 10:11 ` [PATCH bpf-next v2 00/11] LoongArch: BPF: arena features, exceptions, private stack and may_goto Huacai Chen
2026-07-06 7:15 ` Tiezhu Yang
2026-07-07 11:25 ` George Guo
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=eb26a22c-7c64-6d4b-da22-297917702849@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dongtai.guo@linux.dev \
--cc=eddyz87@gmail.com \
--cc=guodongtai@kylinos.cn \
--cc=hengqi.chen@gmail.com \
--cc=jolsa@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--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