57e8d5ecfb
The logging thread is usually woken up by a timer, if the timer period is longer than 10ms, log_flush() can iterate multiple times needlessly, while waiting for the next timer. Instead wake up the logging thread to let it flush the queue immediately. Besides a hard-coded polling period of 10ms is too long for some applications, make it a Kconfig parameter. Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com> |
||
|---|---|---|
| .. | ||
| backends | ||
| frontends | ||
| mipi_syst | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.filtering | ||
| Kconfig.formatting | ||
| Kconfig.links | ||
| Kconfig.misc | ||
| Kconfig.mode | ||
| Kconfig.processing | ||
| Kconfig.template.log_config | ||
| Kconfig.template.log_config_inherit | ||
| Kconfig.template.log_format_config | ||
| log_cache.c | ||
| log_cache.h | ||
| log_cmds.c | ||
| log_core.c | ||
| log_link_ipc_service.c | ||
| log_mgmt.c | ||
| log_minimal.c | ||
| log_msg.c | ||
| log_multidomain_link.c | ||
| log_output_custom.c | ||
| log_output_dict.c | ||
| log_output_syst.c | ||
| log_output.c | ||