s390/bpf: Use direct calls and jumps where possible #9486
Conversation
![kernel-patches-daemon-bpf[bot]](https://avatars.githubusercontent.com/u/70728002?s=60&v=4){kind=small}
|
Upstream branch: 0786654 |
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
c210f22 to
2530e45
Compare
|
Upstream branch: dc0fe95 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
4841deb to
928629d
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
2530e45 to
61c9cef
Compare
|
Upstream branch: c80d797 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
928629d to
564b277
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
61c9cef to
715d6cb
Compare
|
Upstream branch: 3ec8560 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
564b277 to
6ad4f09
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
715d6cb to
506c27a
Compare
|
Upstream branch: 1274163 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
6ad4f09 to
1a68116
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
506c27a to
76c716d
Compare
|
Upstream branch: d87fdb1 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
1a68116 to
059ee3b
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
76c716d to
f3b4b37
Compare
|
Upstream branch: dbe99ea |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
059ee3b to
290ef32
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
f3b4b37 to
bf66d41
Compare
|
Upstream branch: 6850a33 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
290ef32 to
5e9ba6a
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
bf66d41 to
74b5324
Compare
|
Upstream branch: dbe99ea |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
5e9ba6a to
aab100d
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
74b5324 to
c3c6b4b
Compare
|
Upstream branch: 5c42715 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
aab100d to
80a892f
Compare
kernel-patches-daemon-bpf
bot
force-pushed
the
bpf-next_base
branch
from
c3c6b4b to
1a79214
Compare
After the V!=R rework (commit c98d2ec ("s390/mm: Uncouple physical vs virtual address spaces")), all kernel code and related data are allocated within a 4G region, making it possible to use relative addressing in BPF code more extensively. Convert as many indirect calls and jumps to direct calls as possible, namely: * BPF_CALL * __bpf_tramp_enter() * __bpf_tramp_exit() * __bpf_prog_enter() * __bpf_prog_exit() * fentry * fmod_ret * fexit * BPF_TRAMP_F_CALL_ORIG without BPF_TRAMP_F_ORIG_STACK * Trampoline returns without BPF_TRAMP_F_SKIP_FRAME and BPF_TRAMP_F_ORIG_STACK The following indirect calls and jumps remain: * Prog returns * Trampoline returns with BPF_TRAMP_F_SKIP_FRAME or BPF_TRAMP_F_ORIG_STACK * BPF_TAIL_CALL * BPF_TRAMP_F_CALL_ORIG with BPF_TRAMP_F_ORIG_STACK As a result, only one usage of call_r1() remains, so inline it. Signed-off-by: Ilya Leoshkevich <[email protected]>
|
Upstream branch: bf7a6a6 |
kernel-patches-daemon-bpf
bot
force-pushed
the
series/991502=>bpf-next
branch
from
80a892f to
89f9290
Compare
|
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=991502 expired. Closing PR. |
Pull request for series with
subject: s390/bpf: Use direct calls and jumps where possible
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=991502