Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tools: mtrace-reader.py: Add option to mark chunk starts in output #9520

Merged

Conversation

ujfalusi
Copy link
Contributor

Sometimes it can help to see how the chunks arrive from firmware when comparing logs with the kernel for example.

The --mark-chunks flag will add a marker for each new chunk that is printed with a running number and the size of the given chunk, for example:

--- Chunk #604 start (size: 652) ---
[ 0.000000] init: print_version_banner: FW ABI 0x301d001 DBG ABI 0x5003000 tags SOF:v2.5-stable-branch-2772-g76e650e56598-dirty zephyr:v3.7.0-2127-ge7c84756087f src hash 0x4ff3fd64 (ref hash 0x4ff3fd64)
*** Booting Zephyr OS build v3.7.0-2127-ge7c84756087f ***
[ 0.000000] main: sof_app_main: SOF on intel_adsp
[ 0.000000] main: sof_app_main: SOF initialized
[ 0.000000] ipc: ipc_cmd: rx : 0x44000000|0x31400008
[11896.403666] ipc: ipc_cmd: tx-reply : 0x64000000|0x31400008
[11896.404076] ipc: ipc_cmd: rx : 0x44000000|0x3060004c
[11896.404093] ipc: ipc_cmd: tx-reply : 0x64000000|0x3060004c
--- Chunk #605 start (size: 196) ---

[11896.969658] ipc: ipc_cmd: rx : 0x11000005|0x0
[11896.969671] pipe: pipeline_new: pipeline new pipe_id 0 priority 0
[11896.969685] ipc: ipc_cmd: tx-reply : 0xb1000000|0x0

--- Chunk #606 start (size: 2236) ---

Sometimes it can help to see how the chunks arrive from firmware when
comparing logs with the kernel for example.

The --mark-chunks flag will add a marker for each new chunk that is printed
with a running number and the size of the given chunk, for example:

--- Chunk thesofproject#604 start (size: 652) ---
[    0.000000] <inf> init: print_version_banner: FW ABI 0x301d001 DBG ABI 0x5003000 tags SOF:v2.5-stable-branch-2772-g76e650e56598-dirty zephyr:v3.7.0-2127-ge7c84756087f src hash 0x4ff3fd64 (ref hash 0x4ff3fd64)
*** Booting Zephyr OS build v3.7.0-2127-ge7c84756087f ***
[    0.000000] <inf> main: sof_app_main: SOF on intel_adsp
[    0.000000] <inf> main: sof_app_main: SOF initialized
[    0.000000] <inf> ipc: ipc_cmd: rx   : 0x44000000|0x31400008
[11896.403666] <inf> ipc: ipc_cmd: tx-reply     : 0x64000000|0x31400008
[11896.404076] <inf> ipc: ipc_cmd: rx   : 0x44000000|0x3060004c
[11896.404093] <inf> ipc: ipc_cmd: tx-reply     : 0x64000000|0x3060004c
--- Chunk thesofproject#605 start (size: 196) ---

[11896.969658] <inf> ipc: ipc_cmd: rx   : 0x11000005|0x0
[11896.969671] <inf> pipe: pipeline_new: pipeline new pipe_id 0 priority 0
[11896.969685] <inf> ipc: ipc_cmd: tx-reply     : 0xb1000000|0x0

--- Chunk thesofproject#606 start (size: 2236) ---

Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
sys.stdout.write(chunk_msg)

sys.stdout.buffer.write(data)
sys.stdout.flush()
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ujfalusi Paused for a moment on this. Not sure if this disables the buffering compared to old version, but I guess the flush is needed in practise here as the buffer.write() is used. Let's merge this version and return if this causes problems.

@kv2019i
Copy link
Collaborator

kv2019i commented Oct 1, 2024

Unrelated CI fails, proceeding to merge.

@kv2019i kv2019i merged commit 6949112 into thesofproject:main Oct 1, 2024
42 of 47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants