[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<169101062152.23031.14952859291909120655.git-patchwork-notify@kernel.org>
Date: Wed, 02 Aug 2023 21:10:21 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Pu Lehui <pulehui@...weicloud.com>
Cc: linux-riscv@...ts.infradead.org, bpf@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org, bjorn@...nel.org,
palmer@...belt.com, ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, song@...nel.org, yhs@...com, john.fastabend@...il.com,
kpsingh@...nel.org, sdf@...gle.com, haoluo@...gle.com, jolsa@...nel.org,
guoren@...nel.org, suagrfillet@...il.com, pulehui@...wei.com
Subject: Re: [PATCH v2] riscv,
bpf: Adapt bpf trampoline to optimized riscv ftrace framework
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Fri, 21 Jul 2023 18:06:27 +0800 you wrote:
> From: Pu Lehui <pulehui@...wei.com>
>
> Commit 6724a76cff85 ("riscv: ftrace: Reduce the detour code size to
> half") optimizes the detour code size of kernel functions to half with
> T0 register and the upcoming DYNAMIC_FTRACE_WITH_DIRECT_CALLS of riscv
> is based on this optimization, we need to adapt riscv bpf trampoline
> based on this. One thing to do is to reduce detour code size of bpf
> programs, and the second is to deal with the return address after the
> execution of bpf trampoline. Meanwhile, we need to construct the frame
> of parent function, otherwise we will miss one layer when unwinding.
> The related tests have passed.
>
> [...]
Here is the summary with links:
- [v2] riscv, bpf: Adapt bpf trampoline to optimized riscv ftrace framework
https://git.kernel.org/bpf/bpf-next/c/25ad10658dc1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists