All of lore.kernel.org
 help / color / mirror / Atom feed
From: Varun R Mallya <varunrmallya@gmail.com>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, pulehui@huawei.com,
	alex@ghiti.fr, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
	puranjay@kernel.org, shuah@kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 3/3] riscv, bpf: Remove BPF exceptions from BPF CI denylist
Date: Mon, 6 Jul 2026 14:25:19 +0530	[thread overview]
Message-ID: <akttdwZOqvgj4h39@computer> (raw)
In-Reply-To: <878q7yy28o.fsf@all.your.base.are.belong.to.us>

On Sun, Jun 28, 2026 at 11:00:07AM -0700, Björn Töpel wrote:
> Varun R Mallya <varunrmallya@gmail.com> writes:
> 
> > This patch removes BPF exceptions from riscv64 denylist on
> > BPF selftests since support for exceptions has been added now.
> >
> > Signed-off-by: Varun R Mallya <varunrmallya@gmail.com>
> > Reviewed-by: Pu Lehui <pulehui@huawei.com>
> > ---
> >  tools/testing/selftests/bpf/DENYLIST.riscv64 | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/bpf/DENYLIST.riscv64 b/tools/testing/selftests/bpf/DENYLIST.riscv64
> > index 4fc4dfdde293..9268351ce4c1 100644
> > --- a/tools/testing/selftests/bpf/DENYLIST.riscv64
> > +++ b/tools/testing/selftests/bpf/DENYLIST.riscv64
> > @@ -1,3 +1,2 @@
> >  # riscv64 deny list for BPF CI and local vmtest
> > -exceptions					# JIT does not support exceptions
> 
> Hmm, reading your cover the kselftest run still says "#113
> exceptions:FAIL", so from a CI perspective this is not much help. ;-)
> Can we restructure/split so that we're not bitten by the lack of
> BPF-to-BPF calls and tail calls?

Yeah, that was pretty foolish of me. My next version won't include a
denylist change, but if [1] lands, then we won't have to
worry about this anymore!

[1]: https://lore.kernel.org/bpf/bf647816-d292-419c-b79f-fc048122aebc@huaweicloud.com

> 
> Thanks,
> Björn

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Varun R Mallya <varunrmallya@gmail.com>
To: "Björn Töpel" <bjorn@kernel.org>
Cc: pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	eddyz87@gmail.com, memxor@gmail.com, pulehui@huawei.com,
	alex@ghiti.fr, martin.lau@linux.dev, song@kernel.org,
	yonghong.song@linux.dev, jolsa@kernel.org, emil@etsalapatis.com,
	puranjay@kernel.org, shuah@kernel.org,
	linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 3/3] riscv, bpf: Remove BPF exceptions from BPF CI denylist
Date: Mon, 6 Jul 2026 14:25:19 +0530	[thread overview]
Message-ID: <akttdwZOqvgj4h39@computer> (raw)
In-Reply-To: <878q7yy28o.fsf@all.your.base.are.belong.to.us>

On Sun, Jun 28, 2026 at 11:00:07AM -0700, Björn Töpel wrote:
> Varun R Mallya <varunrmallya@gmail.com> writes:
> 
> > This patch removes BPF exceptions from riscv64 denylist on
> > BPF selftests since support for exceptions has been added now.
> >
> > Signed-off-by: Varun R Mallya <varunrmallya@gmail.com>
> > Reviewed-by: Pu Lehui <pulehui@huawei.com>
> > ---
> >  tools/testing/selftests/bpf/DENYLIST.riscv64 | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/bpf/DENYLIST.riscv64 b/tools/testing/selftests/bpf/DENYLIST.riscv64
> > index 4fc4dfdde293..9268351ce4c1 100644
> > --- a/tools/testing/selftests/bpf/DENYLIST.riscv64
> > +++ b/tools/testing/selftests/bpf/DENYLIST.riscv64
> > @@ -1,3 +1,2 @@
> >  # riscv64 deny list for BPF CI and local vmtest
> > -exceptions					# JIT does not support exceptions
> 
> Hmm, reading your cover the kselftest run still says "#113
> exceptions:FAIL", so from a CI perspective this is not much help. ;-)
> Can we restructure/split so that we're not bitten by the lack of
> BPF-to-BPF calls and tail calls?

Yeah, that was pretty foolish of me. My next version won't include a
denylist change, but if [1] lands, then we won't have to
worry about this anymore!

[1]: https://lore.kernel.org/bpf/bf647816-d292-419c-b79f-fc048122aebc@huaweicloud.com

> 
> Thanks,
> Björn

  reply	other threads:[~2026-07-06  8:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28  8:17 [PATCH bpf-next v2 0/3] Add BPF Exceptions support for RISC-V Varun R Mallya
2026-06-28  8:17 ` Varun R Mallya
2026-06-28  8:17 ` [PATCH bpf-next v2 1/3] riscv: stacktrace: Implement arch_bpf_stack_walk() for BPF Varun R Mallya
2026-06-28  8:17   ` Varun R Mallya
2026-06-28 17:26   ` Björn Töpel
2026-06-28 17:26     ` Björn Töpel
2026-06-29  2:45     ` Pu Lehui
2026-06-29  2:45       ` Pu Lehui
2026-06-28  8:17 ` [PATCH bpf-next v2 2/3] riscv, bpf: Add support for BPF exceptions Varun R Mallya
2026-06-28  8:17   ` Varun R Mallya
2026-06-28 17:50   ` Björn Töpel
2026-06-28 17:50     ` Björn Töpel
2026-06-29  3:01     ` Pu Lehui
2026-06-29  3:01       ` Pu Lehui
2026-06-28  8:17 ` [PATCH bpf-next v2 3/3] riscv, bpf: Remove BPF exceptions from BPF CI denylist Varun R Mallya
2026-06-28  8:17   ` Varun R Mallya
2026-06-28 18:00   ` Björn Töpel
2026-06-28 18:00     ` Björn Töpel
2026-07-06  8:55     ` Varun R Mallya [this message]
2026-07-06  8:55       ` Varun R Mallya

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=akttdwZOqvgj4h39@computer \
    --to=varunrmallya@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=andrii@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=pulehui@huawei.com \
    --cc=puranjay@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.