diff options
| author | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2019-06-02 14:30:09 +0300 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2019-07-11 01:52:58 +0300 |
| commit | da0fb5fdd430abef136bc5e1636f8d1855cf0008 (patch) | |
| tree | 638f7d341c173601c97874843ce78f368f33a82f /lib/Kconfig | |
| parent | a2fa38da200cbd454bcb8dc7659bde00044302f7 (diff) | |
| download | u-boot-da0fb5fdd430abef136bc5e1636f8d1855cf0008.tar.xz | |
trace: make call depth limit customizable
Up to now we had hard coded values for the call depth up to which trace
records are created: 200 for early tracing, 15 thereafter. UEFI
applications reach a call depth of 80 or above.
Provide customizing settings for the call trace depth limit and the early
call trace depth limit. Use the old values as defaults.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'lib/Kconfig')
| -rw-r--r-- | lib/Kconfig | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/lib/Kconfig b/lib/Kconfig index 416e63c1c7..e717eb3de5 100644 --- a/lib/Kconfig +++ b/lib/Kconfig @@ -192,6 +192,13 @@ config TRACE_BUFFER_SIZE the size is too small then 'trace stats' will show a message saying how many records were dropped due to buffer overflow. +config TRACE_CALL_DEPTH_LIMIT + int "Trace call depth limit" + depends on TRACE + default 15 + help + Sets the maximum call depth up to which function calls are recorded. + config TRACE_EARLY bool "Enable tracing before relocation" depends on TRACE @@ -209,6 +216,14 @@ config TRACE_EARLY_SIZE Sets the size of the early trace buffer in bytes. This is used to hold tracing information before relocation. +config TRACE_EARLY_CALL_DEPTH_LIMIT + int "Early trace call depth limit" + depends on TRACE_EARLY + default 200 + help + Sets the maximum call depth up to which function calls are recorded + during early tracing. + config TRACE_EARLY_ADDR hex "Address of early trace buffer in U-Boot" depends on TRACE_EARLY |