Home
last modified time | relevance | path

Searched refs:tracking (Results 1 – 8 of 8) sorted by relevance

/tools/perf/tests/
DBuild32 perf-y += switch-tracking.o
33 perf-y += keep-tracking.o
/tools/vm/
Dslabinfo.c94 int tracking; variable
684 tracking = 1; in debug_opt_scan()
708 if (tracking) in debug_opt_scan()
710 tracking = 1; in debug_opt_scan()
777 if (tracking && !s->store_user) { in slab_debug()
783 if (!tracking && s->store_user) { in slab_debug()
/tools/perf/util/
Drecord.c116 if (evsel->tracking && use_comm_exec) in evlist__config()
Devlist.c171 entry->tracking = !entry->core.idx; in evlist__add()
1639 if (evsel->tracking) in evlist__get_tracking_event()
1650 if (tracking_evsel->tracking) in evlist__set_tracking_event()
1655 evsel->tracking = false; in evlist__set_tracking_event()
1658 tracking_evsel->tracking = true; in evlist__set_tracking_event()
Devsel.h113 bool tracking; member
Devsel.c243 evsel->tracking = !idx; in evsel__init()
1094 int track = evsel->tracking; in evsel__config()
/tools/perf/
Ddesign.txt234 The 'comm' bit allows tracking of process comm data on process creation.
283 tracking are logged into a ring-buffer. This ring-buffer is created and
/tools/perf/Documentation/
Dperf-intel-pt.txt710 software event has been introduced that permits tracking events (like mmaps) to
719 23: Test using a dummy software event to keep tracking
724 23: Test using a dummy software event to keep tracking : Ok