From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org, bjorn@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, puranjay@kernel.org,
palmer@dabbelt.com, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v6 0/3] Add 12-argument support for RV64 bpf trampoline
Date: Tue, 02 Jul 2024 14:10:30 +0000 [thread overview]
Message-ID: <171992943017.14973.8310193579957590981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240702121944.1091530-1-pulehui@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 2 Jul 2024 12:19:41 +0000 you wrote:
> This patch adds 12 function arguments support for riscv64 bpf
> trampoline. The current bpf trampoline supports <= sizeof(u64) bytes
> scalar arguments [0] and <= 16 bytes struct arguments [1]. Therefore, we
> focus on the situation where scalars are at most XLEN bits and
> aggregates whose total size does not exceed 2×XLEN bits in the riscv
> calling convention [2].
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/3] riscv, bpf: Add 12-argument support for RV64 bpf trampoline
https://git.kernel.org/bpf/bpf-next/c/6801b0aef79d
- [bpf-next,v6,2/3] selftests/bpf: Factor out many args tests from tracing_struct
https://git.kernel.org/bpf/bpf-next/c/5d52ad36683a
- [bpf-next,v6,3/3] selftests/bpf: Add testcase where 7th argment is struct
https://git.kernel.org/bpf/bpf-next/c/9474f72cd657
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bpf@vger.kernel.org, linux-riscv@lists.infradead.org,
netdev@vger.kernel.org, bjorn@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, puranjay@kernel.org,
palmer@dabbelt.com, pulehui@huawei.com
Subject: Re: [PATCH bpf-next v6 0/3] Add 12-argument support for RV64 bpf trampoline
Date: Tue, 02 Jul 2024 14:10:30 +0000 [thread overview]
Message-ID: <171992943017.14973.8310193579957590981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240702121944.1091530-1-pulehui@huaweicloud.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 2 Jul 2024 12:19:41 +0000 you wrote:
> This patch adds 12 function arguments support for riscv64 bpf
> trampoline. The current bpf trampoline supports <= sizeof(u64) bytes
> scalar arguments [0] and <= 16 bytes struct arguments [1]. Therefore, we
> focus on the situation where scalars are at most XLEN bits and
> aggregates whose total size does not exceed 2×XLEN bits in the riscv
> calling convention [2].
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/3] riscv, bpf: Add 12-argument support for RV64 bpf trampoline
https://git.kernel.org/bpf/bpf-next/c/6801b0aef79d
- [bpf-next,v6,2/3] selftests/bpf: Factor out many args tests from tracing_struct
https://git.kernel.org/bpf/bpf-next/c/5d52ad36683a
- [bpf-next,v6,3/3] selftests/bpf: Add testcase where 7th argment is struct
https://git.kernel.org/bpf/bpf-next/c/9474f72cd657
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-07-02 14:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 12:19 [PATCH bpf-next v6 0/3] Add 12-argument support for RV64 bpf trampoline Pu Lehui
2024-07-02 12:19 ` Pu Lehui
2024-07-02 12:19 ` [PATCH bpf-next v6 1/3] riscv, bpf: " Pu Lehui
2024-07-02 12:19 ` Pu Lehui
2024-07-02 13:40 ` Puranjay Mohan
2024-07-02 13:40 ` Puranjay Mohan
2024-07-05 12:51 ` Puranjay Mohan
2024-07-05 12:51 ` Puranjay Mohan
2024-07-06 2:28 ` Pu Lehui
2024-07-06 2:28 ` Pu Lehui
2024-07-02 12:19 ` [PATCH bpf-next v6 2/3] selftests/bpf: Factor out many args tests from tracing_struct Pu Lehui
2024-07-02 12:19 ` Pu Lehui
2024-07-02 12:19 ` [PATCH bpf-next v6 3/3] selftests/bpf: Add testcase where 7th argment is struct Pu Lehui
2024-07-02 12:19 ` Pu Lehui
2024-07-02 13:57 ` [PATCH bpf-next v6 0/3] Add 12-argument support for RV64 bpf trampoline Jiri Olsa
2024-07-02 13:57 ` Jiri Olsa
2024-07-02 14:10 ` patchwork-bot+netdevbpf [this message]
2024-07-02 14:10 ` 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=171992943017.14973.8310193579957590981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@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-riscv@lists.infradead.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=puranjay@kernel.org \
--cc=sdf@google.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 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.