BPF List
 help / color / mirror / Atom feed
From: Eduard Zingerman <eddyz87@gmail.com>
To: Puranjay Mohan <puranjay@kernel.org>,
	bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	 kernel-team@fb.com, yonghong.song@linux.dev,
	jose.marchesi@oracle.com
Subject: Re: [RFC bpf-next v2 0/9] no_caller_saved_registers attribute for helper calls
Date: Mon, 08 Jul 2024 10:29:35 -0700	[thread overview]
Message-ID: <f36adfc9c1f4d9f42b22248de42795285e9de161.camel@gmail.com> (raw)
In-Reply-To: <mb61psewk3y75.fsf@kernel.org>

On Mon, 2024-07-08 at 11:44 +0000, Puranjay Mohan wrote:

[...]

> Ran the selftest on riscv-64 on qemu:
> 
>     root@rv-tester:~/bpf# uname -a
>     Linux rv-tester 6.10.0-rc2 #27 SMP Mon Jul  8 09:58:20 UTC 2024 riscv64 riscv64 riscv64 GNU/Linux
>     root@rv-tester:~/bpf# ./test_progs -a verifier_nocsr/canary_arm64_riscv64
>     #496/2   verifier_nocsr/canary_arm64_riscv64:OK
>     #496     verifier_nocsr:OK
>     Summary: 1/1 PASSED, 0 SKIPPED, 0 FAILED
> 
> Tested-by: Puranjay Mohan <puranjay@kernel.org> #riscv64

Great, thank you for testing!

  reply	other threads:[~2024-07-08 17:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 10:23 [RFC bpf-next v2 0/9] no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 1/9] bpf: add a get_helper_proto() utility function Eduard Zingerman
2024-07-09 23:42   ` Andrii Nakryiko
2024-07-10  0:26     ` Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 2/9] bpf: no_caller_saved_registers attribute for helper calls Eduard Zingerman
2024-07-09 23:42   ` Andrii Nakryiko
2024-07-10  3:00     ` Eduard Zingerman
2024-07-10  6:01       ` Andrii Nakryiko
2024-07-10  7:57         ` Eduard Zingerman
2024-07-10 15:36           ` Andrii Nakryiko
2024-07-10 16:15             ` Eduard Zingerman
2024-07-10 17:50               ` Andrii Nakryiko
2024-07-10 18:40                 ` Eduard Zingerman
2024-07-10 18:49                   ` Andrii Nakryiko
2024-07-10 19:03                     ` Eduard Zingerman
2024-07-10 19:16                       ` Andrii Nakryiko
2024-07-10 19:07                   ` Alexei Starovoitov
2024-07-10 19:17                     ` Andrii Nakryiko
2024-07-10 19:01             ` Alexei Starovoitov
2024-07-10  9:46     ` Eduard Zingerman
2024-07-10 15:23       ` Andrii Nakryiko
2024-07-10  1:09   ` Alexei Starovoitov
2024-07-10  3:06     ` Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 3/9] bpf, x86, riscv, arm: no_caller_saved_registers for bpf_get_smp_processor_id() Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 4/9] selftests/bpf: extract utility function for BPF disassembly Eduard Zingerman
2024-07-09 23:46   ` Andrii Nakryiko
2024-07-04 10:23 ` [RFC bpf-next v2 5/9] selftests/bpf: no need to track next_match_pos in struct test_loader Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 6/9] selftests/bpf: extract test_loader->expect_msgs as a data structure Eduard Zingerman
2024-07-04 10:23 ` [RFC bpf-next v2 7/9] selftests/bpf: allow checking xlated programs in verifier_* tests Eduard Zingerman
2024-07-04 10:24 ` [RFC bpf-next v2 8/9] selftests/bpf: __arch_* macro to limit test cases to specific archs Eduard Zingerman
2024-07-09 23:50   ` Andrii Nakryiko
2024-07-04 10:24 ` [RFC bpf-next v2 9/9] selftests/bpf: test no_caller_saved_registers spill/fill removal Eduard Zingerman
2024-07-08 11:44 ` [RFC bpf-next v2 0/9] no_caller_saved_registers attribute for helper calls Puranjay Mohan
2024-07-08 17:29   ` Eduard Zingerman [this message]
2024-07-10  1:18 ` Alexei Starovoitov
2024-07-10  3:35   ` Eduard Zingerman

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=f36adfc9c1f4d9f42b22248de42795285e9de161.camel@gmail.com \
    --to=eddyz87@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jose.marchesi@oracle.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=puranjay@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