Home
last modified time | relevance | path

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

/tools/perf/Documentation/
Dperf-stat.txt95 --cgroup name::
96 monitor only in the container (cgroup) called "name". This option is available only
97 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
99 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
100 to first event, second cgroup to second event and so on. It is possible to provide
101 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
Dperf-record.txt154 --cgroup name,...::
155 monitor only in the container (cgroup) called "name". This option is available only
156 in per-cpu mode. The cgroup filesystem must be mounted. All threads belonging to
158 can be provided. Each cgroup is applied to the corresponding event, i.e., first cgroup
159 to first event, second cgroup to second event and so on. It is possible to provide
160 an empty cgroup (monitor all the time) using, e.g., -G foo,,bar. Cgroups must have
/tools/
DMakefile48 cgroup firewire hv guest usb virtio vm net: FORCE target
69 all: acpi cgroup cpupower hv firewire lguest \
/tools/perf/util/
Dpython-ext-sources17 util/cgroup.c
/tools/perf/
DMakefile.perf292 LIB_H += util/cgroup.h
372 LIB_OBJS += $(OUTPUT)util/cgroup.o