1cfe90d825
I am using the tracing module using the RAM backend on a system with limited RAM & a buffer that can only store 300ms of tracing data. Current tracing module starts recording during boot-up & we run out of memory prior to executing code we actually want to trace. By reseting buffer metadata here, I can call init() at an arbitrary point of program execution & the tracing module will reset & start tracing. I tested on E2E on an ARM M-class MCU by calling init & then reading buffered tracing data via GDB Signed-off-by: Galen Krulce <gkrulce@meta.com> |
||
|---|---|---|
| .. | ||
| ctf | ||
| include | ||
| sysview | ||
| test | ||
| user | ||
| CMakeLists.txt | ||
| Kconfig | ||
| tracing_backend_adsp_memory_window.c | ||
| tracing_backend_posix_bottom.c | ||
| tracing_backend_posix_bottom.h | ||
| tracing_backend_posix.c | ||
| tracing_backend_ram.c | ||
| tracing_backend_uart.c | ||
| tracing_backend_usb.c | ||
| tracing_buffer.c | ||
| tracing_core.c | ||
| tracing_format_async.c | ||
| tracing_format_common.c | ||
| tracing_format_sync.c | ||
| tracing_none.c | ||
| tracing_tracking.c | ||