diff options
author | Kan Liang <[email protected]> | 2018-01-18 13:26:26 -0800 |
---|---|---|
committer | Arnaldo Carvalho de Melo <[email protected]> | 2018-02-15 09:54:42 -0300 |
commit | 63878a53cedc3df31bd4ba8740a49fa0fc116ac6 (patch) | |
tree | d86d301a89ba91fd4b801fb96989d2baa45f3f63 /tools/perf/scripts/python/call-graph-from-sql.py | |
parent | 3effc2f165a842d640873e29d4c5cc1650143aef (diff) |
perf top: Check per-event overwrite term
Per-event overwrite term is not forbidden in 'perf top', which can bring
problems. Because 'perf top' only support non-overwrite mode now.
Add new rules and check regarding to overwrite term for 'perf top'.
- All events either have same per-event term or don't have per-event
mode setting. Otherwise, it will error out.
- Per-event overwrite term should be consistent as opts->overwrite.
If not, updating the opts->overwrite according to per-event term.
Make it possible to support either non-overwrite or overwrite mode.
The overwrite mode is forbidden now, which will be removed when the
overwrite mode is supported later.
Signed-off-by: Kan Liang <[email protected]>
Acked-by: Jiri Olsa <[email protected]>
Cc: Andi Kleen <[email protected]>
Cc: Jin Yao <[email protected]>
Cc: Namhyung Kim <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Wang Nan <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
[ Renamed perf_top_overwrite_check to perf_top__overwrite_check, to follow existing convention ]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions