Home
last modified time | relevance | path

Searched refs:cgroup (Results 1 – 6 of 6) sorted by relevance

/tools/perf/Documentation/
Dperf-stat.txt111 --cgroup name::
112 monitor only in the container (cgroup) called "name". This option is available only
113 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
115 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
116 to first event, second cgroup to second event and so on. It is possible to provide
117 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
Dperf-record.txt221 --cgroup name,...::
222 monitor only in the container (cgroup) called "name". This option is available only
223 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
225 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
226 to first event, second cgroup to second event and so on. It is possible to provide
227 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
Dintel-pt.txt537 In per-cpu mode all processes (or processes from the selected cgroup i.e. -G
/tools/
DMakefile55 cgroup firewire hv guest usb virtio vm net iio: FORCE target
84 all: acpi cgroup cpupower hv firewire lguest \
/tools/perf/util/
Dpython-ext-sources17 util/cgroup.c
DBuild68 libperf-y += cgroup.o