Home
last modified time | relevance | path

Searched refs:errors (Results 1 – 24 of 24) sorted by relevance

/tools/perf/scripts/perl/
Drw-by-pid.pl36 $reads{$common_pid}{errors}{$ret}++;
58 $writes{$common_pid}{errors}{$ret}++;
102 foreach my $error (keys %{$reads{$pid}{errors}}) {
104 my $errcount = $reads{$pid}{errors}{$error} || 0;
142 foreach my $error (keys %{$writes{$pid}{errors}}) {
144 my $errcount = $writes{$pid}{errors}{$error} || 0;
Drwtop.pl49 $reads{$common_pid}{errors}{$ret}++;
75 $writes{$common_pid}{errors}{$ret}++;
/tools/testing/selftests/powerpc/mm/
Dsubpage_prot.c35 int errors; variable
80 ++errors; in check_faulted()
119 errors = 0; in run_test()
130 if (errors) { in run_test()
131 printf("%d errors detected\n", errors); in run_test()
/tools/testing/selftests/rcutorture/bin/
Dparse-build.sh47 print_bug $title build errors:
58 print_warning $title build errors:
/tools/testing/selftests/media_tests/
Dregression_test.txt43 Run dmesg looking for any user-after free errors or mutex lock errors.
/tools/perf/Documentation/
Dperf-data.txt35 Be more verbose (show counter open errors, etc).
Dperf-list.txt185 can cause measurement errors when the workload changes its execution
190 errors. Event groups can be specified using { }.
Dperf-kvm.txt98 Be more verbose (show counter open errors, etc).
Dperf-top.txt110 Be more verbose (show counter open errors, etc).
Dperf-record.txt240 Be more verbose (show counter open errors, etc).
432 Parse options then exit. --dry-run can be used to detect errors in cmdline
Dperf-stat.txt106 be more verbose (show counter open errors, etc)
Dperf-probe.txt60 Be quiet (do not show any messages including errors).
Dintel-pt.txt115 Another problem that will be experienced is decoder errors. They can be caused
238 starting point for decoding or recovery from errors.
/tools/perf/pmu-events/
DREADME88 In case of errors when processing files in the tools/perf/pmu-events/arch
92 However some errors in processing may cause the perf build to fail.
/tools/perf/util/
Dintel-bts.c401 if (!btsq->bts->synth_opts.errors) in intel_bts_get_branch_type()
647 bts->synth_opts.errors) in intel_bts_process_event()
Dauxtrace.h81 bool errors; member
Dauxtrace.c948 synth_opts->errors = true; in itrace_synth_opts__set_default()
1032 synth_opts->errors = true; in itrace_parse_synth_opts()
Dintel-pt.c1475 if (pt->synth_opts.errors) { in intel_pt_run_decoder()
1806 pt->synth_opts.errors) { in intel_pt_process_event()
/tools/objtool/Documentation/
Dstack-validation.txt331 3. Another possible cause for errors in C code is if the Makefile removes
334 Also see the above section for .S file errors for more information what
/tools/power/cpupower/po/
Dde.po214 msgid "Report errors and bugs to %s, please.\n"
629 "Error setting new values. Common errors:\n"
Dfr.po214 msgid "Report errors and bugs to %s, please.\n"
615 "Error setting new values. Common errors:\n"
Dit.po214 msgid "Report errors and bugs to %s, please.\n"
624 "Error setting new values. Common errors:\n"
Dcs.po217 msgid "Report errors and bugs to %s, please.\n"
618 "Error setting new values. Common errors:\n"
Dpt.po212 msgid "Report errors and bugs to %s, please.\n"
625 "Error setting new values. Common errors:\n"