diff options
| author | Waiman Long <[email protected]> | 2020-04-21 13:07:55 +0000 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2020-04-21 15:49:36 +0000 |
| commit | d6c8e949a35d6906d6c03a50e9a9cdf4e494528a (patch) | |
| tree | b3e31a1639e2409c77ed2e1ca85eed35f57d9ffb /tools/perf/scripts/python/compaction-times.py | |
| parent | bdev: Reduce time holding bd_mutex in sync in blkdev_close() (diff) | |
| download | kernel-d6c8e949a35d6906d6c03a50e9a9cdf4e494528a.tar.gz kernel-d6c8e949a35d6906d6c03a50e9a9cdf4e494528a.zip | |
blk-iocost: Fix error on iocost_ioc_vrate_adj
Systemtap 4.2 is unable to correctly interpret the "u32 (*missed_ppm)[2]"
argument of the iocost_ioc_vrate_adj trace entry defined in
include/trace/events/iocost.h leading to the following error:
/tmp/stapAcz0G0/stap_c89c58b83cea1724e26395efa9ed4939_6321_aux_6.c:78:8:
error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token
, u32[]* __tracepoint_arg_missed_ppm
That argument type is indeed rather complex and hard to read. Looking
at block/blk-iocost.c. It is just a 2-entry u32 array. By simplifying
the argument to a simple "u32 *missed_ppm" and adjusting the trace
entry accordingly, the compilation error was gone.
Fixes: 7caa47151ab2 ("blkcg: implement blk-iocost")
Acked-by: Steven Rostedt (VMware) <[email protected]>
Acked-by: Tejun Heo <[email protected]>
Signed-off-by: Waiman Long <[email protected]>
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/compaction-times.py')
0 files changed, 0 insertions, 0 deletions