diff options
| author | Tom Rini <[email protected]> | 2025-10-01 14:30:52 -0600 |
|---|---|---|
| committer | Tom Rini <[email protected]> | 2025-10-10 14:25:24 -0600 |
| commit | 16bbc225fed7931988616ba4e223954ae5ccc06b (patch) | |
| tree | 52f02214484508f987e97e992655715961563aa8 /cmd | |
| parent | b30155c08e95550296668766bfd7d3da27c970fe (diff) | |
iotrace: Finish migrating this to Kconfig
When I migrated this to Kconfig in commit 68e54040ccc3 ("sandbox: Move
CONFIG_IO_TRACE to Kconfig") I didn't look hard enough for other
details. As explained in the README, this is valid for ARM too. So start
by making this be a prompted question and CMD_IOTRACE depend on IO_TRACE
being enabled. Next, migrate the information out of README and in to
the appropriate help text for existing options in Kconfig. Finally, make
this option be default y on SANDBOX but not selected as it's valid to
build without it.
Signed-off-by: Tom Rini <[email protected]>
Diffstat (limited to 'cmd')
| -rw-r--r-- | cmd/Kconfig | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/cmd/Kconfig b/cmd/Kconfig index dcf63f423fd..5fcf37e67b9 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -1308,12 +1308,23 @@ config CMD_IO config CMD_IOTRACE bool "iotrace - Support for tracing I/O activity" + depends on IO_TRACE help Provides an 'iotrace' command which supports recording I/O reads and writes in a trace buffer in memory . It also maintains a checksum of the trace records (even if space is exhausted) so that the sequence of I/O accesses can be verified. + Example output from the 'iotrace stats' command is below. + + iotrace is enabled + Start: 10000000 (buffer start address) + Size: 00010000 (buffer size) + Offset: 00000120 (current buffer offset) + Output: 10000120 (start + offset) + Count: 00000018 (number of trace records) + CRC32: 9526fb66 (CRC32 of all trace records) + When debugging drivers it is useful to see what I/O accesses were done and in what order. |