RFC tracing: Teach FETCH_MTD_symbol to handle per-cpu data
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 11 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | tracing: Don't update sc->addr in update_symbol_cache()kernel/ | +3 | 0 replies | |
| 2/2 | tracing: Teach FETCH_MTD_symbol to handle per-cpu datakernel/ | +18 | 7 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] tracing: Teach FETCH_MTD_symbol to handle per-cpu data
Quoted 6 lines · Masami Hiramatsu
Quoted 4 lines · Oleg Nesterov
@symbol can't be used to dump the per-cpu variables. The same is true for +offset(something) if "something" results in
__percpupointer.
Quoted 8 lines
Quoted 4 lines
With this patch
parse_probe_offset()treats "~" before the numeric offset as "per cpu" mark and stores it in the lowest bit,calc_probe_offset()simply adds per_cpu_offset(smp_processor_id()) if this bit is set.IMHO, if the symbol is a per-cpu symbol, it is meaningless to access the symbol itself. For the symbol(static) percpu, maybe we can use
is_kernel_percpu_address()to check.
No, we can't use is_kernel_percpu_address(), this is another thing. is_kernel_percpu_address(&my_pcpu_var) == F. It is true for &per_cpu(my_pcpu_var), this is not what we need.
Quoted 3 lines
If the symbol is
percpu, it should be automatically translated to something likeFETCH_percpu, instead of such additional expression.
OK. Probably yes, it should be automatically translated, please see the patches.
This doesn't allow to read the data from other CPUs, but at least the changes are simple and this_cpu_ is better than the reading from the obviously wrong address.
Quoted 2 lines
For the dynamic allocated per-cpu things, it is also good to give a straight operation, like +10(percpu(%rdi)).
Probably yes, but this needs more changes and I am still not sure this is really useful. And if we do this, we probably also need to allow to read from other CPUs...
Quoted 1 line
Also, please do not be afraid to add fetch operation,
Well, this is what I am trying to avoid ;)
Oleg.