michaelh/zephyr
1
0
Fork 0
Code Releases Activity

logging: Use runtime packaging in immediate mode

Browse source 
Always use runtime packaging in immediate mode. Removing attempt to
package on stack if possible. It would be done only to speed up
logging but that is not a requirement in immediate mode where
packaging time is fractional compared to backend processing. Using
runtime packaging also reduces stack usage in the context which calls
log message.

Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
This commit is contained in:
Krzysztof Chruscinski 2022-02-09 11:59:26 +01:00 • committed by Carles Cufí
commit 154ca8526c
3 changed files with 8 additions and 42 deletions
Download patch file Download diff file Expand all files Collapse all files

12
subsys/logging/Kconfig.misc
View file

@ -35,16 +35,18 @@ config LOG2_USE_VLA
compile time so at runtime arrays have fixed size.
config LOG2_ALWAYS_RUNTIME
bool "Always use runtime message creation (v2)"
bool
default y if NO_OPTIMIZATIONS
default y if LOG_MODE_IMMEDIATE
help
If enabled, runtime method is always used for message creation. Static
creation relies on compiler being able to optimize and remove code
based on information known at compile time. It is recommended to
enable this option when optimization is disabled because some compilers
based on information known at compile time. Runtime only approach is
used when optimization is disabled because some compilers
(seen on arm_cortex_m and x86) were using unrealistic amount of stack
for dead code. Option applies to v1 as well because distinction
between versions is done by the compiler.
for dead code. It is also used in immediate mode since it requires
less stack than static message creation and speed has lower priority
in that mode.
config LOG2_FMT_SECTION
bool "Keep log strings in dedicated section"