RFC tracing: Teach FETCH_MTD_{symbol,deref} to handle per-cpu data
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | tracing: Don't mangle sc->addr in update_symbol_cache()kernel/ | +3 | 0 replies | |
| 2/3 | tracing: introduce {calc,parse}_probe_offset() for FETCH_MTD_{symbol,deref}kernel/ | +21 | 0 replies | |
| 3/3 | tracing: Teach FETCH_MTD_{symbol,deref} to handle per-cpu datakernel/ | +32 | 15 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] tracing: Teach FETCH_MTD_{symbol,deref} to handle per-cpu data
Quoted 8 lines · Oleg Nesterov
After I looked at Namhyung's patches I learned that
trace_probeshas a rich set of ->fetch methods.But perhaps it makes sense to add a bit more? The patch is simple and the idea looks natural. If this patch is accepted, I can try to add a bit more hacks to fetch the per-cpu data, but this needs a couple of simple preparations.
Before I redo/resend this patch, let me show the next changes which allow to dump the per-cpu data.
Not for inclusion! I am not sure if this is really useful, I am not sure about the syntax or implementation, etc. Just for discussion, please comment.
Oleg.