| /external/rust/crates/tracing/ |
| D | README.md | 1 ![Tracing — Structured, application-level diagnostics][splash]
3 [splash]: https://raw.githubusercontent.com/tokio-rs/tracing/master/assets/splash.svg
5 # tracing chapter
7 Application-level tracing for Rust.
18 [crates-badge]: https://img.shields.io/crates/v/tracing.svg
19 [crates-url]: https://crates.io/crates/tracing
20 [docs-badge]: https://docs.rs/tracing/badge.svg
21 [docs-url]: https://docs.rs/tracing
23 [docs-master-url]: https://tracing-rs.netlify.com/tracing
26 [actions-badge]: https://github.com/tokio-rs/tracing/workflows/CI/badge.svg
[all …]
|
| D | CHANGELOG.md | 3 This release of `tracing` incorporates changes from `tracing-core`
4 [v0.1.30][core-0.1.30] and `tracing-attributes` [v0.1.23][attrs-0.1.23],
8 `bare_trait_objects` lint, which is now a warning on `tracing`'s MSRV and will
28 - `tracing-core`: updated to [0.1.30][core-0.1.30]
29 - `tracing-attributes`: updated to [0.1.23][attrs-0.1.23]
33 - Added [`tracing-web`] and [`reqwest-tracing`] to related crates ([#2283],
40 [core-0.1.30]: https://github.com/tokio-rs/tracing/releases/tag/tracing-core-0.1.30
41 [attrs-0.1.23]: https://github.com/tokio-rs/tracing/releases/tag/tracing-attributes-0.1.23
42 [`tracing-web`]: https://crates.io/crates/tracing-web/
43 [`reqwest-tracing`]: https://crates.io/crates/reqwest-tracing/
[all …]
|
| /external/bcc/tools/ |
| D | reset-trace_example.txt | 5 signals, like SIGTERM), or if a bcc tool crashes, then kernel tracing can be
8 used to clean up the tracing state, and reset and disable active tracing.
10 WARNING: Make sure no other tracing sessions are active, as it will likely
14 /sys/kernel/debug/tracing: kprobe_events, uprobe_events, trace_pipe.
15 Other tracing facilities (ftrace) are checked, and if not in an expected state,
16 a note is printed. All tracing files can be reset with -F for force, but this
17 will interfere with any other running tracing sessions (eg, ftrace).
30 Resetting tracing state...
32 Checking /sys/kernel/debug/tracing/kprobe_events
33 Checking /sys/kernel/debug/tracing/uprobe_events
[all …]
|
| D | reset-trace.sh | 3 # reset-trace - reset state of tracing, disabling all tracing.
6 # If a bcc tool crashed and you suspect tracing is partially enabled, you
7 # can use this tool to reset the state of tracing, disabling anything still
11 # bcc-used tracing facilities are reset. Other tracing facilities (ftrace) are
12 # checked, and if not in an expected state, a note is printed. All tracing
14 # running tracing sessions (eg, ftrace).
26 tracing=/sys/kernel/debug/tracing
32 -F # force: reset all tracing files
37 reset-trace # disable semi-enabled tracing
95 echo "Noticed unrelated tracing file $PWD/$file isn't set as" \
[all …]
|
| /external/chromium-trace/catapult/systrace/systrace/ |
| D | tracing_controller.py | 7 '''Tracing controller class. This class manages
8 multiple tracing agents and collects data from all of them. It also
29 """Record the clock sync marker for controller tracing agent.
31 Unlike with the other tracing agents, the tracing controller should not
33 tracing agents when they write a trace.
45 """Start tracing for the controller tracing agent.
47 Start tracing for the controller tracing agent. Note that
48 the tracing controller records the "controller side"
64 """Stops tracing for the controller tracing agent.
74 """Gets the log output from the controller tracing agent.
[all …]
|
| /external/rust/crates/tracing/src/ |
| D | lib.rs | 5 //! `tracing` is a framework for instrumenting Rust programs to collect
11 //! trace the logic flow. `tracing` expands upon logging-style diagnostics by
14 //! in `tracing` has a beginning and end time, may be entered and exited by the
16 //! addition, `tracing` spans are *structured*, with the ability to record typed
19 //! The `tracing` crate provides the APIs necessary for instrumenting libraries
27 //! The core of `tracing`'s API is composed of _spans_, _events_ and
32 //! To record the flow of execution through a program, `tracing` introduces the
42 //! use tracing::{span, Level};
73 //! use tracing::{event, span, Level};
119 //! tracing = "0.1"
[all …]
|
| /external/rust/crates/tracing-core/ |
| D | README.md | 1 ![Tracing — Structured, application-level diagnostics][splash]
3 [splash]: https://raw.githubusercontent.com/tokio-rs/tracing/master/assets/splash.svg
5 # tracing-core
7 Core primitives for application-level tracing.
18 [crates-badge]: https://img.shields.io/crates/v/tracing-core.svg
19 [crates-url]: https://crates.io/crates/tracing-core/0.1.30
20 [docs-badge]: https://docs.rs/tracing-core/badge.svg
21 [docs-url]: https://docs.rs/tracing-core/0.1.30
23 [docs-master-url]: https://tracing-rs.netlify.com/tracing_core
26 [actions-badge]: https://github.com/tokio-rs/tracing/workflows/CI/badge.svg
[all …]
|
| D | CHANGELOG.md | 3 This release of `tracing-core` adds a new `on_register_dispatch` method to the
16 [#2269]: https://github.com/tokio-rs/tracing/pull/2269
17 [#2293]: https://github.com/tokio-rs/tracing/pull/2293
21 This release of `tracing-core` adds `PartialEq` and `Eq` implementations for
38 [#2229]: https://github.com/tokio-rs/tracing/pull/2229
39 [#2246]: https://github.com/tokio-rs/tracing/pull/2246
40 [#2250]: https://github.com/tokio-rs/tracing/pull/2250
44 This release of `tracing-core` adds new `Value` implementations, including one
62 [#2164]: https://github.com/tokio-rs/tracing/pull/2164
63 [#2166]: https://github.com/tokio-rs/tracing/pull/2166
[all …]
|
| /external/rust/crates/tracing-attributes/ |
| D | README.md | 1 ![Tracing — Structured, application-level diagnostics][splash]
3 [splash]: https://raw.githubusercontent.com/tokio-rs/tracing/master/assets/splash.svg
5 # tracing-attributes
7 Macro attributes for application-level tracing.
18 [crates-badge]: https://img.shields.io/crates/v/tracing-attributes.svg
19 [crates-url]: https://crates.io/crates/tracing-attributes
20 [docs-badge]: https://docs.rs/tracing-attributes/badge.svg
21 [docs-url]: https://docs.rs/tracing-attributes/0.1.23
23 [docs-master-url]: https://tracing-rs.netlify.com/tracing_attributes
26 [actions-badge]: https://github.com/tokio-rs/tracing/workflows/CI/badge.svg
[all …]
|
| D | CHANGELOG.md | 3 This release of `tracing-attributes` fixes a bug where compiler diagnostic spans
18 [#2307]: https://github.com/tokio-rs/tracing/pull/2307
19 [#2270]: https://github.com/tokio-rs/tracing/pull/2270
20 [#2246]: https://github.com/tokio-rs/tracing/pull/2246
42 [#2184]: https://github.com/tokio-rs/tracing/pull/2184
43 [#2119]: https://github.com/tokio-rs/tracing/pull/2119
67 [#2093]: https://github.com/tokio-rs/tracing/pull/2093
68 [#2091]: https://github.com/tokio-rs/tracing/pull/2091
69 [#2090]: https://github.com/tokio-rs/tracing/pull/2090
70 [#2077]: https://github.com/tokio-rs/tracing/pull/2077
[all …]
|
| /external/perfetto/include/perfetto/ |
| D | tracing.h | 21 // Tracing API. Embedders should preferably use this one header to avoid having
27 #include "perfetto/tracing/buffer_exhausted_policy.h"
28 #include "perfetto/tracing/console_interceptor.h"
29 #include "perfetto/tracing/core/data_source_config.h"
30 #include "perfetto/tracing/core/data_source_descriptor.h"
31 #include "perfetto/tracing/core/trace_config.h"
32 #include "perfetto/tracing/data_source.h"
33 #include "perfetto/tracing/interceptor.h"
34 #include "perfetto/tracing/platform.h"
35 #include "perfetto/tracing/tracing.h"
[all …]
|
| /external/perfetto/docs/ |
| D | README.md | 1 # Perfetto - System profiling, app tracing and trace analysis
14 [tracing protocol](/docs/design-docs/api-and-abi.md#tracing-protocol-abi) based
15 on direct protobuf serialization onto a shared memory buffer. The tracing
17 C++ apps through the [Tracing SDK](/docs/instrumentation/tracing-sdk.md) and the
20 This new tracing protocol allows dynamic configuration of all aspects of tracing
29 ### System-wide tracing on Android and Linux
36 * [Kernel tracing](/docs/data-sources/cpu-scheduling.md): Perfetto integrates
59 On Android, Perfetto is the next-generation system tracing system and replaces
63 See [Android developer docs](https://developer.android.com/topic/performance/tracing)
66 ### Tracing SDK and user-space instrumentation
[all …]
|
| D | tracing-101.md | 1 # Tracing 101
3 The aim is to orient people who have no idea what "tracing" is.*
21 **Tracing** and **profiling** are two such widely-used techniques for
23 tracing and profiling to give users powerful insights into their system.
25 ### Tracing subsection
26 **Tracing** involves collecting highly detailed data about the execution
49 #### Logging vs tracing
51 tracing is to performance analysis. Tracing is, in a sense, "structured"
53 tracing reflects the detailed state of a system in a structured way to allow
56 Moreover, tracing frameworks (like Perfetto) place heavy emphasis
[all …]
|
| /external/rust/crates/tracing/tests/ |
| D | macro_imports.rs | 1 use tracing::Level;
6 tracing::span!(Level::DEBUG, "foo"); in prefixed_span_macros()
7 tracing::trace_span!("foo"); in prefixed_span_macros()
8 tracing::debug_span!("foo"); in prefixed_span_macros()
9 tracing::info_span!("foo"); in prefixed_span_macros()
10 tracing::warn_span!("foo"); in prefixed_span_macros()
11 tracing::error_span!("foo"); in prefixed_span_macros()
17 tracing::event!(Level::DEBUG, "foo"); in prefixed_event_macros()
18 tracing::trace!("foo"); in prefixed_event_macros()
19 tracing::debug!("foo"); in prefixed_event_macros()
[all …]
|
| D | span.rs | 8 use tracing::{
23 let foo1 = tracing::span!(Level::TRACE, "foo"); in handles_to_the_same_span_are_equal()
36 let foo1 = tracing::span!(Level::TRACE, "foo", bar = 1u64, baz = false); in handles_to_different_spans_are_not_equal()
37 let foo2 = tracing::span!(Level::TRACE, "foo", bar = 1u64, baz = false); in handles_to_different_spans_are_not_equal()
49 tracing::span!(Level::TRACE, "foo", bar = 1u64, baz = false) in handles_to_different_spans_with_the_same_metadata_are_not_equal()
75 let foo = tracing::span!(Level::TRACE, "foo"); in spans_always_go_to_the_subscriber_that_tagged_them()
100 let foo = tracing::span!(Level::TRACE, "foo"); in spans_always_go_to_the_subscriber_that_tagged_them_even_across_threads()
126 let span = tracing::span!(Level::TRACE, "foo"); in dropping_a_span_calls_drop_span()
145 tracing::span!(Level::TRACE, "foo").in_scope(|| { in span_closes_after_event()
146 tracing::event!(Level::DEBUG, {}, "my tracing::event!"); in span_closes_after_event()
[all …]
|
| /external/cronet/base/trace_event/ |
| D | tracing_agent.h | 20 // A tracing agent is an entity that records its own sort of trace. Each
21 // tracing method that produces its own trace log should implement this
22 // interface. All tracing agents must only be controlled by TracingController.
43 // Gets the name of the tracing agent. Each tracing agent's name should be
47 // Gets the trace event label of this tracing agent. The label will be used to
48 // label this agent's trace when all traces from different tracing agents are
49 // combined. Multiple tracing agents could have the same label. The tracing
51 // example, ETW on Windows and CrOS system tracing both use
56 // Starts tracing on the tracing agent with the trace configuration.
60 // Stops tracing on the tracing agent. The trace data will be passed back to
[all …]
|
| /external/libchrome/base/trace_event/ |
| D | tracing_agent.h | 21 // A tracing agent is an entity that records its own sort of trace. Each
22 // tracing method that produces its own trace log should implement this
23 // interface. All tracing agents must only be controlled by TracingController.
44 // Gets the name of the tracing agent. Each tracing agent's name should be
48 // Gets the trace event label of this tracing agent. The label will be used to
49 // label this agent's trace when all traces from different tracing agents are
50 // combined. Multiple tracing agents could have the same label. The tracing
52 // example, ETW on Windows and CrOS system tracing both use
57 // Starts tracing on the tracing agent with the trace configuration.
61 // Stops tracing on the tracing agent. The trace data will be passed back to
[all …]
|
| /external/skia/site/docs/dev/tools/ |
| D | tracing.md | 3 title: "Tracing Skia Execution"
4 linkTitle: "Tracing Skia Execution"
13 with the standard [tracing interface](chrome://tracing), along with the rest of Chromium. In
14 the Android framework, Skia's tracing is integrated into
17 For standalone builds, Skia's tools (DM, nanobench, and Viewer) are capable of tracing execution
20 Standalone Tracing
25 [chrome://tracing](chrome://tracing).
29 # Run DM on several GMs to get tracing data
33 tracing tool that prevent loading a file larger than 256 MB. To stay under that limit (and avoid
35 tracing. Once you have generated a file in this way, go to
[all …]
|
| /external/perfetto/include/perfetto/tracing/ |
| D | tracing.h | 33 #include "perfetto/tracing/backend_type.h"
34 #include "perfetto/tracing/core/forward_decls.h"
35 #include "perfetto/tracing/internal/in_process_tracing_backend.h"
36 #include "perfetto/tracing/internal/system_tracing_backend.h"
37 #include "perfetto/tracing/tracing_policy.h"
123 // As a result when a tracing session is already running and if we attempt to
137 // consumer in Tracing::Initialize(), so that the linker can remove the unused
140 // false, Tracing::NewTrace() will instatiate the system backend only if
151 friend class Tracing;
165 class PERFETTO_EXPORT_COMPONENT Tracing {
[all …]
|
| /external/libtracefs/Documentation/ |
| D | libtracefs-traceon.txt | 7 tracefs_trace_on_fd, tracefs_trace_off_fd - Functions to enable or disable tracing.
26 the given trace instance. The tracing is enabled when writing to the ring buffer is enabled.
28 The *tracefs_trace_is_on()* function checks if tracing is enabled for the given _instance_. If
31 The *tracefs_trace_on()* and *tracefs_trace_off()* functions set the tracing in the _instance_
36 can be used for fast enabling or disabling the tracing of the instance.
38 The *tracefs_trace_on_fd()* and *tracefs_trace_off_fd()* functions set the tracing state to enable
45 The *tracefs_trace_is_on()* function returns 0 if tracing is disable, 1 if it is enabled or
64 /* Tracing is disabled in the top instance */
66 /* Tracing is enabled in the top instance */
68 /* Error getting tracing state of the top instance */
[all …]
|
| /external/perfetto/docs/design-docs/ |
| D | api-and-abi.md | 1 # Tracing API and ABI: surfaces and stability
9 * The public C++ API in `include/perfetto/tracing/` is mostly stable but can
13 * A new C API/ABI for a tracing shared library is in the works in
15 * The tracing protocol ABI is based on protobuf-over-UNIX-socket and shared
23 * There isn't a version number neither in the trace file nor in the tracing
41 [`track_event.h`](/include/perfetto/tracing/track_event.h).
49 `perfetto::Tracing` controller class defined in
50 [`tracing.h`](/include/perfetto/tracing.h).
52 notifications about tracing sessions lifecycle and emit custom protos in the
78 chrome://tracing. The team is continuously reshaping this surface to gradually
[all …]
|
| /external/perfetto/src/tracing/ |
| D | BUILD.gn | 23 # when not use. See comments in Tracing::Initialize() in tracing.h.
29 "../../include/perfetto/tracing",
30 "../../include/perfetto/tracing/core",
57 "../../include/perfetto/tracing",
71 "../../include/perfetto/tracing",
77 # src/tracing/core) need to depend on. It cannot be in the root :tracing target
79 # depend on tracing.
83 "../../include/perfetto/tracing",
92 "../../include/perfetto/tracing/core",
102 "../../include/perfetto/tracing",
[all …]
|
| /external/tensorflow/tensorflow/lite/tools/benchmark/android/ |
| D | README.md | 93 https://developer.android.com/topic/performance/tracing/on-device. Refer to the
99 (4) Enable platform tracing.
105 (5) Set up Quick Settings tile for System Tracing app on your device. Follow the
106 [instruction](https://developer.android.com/topic/performance/tracing/on-device#set-up-tile).
107 The System Tracing tile will be added to the Quick Settings panel.
109 Optionally, you can set up other configurations for tracing from the app menu.
111 [guide](https://developer.android.com/topic/performance/tracing/on-device#app-menu)
114 (6) Tap the System Tracing tile, which has the label "Record trace". The tile
118 (7) Run the benchmark with platform tracing enabled.
136 (9) Stop tracing by tapping either the System Tracing tile in the Quick Settings
[all …]
|
| /external/perfetto/examples/sdk/ |
| D | example_startup_trace.cc | 17 // This example demonstrates startup tracing with a custom data source.
18 // Startup tracing can work only with kSystemBackend. Before running
21 // Run system tracing: ninja -C out/default/ traced && ./out/default/traced
26 #include "perfetto/tracing.h"
27 #include "perfetto/tracing/core/data_source_descriptor.h"
28 #include "perfetto/tracing/core/trace_config.h"
29 #include "perfetto/tracing/data_source.h"
30 #include "perfetto/tracing/tracing.h"
49 // are going to use the system-wide tracing service, because the in-process in InitializePerfetto()
50 // backend doesn't support startup tracing. in InitializePerfetto()
[all …]
|
| /external/perfetto/docs/instrumentation/ |
| D | tracing-sdk.md | 1 # Tracing SDK
3 The Perfetto Tracing SDK is a C++17 library that allows userspace applications
6 When using the Tracing SDK there are two main aspects to consider:
8 1. Whether you are interested only in tracing events coming from your own app
13 2. For app-specific tracing, whether you need to trace simple types of timeline
92 perfetto::Tracing::Initialize(args);
100 The SDK offers two abstraction layers to inject tracing data, built on top of
106 Track events are the suggested option when dealing with app-specific tracing as
126 perfetto::Tracing::Initialize(args);
146 Track events are the best default option and serve most tracing use cases with
[all …]
|