Lines Matching refs:session

345   // Priority of the tracing session client. A higher priority session may
412   // Fix gpu clock rate during trace session.
707   // If set, stop the trace session after blocking the client for this
737   // Escape hatch if the session is being torn down because of a forked child
1379   // Set by the service to indicate whether this tracing session has extra
1388   // Set by the service to indicate which tracing session the data source
1391   // session and hence should be linked together.
1472 // The overall config that is used when starting a new tracing session through
1667   // result in a hung trace session.
1691   // Android-only. If set to a value > 0, marks the trace session as a candidate
1694   // --save-for-bugreport, traced will pick the tracing session with the highest
1700   // Triggers allow producers to start or stop the tracing session when an event
1715       // starting of the tracing system. On triggering, the session will then
1717       // after |trigger_timeout_ms| the session will be stopped and no data will
1721       // When this mode is chosen, the session will be started via the normal
1723       // the session will be stopped after |trigger_timeout_ms| and no data will
1808   // If set the tracing service will ensure there is at most one tracing session
1989   // Stats for the TraceBuffer(s) of the current trace session.
1993   // session or not).
2009   // Num. buffers for all tracing session (not just the current one). This will
2011   // session.
2084   // session and NOT relative to the previous Stats snapshot).
2454   // List of all active triggers in current session, when trace was triggered.
5677   // The first trace packet of each session should include counter_spec.
5782   // The first trace packet of each session should include a Specifications
7284   // index, thus interning IDs are scoped to the tracing session and field
7287   // within the same tracing session, even after a reset of the emitted
7521     // tracing session was running and it had the highest bugreport_score. In
7566   // The first trace packet of each session should include a energy consumer
7878     // This process was not profiled because a concurrent session was active.
7883     // If false, the process outlived the profiling session.
7900     // guardrails during this profiling session.
8593   // * On the other hand, if there was a crash during the session and trace was
9012   // Uniquely identifies a producer + writer pair within the tracing session. A