perfetto parameters are confused

[qiu]

Hello, I only configure the surfaceflinger layer property will grab the windowmanger and other information on the root. I want to know the reason

[Lalit Maganti]

Please provide your full trace config. It's very difficult to help without it. 

On Mon, 10 Mar 2025, 08:35 qiu, <qiu4...@gmail.com> wrote:

Hello, I only configure the surfaceflinger layer property will grab the windowmanger and other information on the root. I want to know the reason

--
You received this message because you are subscribed to the Google Groups "Perfetto Development - www.perfetto.dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to perfetto-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/perfetto-dev/a027080c-8683-4317-ae47-aeab7edb7cbcn%40googlegroups.com.

[qiu]

write_into_file: true flush_period_ms: 30000 notify_traceur: true incremental_state_config { clear_period_ms: 15000 } file_write_period_ms: 1000 buffers { size_kb: 63488 fill_policy: RING_BUFFER } buffers { size_kb: 2048 fill_policy: RING_BUFFER } data_sources: { config { name: "android.surfaceflinger.layers" target_buffer: 1 surfaceflinger_layers_config { mode: MODE_ACTIVE trace_flags: TRACE_FLAG_INPUT trace_flags: TRACE_FLAG_COMPOSITION trace_flags: TRACE_FLAG_HWC trace_flags: TRACE_FLAG_BUFFERS trace_flags: TRACE_FLAG_VIRTUAL_DISPLAYS } } } duration_ms: 0

[Lalit Maganti]

Are you sure this is your full config? You should be getting wm tracing if this is the config. 

How are you collecting the trace? Through the on device tracing app? Because otherwise the presence of traceur is very strange. 

To view this discussion visit https://groups.google.com/d/msgid/perfetto-dev/dad681bf-a924-4a46-a7c1-cdf5d4ef23d8n%40googlegroups.com.

[qiu]

But why do I get wm information if I add traceur

[Lalit Maganti]

Honestly I don't know. It would be quite strange for Perfetto to give information you are not asking for. 

I only asked about traceur because I have my doubts of the config you are using. How you are collecting the trace may help figure out if someone is adding extra data sources etc. 

To view this discussion visit https://groups.google.com/d/msgid/perfetto-dev/180f5440-d08e-4954-826e-1ad295c2ca4en%40googlegroups.com.

[qiu]

This problem will only occur on root, user will not be able to capture wm information file; But I went to check the source code of traceur and found that there was no wm logic to capture the operation. Do you have any clue, this has troubled me for a long time

[Lalit Maganti]

No clue I'm afraid. This is a very mysterious issue. I'm still not convinced that what you've pasted is the full config honestly. 

To view this discussion visit https://groups.google.com/d/msgid/perfetto-dev/a282c857-9d7c-47f5-929e-ae21f47ebde7n%40googlegroups.com.

[qiu]

I have found the reason is that the packages/apps/Traceur/src_common/com/android/Traceur/PerfettoUtils in Java tracestart method were used in the two buffer contributed to grab the ftrace. I tried to grab the layer with only one buffer, but the actual effect is that the grab failed, which is not allowed. What should I do to grab only the layer, the source code is as follows:// Allots 1 / BUFFER_SIZE_RATIO to the small buffer and the remainder to the large buffer,
// (less the size of the buffer reserved for unchanging system information).
int totalBufferSizeKb = numCpus * bufferSizeKb - SYSTEM_INFO_BUFFER_SIZE_KB;
int targetBuffer1Kb = totalBufferSizeKb / BUFFER_SIZE_RATIO;
int targetBuffer0Kb = totalBufferSizeKb - targetBuffer1Kb;

// This is target_buffer: 0, which is used for ftrace and the ftrace-derived
// android.gpu.memory.
appendTraceBuffer(config, targetBuffer0Kb);

// This is target_buffer: 1, which is used for additional data sources.
appendTraceBuffer(config, targetBuffer1Kb);

// This is target_buffer: 2, used for unchanging system information like the packages
// list.
appendTraceBuffer(config, SYSTEM_INFO_BUFFER_SIZE_KB);