Dynamic ftrace support for s390
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | maccess: add weak attribute to probe_kernel_writemm/ | +1 | 0 replies | |
| 2/4 | arch specific probe_kernel_write() implementationarch/ arch/ | +62 | 0 replies | |
| 3/4 | kprobes: use probe_kernel_writearch/ | +2 | 0 replies | |
| 4/4 | add dynamic ftrace supportarch/ arch/ arch/ +7 more | +276 | 1 reply |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Steven Rostedt |
|---|---|
| 1/4 | |
| 2/4 | |
| 3/4 | |
| 4/4 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH/RFC 0/4] Dynamic ftrace support for s390
This patch series adds dynamic ftrace support for s390.
The first three patches are actually just preparation and cleanup. However the first patch touches common code, because I want to be able to have an arch specific version of probe_kernel_write().
The reason for that is that s390 enables page write protection for the kernel text segment in order to catch random (broken) writes to kernel text. Since write proctection is enabled any probe_kernel_write() call would fail.
Now to solve this, we could disable write protection before writing to the segment and afterwards enable it again (like the x86 specific ftrace code does). Alternatively we could use some s390 special instructions in order to bypass virtual addresses and their protection and directly access the physical page that belongs to the virtual address. That's my preferred solution and why I'd like to be able an arch specific version of probe_kernel_write().
If there are no objections, these patches should go upstream via git-s390 I would guess?
Thanks,
Heiko