diff options
author | Simon Glass <sjg@chromium.org> | 2017-05-17 03:25:36 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2017-05-22 12:45:30 -0400 |
commit | 7d0f5c1300555101e1625ed7256ee6c3502e8482 (patch) | |
tree | 1890439fb1ebb68ffa78ed87e142ef260fb14ef2 /cmd | |
parent | 070f3168fa93f205af3c4c971a307ed8325e7754 (diff) | |
download | u-boot-7d0f5c1300555101e1625ed7256ee6c3502e8482.tar.gz |
Convert CONFIG_CMD_IOTRACE to Kconfig
This converts the following to Kconfig:
CONFIG_CMD_IOTRACE
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'cmd')
-rw-r--r-- | cmd/Kconfig | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/cmd/Kconfig b/cmd/Kconfig index 0f54ae35f9..c1e271d329 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -501,6 +501,40 @@ config CMD_IO checking the state of devices during boot when debugging device drivers, etc. +config CMD_IOTRACE + bool "iotrace - Support for tracing I/O activity" + 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. + + When debugging drivers it is useful to see what I/O accesses were + done and in what order. + + Even if the individual accesses are of little interest it can be + useful to verify that the access pattern is consistent each time + an operation is performed. In this case a checksum can be used to + characterise the operation of a driver. The checksum can be compared + across different runs of the operation to verify that the driver is + working properly. + + In particular, when performing major refactoring of the driver, where + the access pattern should not change, the checksum provides assurance + that the refactoring work has not broken the driver. + + This works by sneaking into the io.h heder for an architecture and + redirecting I/O accesses through iotrace's tracing mechanism. + + For now no commands are provided to examine the trace buffer. The + format is fairly simple, so 'md' is a reasonable substitute. + + Note: The checksum feature is only useful for I/O regions where the + contents do not change outside of software control. Where this is not + suitable you can fall back to manually comparing the addresses. It + might be useful to enhance tracing to only checksum the accesses and + not the data read/written. + config CMD_LOADB bool "loadb" default y |