| /tools/perf/util/ |
| D | values.c | 6 void perf_read_values_init(struct perf_read_values *values) in perf_read_values_init() argument
8 values->threads_max = 16; in perf_read_values_init()
9 values->pid = malloc(values->threads_max * sizeof(*values->pid)); in perf_read_values_init()
10 values->tid = malloc(values->threads_max * sizeof(*values->tid)); in perf_read_values_init()
11 values->value = malloc(values->threads_max * sizeof(*values->value)); in perf_read_values_init()
12 if (!values->pid || !values->tid || !values->value) in perf_read_values_init()
14 values->threads = 0; in perf_read_values_init()
16 values->counters_max = 16; in perf_read_values_init()
17 values->counterrawid = malloc(values->counters_max in perf_read_values_init()
18 * sizeof(*values->counterrawid)); in perf_read_values_init()
[all …]
|
| D | counts.c | 10 struct xyarray *values; in perf_counts__new() local
12 values = xyarray__new(ncpus, nthreads, sizeof(struct perf_counts_values)); in perf_counts__new()
13 if (!values) { in perf_counts__new()
18 counts->values = values; in perf_counts__new()
27 xyarray__delete(counts->values); in perf_counts__delete()
34 xyarray__reset(counts->values); in perf_counts__reset()
|
| D | values.h | 17 void perf_read_values_init(struct perf_read_values *values);
18 void perf_read_values_destroy(struct perf_read_values *values);
20 void perf_read_values_add_value(struct perf_read_values *values,
24 void perf_read_values_display(FILE *fp, struct perf_read_values *values,
|
| D | counts.h | 13 u64 values[3]; member
20 struct xyarray *values; member
27 return xyarray__entry(counts->values, cpu, thread); in perf_counts()
|
| D | stat.c | 267 perf_stat__update_shadow_stats(evsel, count->values, cpu); in process_counter_values()
309 u64 *count = counter->counts->aggr.values; in perf_stat_process_counter()
|
| D | Build | 42 libperf-y += values.o
|
| D | event.h | 121 struct sample_read_value *values; member
|
| D | session.c | 896 value = &sample->read.group.values[i]; in sample_read__printf()
1027 &sample->read.group.values[i], in deliver_sample_group()
|
| D | evsel.c | 1726 data->read.group.values = in perf_evsel__parse_sample()
2063 memcpy(array, sample->read.group.values, sz); in perf_event__synthesize_sample()
|
| /tools/perf/Documentation/ |
| D | callchain-overhead-calculation.txt | 5 adding all period values of the entry - usually a function (symbol).
7 'self' overhead values should be 100%.
9 The 'children' overhead is calculated by adding all period values of
16 values exceeds 100% since each of them is already an accumulation of
64 When the --children option is enabled, the 'self' overhead values of
105 is sorted by its values. The 'children' overhead is disabled by
|
| D | perf-kvm.txt | 106 event to be analyzed. Possible values: vmexit, mmio (x86 only),
110 Sorting key. Possible values: sample (default, sort by samples
141 event to be analyzed. Possible values: vmexit,
147 Sorting key. Possible values: sample (default, sort by samples
|
| D | perf-lock.txt | 50 Sorting key. Possible values: acquired (default), contended,
|
| D | intel-pt.txt | 247 Valid values are given by:
252 valid values e.g. bit 2 set means value 2 is valid.
262 will give a list of valid values e.g.
265 Invalid psb_period for intel_pt. Valid values are: 0-5
297 Valid values are given by:
302 valid values e.g. bit 2 set means value 2 is valid.
311 can be related to TSC via values provided in cpuid leaf 0x15.
314 will give a list of valid values e.g.
317 Invalid mtc_period for intel_pt. Valid values are: 0,3,6,9
342 Valid cyc_thresh values are given by:
[all …]
|
| D | perf-script-perl.txt | 45 Most of the event's field values are passed as arguments to the
181 and values parsed from the 'print fmt' fields of the event format
212 avg($total, $n) - returns average given a sum and a total number of values
|
| D | perf-script-python.txt | 187 and its parameter values to stdout. The print_header() function is
252 values without having to go to the trouble of creating intermediate
262 and having the counts we've tallied as values.
443 Most of the event's field values are passed as arguments to the
576 and values parsed from the 'print fmt' fields of the event format
584 i.e. with autovivifying hashes, you can assign nested hash values
616 avg(total, n) - returns average given a sum and a total number of values
|
| D | perf-stat.txt | 45 Acceptable values for each of 'config', 'config1' and 'config2'
67 scale/normalize counter values
|
| D | perf-record.txt | 47 values for each of 'config', 'config1' and 'config2' are defined by
53 These params can be used to overload default config values per event.
57 - 'time': Disable/enable time stamping. Acceptable values are 1 for
184 the values.
|
| D | perf-diff.txt | 94 Show period values for both compared hist entries.
|
| /tools/perf/tests/ |
| D | sample-parsing.c | 72 MCOMP(read.group.values[i]); in samples_same()
208 struct sample_read_value values[] = {{1, 5}, {9, 3}, {2, 7}, {6, 4},}; in do_test() local
224 sample.read.group.values = values; in do_test()
|
| /tools/perf/tests/attr/ |
| D | README | 10 these files are checked for values we expect for command.
22 separate file. Besides 'struct perf_event_attr' values we also
23 store 'fd' and 'group_fd' values to allow checking for groups.
|
| /tools/usb/usbip/ |
| D | INSTALL | 18 The `configure' shell script attempts to guess correct values for
20 those values to create a `Makefile' in each directory of the package.
80 You can give `configure' initial values for configuration parameters
118 options like `--bindir=DIR' to specify different values for particular
158 See the file `config.sub' for the possible values of each field. If
174 If you want to set default values for `configure' scripts to share, you
176 values for variables like `CC', `cache_file', and `prefix'.
187 configure again during the build, and the customized values of these
|
| /tools/testing/fault-injection/ |
| D | failcmd.sh | 55 The following values for FAILCMD_TYPE are recognized:
|
| /tools/perf/ |
| D | design.txt | 145 tracer is available, and event_id values can be obtained from
156 additional values as specified by 'read_format', each value is a u64 (8 bytes)
169 Using these additional values one can establish the overcommit ratio for a
271 put onto the CPU. This means that the values of the member counters
|
| /tools/power/cpupower/po/ |
| D | de.po | 629 "Error setting new values. Common errors:\n"
|
| D | fr.po | 615 "Error setting new values. Common errors:\n"
|