bpf: Yet another approach to fix the BPF dispatcher thing
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 3 repliesIn review 1 of 2 applied
Patches in v1 1 of 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop")arch/ include/ kernel/ | +1 | 0 replies | |
| 2/2 | bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace)include/ kernel/ | +46 | 1 reply | Applied |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Björn Töpel | Jiri Olsa | Steven Rostedt (Google) |
|---|---|---|---|
| Series | A-b T-b | A-b T-b | |
| 1/2 | |||
| 2/2 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing
Hi!
Even thought the __attribute__((patchable_function_entry())) solution to the BPF dispatcher woes works, it turns out to not be supported by the whole range of ageing compilers we support. Specifically this attribute seems to be GCC-8 and later.
This is another approach -- using static_call() to rewrite the dispatcher function. I've compile tested this on:
x86_64 (inline static-call support)
i386 (out-of-line static-call support)
aargh64 (no static-call support)
A previous version was tested and found working by Bjorn.
It is split in two patches; first reverting the current approach and then introducing the new for ease of review.