| /external/strace/ |
| D | strace.1 | 4 .\" Copyright (c) 1996-2017 The strace developers.
42 .\" an-ext.tmac.
44 . ie \\n(.$-1 \
51 . ie \\n(.$-1 \
56 .TH STRACE 1 "2018-07-07" "strace 4.25"
58 strace \- trace system calls and signals
62 .OP \-ACdffhikqrtttTvVxxy
65 .OP \-ACdffhiqrtttTvVxxy
67 .OP \-I n
68 .OP \-b execve
[all …]
|
| D | strace.1.in | 4 .\" Copyright (c) 1996-2017 The strace developers.
42 .\" an-ext.tmac.
44 . ie \\n(.$-1 \
51 . ie \\n(.$-1 \
58 strace \- trace system calls and signals
62 .OP \-ACdffhikqrtttTvVxxy
65 .OP \-ACdffhiqrtttTvVxxy
67 .OP \-I n
68 .OP \-b execve
69 .OM \-e expr
[all …]
|
| /external/libtracefs/Documentation/ |
| D | libtracefs-instances-manage.txt | 5 ----
7 tracefs_instance_is_new, tracefs_instances - Manage trace instances.
10 --------
12 --
22 --
25 -----------
26 This set of functions can be used to manage trace instances. A trace
27 instance is a sub buffer used by the Linux tracing system. Given a unique
29 system, nor other instances, as events enabled in the main tracing system
34 not yet exist in the system, it will be created. The _name_ could be NULL,
[all …]
|
| /external/perfetto/docs/ |
| D | README.md | 1 # Perfetto - System profiling, app tracing and trace analysis
3 Perfetto is a production-grade open-source stack for performance
4 instrumentation and trace analysis. It offers services and libraries for
5 recording system-level and app-level traces, native + java heap profiling, a
6 library for analyzing traces using SQL and a web-based UI to visualize and
7 explore multi-GB traces.
9 
13 At its core, Perfetto introduces a novel userspace-to-userspace
14 [tracing protocol](/docs/design-docs/api-and-abi.md#tracing-protocol-abi) based
16 protocol is used both internally for the built-in data sources and exposed to
[all …]
|
| D | tracing-101.md | 2 *This page provides a birds-eye view of performance analysis.
17 complicated, having a lot of components and a web of cross-interactions.
18 Techniques which help engineers understand the execution of a system
21 **Tracing** and **profiling** are two such widely-used techniques for
22 performance analysis. **Perfetto** is an open-source suite of tools, combining
23 tracing and profiling to give users powerful insights into their system.
27 of a system. A single continuous session of recording is called a trace file
28 or **trace** for short.
31 They often include low-level kernel events like scheduler context switches,
32 thread wakeups, syscalls, etc. With the "right" trace, reproduction of a
[all …]
|
| /external/perfetto/docs/instrumentation/ |
| D | tracing-sdk.md | 4 to emit trace events and add more app-specific context to a Perfetto trace.
9 or want to collect full-stack traces that overlay app trace events with
10 system trace events like scheduler traces, syscalls or any other Perfetto
13 2. For app-specific tracing, whether you need to trace simple types of timeline
15 custom strongly-typed schema (e.g., for dumping the state of a subsystem of
16 your app into the trace).
18 For Android-only instrumentation, the advice is to keep using the existing
19 [android.os.Trace (SDK)][atrace-sdk] / [ATrace_* (NDK)][atrace-ndk] if they
20 are sufficient for your use cases. Atrace-based instrumentation is fully
22 See the [Data Sources -> Android System -> Atrace Instrumentation][atrace-ds]
[all …]
|
| /external/perfetto/docs/quickstart/ |
| D | chrome-tracing.md | 5 …Android, follow the [instructions for recording Android system traces](/docs/quickstart/android-tr…
7 …h), you'll have to enable integration with system Perfetto by switching chrome://flags#enable-perf…
9 ## Recording a trace
11 1. Navigate to [ui.perfetto.dev](https://ui.perfetto.dev/) and select **"Record new trace"** from t…
12 …etto UI Chrome extension](https://chrome.google.com/webstore/detail/perfetto-ui/lfmkphfpdbjijhpomg…
13 2. Select **"Chrome"** as **"Target platform"** in the drop-down.
15 …On Chrome OS, you can also record system traces by selecting the "Chrome OS (system trace)" target…
18 
20 >Note: "Long trace" mode is not yet available for Chrome desktop.
24 > - To save the current config settings and apply them later go to the "Saved configs" menu.
[all …]
|
| D | linux-tracing.md | 3 Perfetto can capture system traces on Linux. All ftrace-based data sources
4 and most other procfs / sysfs-based data sources are supported.
18 tools/install-build-deps
24 tools/gn gen --args='is_debug=false' out/linux
30 tools/ninja -C out/linux tracebox traced traced_probes perfetto
33 ## Capturing a trace
35 Due to Perfetto's [service-based architecture](/docs/concepts/service-model.md),
36 in order to capture a trace, the `traced` (session daemon) and `traced_probes`
37 (probes and ftrace-interop daemon) need to be running.
41 #### Capturing a trace with ftrace and /proc pollers, no SDK argument
[all …]
|
| D | android-tracing.md | 3 Perfetto allows you to collect system-wide performance traces from Android
9 Perfetto is based on [platform services](/docs/concepts/service-model.md)
16 # Needed only on Android 9 (P) and 10 (Q) on non-Pixel phones.
21 trace with Perfetto using the `record_android_trace` script. See instructions
23 [Recording a trace through the cmdline](#recording-a-trace-through-the-cmdline)
26 ## Recording a trace
31 * Using directly the `/system/bin/perfetto` command on device [[reference](/docs/reference/perfetto…
36 * Using the on-device [System Tracing App](https://developer.android.com/topic/performance/tracing/…
38 ### Recording a trace through the Perfetto UI argument
41 **Record new trace** from the left menu.
[all …]
|
| /external/trace-cmd/Documentation/trace-cmd/ |
| D | trace-cmd-list.1.txt | 1 TRACE-CMD-LIST(1)
5 ----
6 trace-cmd-list - list available plugins, events or options for Ftrace.
9 --------
10 *trace-cmd list* ['OPTIONS']
13 -----------
14 The trace-cmd(1) list displays the available plugins, events or Ftrace options
19 -------
20 *-e* ['regex']::
22 local system.
[all …]
|
| D | trace-cmd-dump.1.txt | 1 TRACE-CMD-DUMP(1)
5 ----
6 trace-cmd-dump - show a meta data from a trace file, created by trace-cmd record
9 --------
10 *trace-cmd dump* ['OPTIONS'] ['input-file']
13 -----------
14 The trace-cmd(1) dump command will display the meta data from a trace file
15 created by trace-cmd record.
18 -------
19 *-i* 'input-file'::
[all …]
|
| /external/tensorflow/tensorflow/lite/tools/benchmark/android/ |
| D | README.md | 6 [command-line benchmark utility](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/li…
14 enabling multi-threaded CPU execution with TensorFlow Lite.
29 bazel build -c opt \
30 --config=android_arm64 \
34 (Optional) To enable Hexagon delegate with `--use_hexagon=true` option, you can
57 adb install -r -d -g bazel-bin/tensorflow/lite/tools/benchmark/android/benchmark_model.apk
60 Note: Make sure to install with "-g" option to grant the permission for reading
69 (4) Run the benchmark. Additional command-line flags are documented
71 and can be appended to the `args` string alongside the required `--graph` flag
76 adb shell am start -S \
[all …]
|
| /external/bcc/man/man8/ |
| D | trace.8 | 1 .TH trace 8 "2016-02-18" "USER COMMANDS"
3 trace \- Trace a function and print its arguments or return value, optionally evaluating a filter. …
5 .B trace [-h] [-b BUFFER_PAGES] [-p PID] [-L TID] [--uid UID] [-v] [-Z STRING_SIZE] [-S] [-s SYM_FI…
6 [-M MAX_EVENTS] [-t] [-u] [-T] [-C] [-K] [-U] [-a] [-I header] [-A]
9 trace probes functions you specify and displays trace messages if a particular
18 \-h
21 \-p PID
22 Trace only functions in the process PID.
24 \-L TID
25 Trace only functions in the thread TID.
[all …]
|
| D | fileslower.8 | 1 .TH fileslower 8 "2016-02-07" "USER COMMANDS"
3 fileslower \- Trace slow synchronous file reads and writes.
5 .B fileslower [\-h] [\-p PID] [-a] [min_ms]
9 system.
14 system request types: file reads and writes. There are typically many others:
30 \-p PID
31 Trace this PID only.
33 \-a
34 Include non-regular file types in output (sockets, FIFOs, etc).
37 Minimum I/O latency (duration) to trace, in milliseconds. Default is 10 ms.
[all …]
|
| D | btrfsslower.8 | 1 .TH btrfsslower 8 "2016-02-15" "USER COMMANDS"
3 btrfsslower \- Trace slow btrfs file operations, with per-event details.
5 .B btrfsslower [\-h] [\-j] [\-p PID] [min_ms] [\-d DURATION]
23 \-p PID
24 Trace this PID only.
27 Minimum I/O latency (duration) to trace, in milliseconds. Default is 10 ms.
29 \-d DURATION
30 Total duration of trace in seconds.
33 Trace synchronous file reads and writes slower than 10 ms:
37 Trace slower than 1 ms:
[all …]
|
| /external/robolectric/resources/src/main/java/org/robolectric/res/android/ |
| D | NativeObjRegistry.java | 58 System.out.printf("NativeObjRegistry %s: register %d -> %s%n", name, nativeId, o); in getNativeObjectId()
78 System.out.printf( in register()
79 "NativeObjRegistry %s: register %d -> %s already registered:%n", name, nativeId, o); in register()
80 debugInfo.registrationTrace.printStackTrace(System.out); in register()
88 System.out.printf("NativeObjRegistry %s: register %d -> %s%n", name, nativeId, o); in register()
89 idToDebugInfoMap.put(nativeId, new DebugInfo(new Trace())); in register()
106 System.out.printf("NativeObjRegistry %s: unregister %d -> %s%n", name, nativeId, o); in unregister()
107 new RuntimeException("unregister debug").printStackTrace(System.out); in unregister()
112 debugInfo.unregistrationTraces.add(new Trace()); in unregister()
114 System.out.format("NativeObjRegistry %s: Too many unregistrations:%n", name); in unregister()
[all …]
|
| /external/strace/tests-mx32/ |
| D | filtering_syscall-syntax.test | 5 # Copyright (c) 2016-2018 Dmitry V. Levin <ldv@altlinux.org>
35 [ -z "$2" ] || check_e "invalid system call '$1'" -e"$2"
37 check_e "invalid system call '$1'" -e "$2"
38 check_e "invalid system call '$1'" -etrace="$2"
39 check_e "invalid system call '$1'" -e trace="$2"
41 check_e "invalid system call '$1'" -eabbrev="$2"
42 check_e "invalid system call '$1'" -e abbrev="$2"
44 check_e "invalid system call '$1'" -everbose="$2"
45 check_e "invalid system call '$1'" -e verbose="$2"
47 check_e "invalid system call '$1'" -eraw="$2"
[all …]
|
| /external/strace/tests-m32/ |
| D | filtering_syscall-syntax.test | 5 # Copyright (c) 2016-2018 Dmitry V. Levin <ldv@altlinux.org>
35 [ -z "$2" ] || check_e "invalid system call '$1'" -e"$2"
37 check_e "invalid system call '$1'" -e "$2"
38 check_e "invalid system call '$1'" -etrace="$2"
39 check_e "invalid system call '$1'" -e trace="$2"
41 check_e "invalid system call '$1'" -eabbrev="$2"
42 check_e "invalid system call '$1'" -e abbrev="$2"
44 check_e "invalid system call '$1'" -everbose="$2"
45 check_e "invalid system call '$1'" -e verbose="$2"
47 check_e "invalid system call '$1'" -eraw="$2"
[all …]
|
| /external/strace/tests/ |
| D | filtering_syscall-syntax.test | 5 # Copyright (c) 2016-2018 Dmitry V. Levin <ldv@altlinux.org>
35 [ -z "$2" ] || check_e "invalid system call '$1'" -e"$2"
37 check_e "invalid system call '$1'" -e "$2"
38 check_e "invalid system call '$1'" -etrace="$2"
39 check_e "invalid system call '$1'" -e trace="$2"
41 check_e "invalid system call '$1'" -eabbrev="$2"
42 check_e "invalid system call '$1'" -e abbrev="$2"
44 check_e "invalid system call '$1'" -everbose="$2"
45 check_e "invalid system call '$1'" -e verbose="$2"
47 check_e "invalid system call '$1'" -eraw="$2"
[all …]
|
| /external/opencensus-java/contrib/log_correlation/stackdriver/src/test/java/io/opencensus/contrib/logcorrelation/stackdriver/ |
| D | OpenCensusTraceLoggingEnhancerTest.java | 8 * http://www.apache.org/licenses/LICENSE-2.0
27 import io.opencensus.trace.Annotation;
28 import io.opencensus.trace.AttributeValue;
29 import io.opencensus.trace.BlankSpan;
30 import io.opencensus.trace.EndSpanOptions;
31 import io.opencensus.trace.Link;
32 import io.opencensus.trace.Span;
33 import io.opencensus.trace.SpanContext;
34 import io.opencensus.trace.SpanId;
35 import io.opencensus.trace.TraceId;
[all …]
|
| /external/bcc/tools/ |
| D | trace_example.txt | 1 Demonstrations of trace.
4 trace probes functions you specify and displays trace messages if a particular
8 For example, suppose you want to trace all commands being exec'd across the
9 system:
11 # trace 'sys_execve "%s", arg1'
12 PID COMM FUNC -
32 to be the command that is exec'd. The above trace was generated by executing
36 Next, suppose you are looking for large reads across the system. Let's trace
37 the read system call and inspect the third argument, which is the number of
40 # trace 'sys_read (arg3 > 20000) "read %d bytes", arg3'
[all …]
|
| /external/perfetto/docs/data-sources/ |
| D | atrace.md | 1 # ATrace: Android system and app trace events
3 On Android, native and managed apps can inject custom slices and counter trace
4 points into the trace. This is possible through the following:
6 * Java/Kotlin apps (SDK): `android.os.Trace`.
7 See https://developer.android.com/reference/android/os/Trace.
10 in `<trace.h>`. See https://developer.android.com/ndk/reference/group/tracing.
13 [`libcutils/trace.h`][libcutils].
19 There are two types of atrace events: System and App events.
21 **System events**: are emitted only by Android internals using libcutils.
28 without having to worry about which particular system process emits them.
[all …]
|
| /external/perfetto/examples/sdk/ |
| D | README.md | 4 SDK](https://perfetto.dev/docs/instrumentation/tracing-sdk). It demonstrates
10 - [CMake](https://cmake.org/)
11 - C++17
18 git clone https://android.googlesource.com/platform/external/perfetto -b v34.0
25 cmake -B build
26 cmake --build build
30 `cd perfetto ; tools/gen_amalgamated --output sdk/perfetto`.
31 [Learn more](https://perfetto.dev/docs/contributing/sdk-releasing#building-and-tagging-the-release)
43 The program will create a trace file in `example.perfetto-trace`, which can be
47 ![Example trace loaded in the Perfetto UI](
[all …]
|
| /external/python/google-api-python-client/docs/dyn/ |
| D | apigee_v1.organizations.environments.traceConfig.overrides.html | 8 font-weight: inherit;
9 font-style: inherit;
10 font-size: 100%;
11 font-family: inherit;
12 vertical-align: baseline;
16 font-size: 13px;
21 font-size: 26px;
22 margin-bottom: 1em;
26 font-size: 24px;
27 margin-bottom: 1em;
[all …]
|
| /external/robolectric-shadows/resources/src/main/java/org/robolectric/res/android/ |
| D | NativeObjRegistry.java | 58 System.out.printf("NativeObjRegistry %s: register %d -> %s%n", name, nativeId, o); in getNativeObjectId()
78 System.out.printf( in register()
79 "NativeObjRegistry %s: register %d -> %s already registered:%n", name, nativeId, o); in register()
80 debugInfo.registrationTrace.printStackTrace(System.out); in register()
88 System.out.printf("NativeObjRegistry %s: register %d -> %s%n", name, nativeId, o); in register()
89 idToDebugInfoMap.put(nativeId, new DebugInfo(new Trace(o))); in register()
106 System.out.printf("NativeObjRegistry %s: unregister %d -> %s%n", name, nativeId, o); in unregister()
107 new RuntimeException("unregister debug").printStackTrace(System.out); in unregister()
112 debugInfo.unregistrationTraces.add(new Trace(o)); in unregister()
114 System.out.format("NativeObjRegistry %s: Too many unregistrations:%n", name); in unregister()
[all …]
|