michaelh/zephyr
1
0
Fork 0
Code Releases Activity

logging: add API to trigger immediate processing of logs

Browse source 
There are use cases where it's beneficial to trigger the log
thread to process log messages as soon as able instead of waiting
for the processing timer or threshold triggers. An example would be
to flush the log buffer before entering the idle thread after
forcing a system power state.

Signed-off-by: Corey Wharton <xodus7@cwharton.com>
This commit is contained in:
Corey Wharton 2024-04-15 16:22:28 -07:00 • committed by Anas Nashif
commit bf114c6b1a
3 changed files with 51 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

35
tests/subsys/logging/log_core_additional/src/log_test.c
View file

@ -439,6 +439,41 @@ ZTEST(test_log_core_additional, test_log_thread)
}
#endif
/**
* @brief Process all logging activities using a dedicated thread (trigger immediate processing)
*
* @addtogroup logging
*/
#ifdef CONFIG_LOG_PROCESS_THREAD
ZTEST(test_log_core_additional, test_log_thread_trigger)
{
log_setup(false);
zassert_false(log_data_pending());
LOG_INF("log info to log thread");
LOG_WRN("log warning to log thread");
LOG_ERR("log error to log thread");
zassert_true(log_data_pending());
/* Trigger log thread to process messages as soon as possible. */
log_thread_trigger();
/* wait 1ms to give logging thread chance to handle these log messages. */
k_sleep(K_MSEC(1));
zassert_equal(3, backend1_cb.counter,
"Unexpected amount of messages received by the backend.");
zassert_false(log_data_pending());
}
#else
ZTEST(test_log_core_additional, test_log_thread_trigger)
{
ztest_test_skip();
}
#endif
static void call_log_generic(const char *fmt, ...)
{
va_list ap;