activate & deactivate dprintks individually and severally
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | Move definitions of struct module_sect_attr back into module.h.include/ kernel/ | +15 | 0 replies | |
| 2/5 | Add apply_modules() which applies a function to each module.include/ kernel/ | +14 | 0 replies | |
| 3/5 | Make the dprintk() macro record information about the callsiteinclude/ include/ include/ +4 more | +124 | 0 replies | |
| 4/5 | Add the dprintk module to allow dprintks to be activated/deactivated singlyDocumentation/ init/ kernel/ +1 more | +1131 | 0 replies | |
| 5/5 | Add a module to test the dprintk module.init/ kernel/ kernel/ | +76 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [patch 0/5] activate & deactivate dprintks individually and severally
As mentioned in the recent discussion on NFS trace points on the NFS & SystemTap mailing lists. This patch allows field support staff and kernel developers debug kernel problems, by enabling them to treat dprintks as precise trace points rather than syslog spamming tools.
This is a forward ported (from 2.6.16), updated, and split version of a patch that has been used in SGI's internal development tree for the last few months. The very first version of this was used about eighteen months ago when debugging NFS/RDMA, which has an enormous number of dprintks and no other way to debug it.
Jason Baron suggested I post it here for review and contrast with his dynamic dprintk feature.
Signature · 3 lines
Greg Banks, P.Engineer, SGI Australian Software Group. the brightly coloured sporks of revolution. I don't speak for SGI.