Merge branch 'next'
This commit is contained in:
@@ -18,8 +18,8 @@ The callbacks are named and associated with a function using the
|
||||
U_BOOT_ENV_CALLBACK macro in your board or driver code.
|
||||
|
||||
These callbacks are associated with variables in one of two ways. The
|
||||
static list can be added to by defining CFG_ENV_CALLBACK_LIST_STATIC
|
||||
in the board configuration to a string that defines a list of
|
||||
static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC
|
||||
in the board defconfig via menuconfig to a string that defines a list of
|
||||
associations. The list must be in the following format::
|
||||
|
||||
entry = variable_name[:callback_name]
|
||||
|
||||
@@ -163,6 +163,17 @@ you will see the time taken by each function shown against its exit record.
|
||||
u-boot-1 [000] 3.116466: funcgraph_entry: 0.063 us | memset();
|
||||
u-boot-1 [000] 3.116539: funcgraph_exit: 0.143 us | }
|
||||
|
||||
The `trace wipe` command may be used to clear the trace buffer. It leaves
|
||||
tracing in its current enable state. This command is convenient when tracing a
|
||||
single command, for example:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
=> trace pause; trace wipe
|
||||
=> trace resume; dhcp; trace pause
|
||||
=> trace stats
|
||||
...
|
||||
|
||||
Flame graph
|
||||
-----------
|
||||
|
||||
|
||||
Reference in New Issue
Block a user