Pau Espin d12f698dbb logging: Introduce mutex API to manage log_target in multi-thread envs ... log_enable_multithread() enables use of locks inside the implementation. Lock use is disabled by default, this way only multi-thread processes need to enable it and suffer related complexity/performance penalties. Locks are required around osmo_log_target_list and items inside it, since targets can be used, modified and deleted by different threads concurrently (for instance, user writing "logging disable" in VTY while another thread is willing to write into that target). Multithread apps and libraries aiming at being used in multithread apps should update their code to use the locks introduced here when containing code iterating over osmo_log_target_list explictly or implicitly by obtaining a log_target (eg. osmo_log_vty2tgt()). Related: OS#4088 Change-Id: Id7711893b34263baacac6caf4d489467053131bb		2019-10-09 14:19:52 +02:00
..
DUMMY	Create a dummy m4 directory to make autoreconf --install --force work	2010-03-24 02:55:33 +01:00
ax_check_compile_flag.m4	configure.ac: add SIMD detection capabilities	2017-05-07 23:11:06 +07:00
ax_check_simd.m4	conv_acc: Our code requires SSSE3, not just SSE3	2017-11-17 11:44:22 +01:00
ax_pthread.m4	logging: Introduce mutex API to manage log_target in multi-thread envs	2019-10-09 14:19:52 +02:00
check_tls_gcc_arm_bug.m4	configure: Allow disabling workaround for TLS bug in old ARM gcc versions	2019-08-06 12:50:26 +02:00