diff options
| author | Pau Espin Pedrol <pespin@sysmocom.de> | 2019-09-17 20:26:53 +0200 |
|---|---|---|
| committer | Pau Espin Pedrol <pespin@sysmocom.de> | 2019-10-09 19:15:49 +0200 |
| commit | b7e992703c285fa8ea1f22b970d4aa1f202720eb (patch) | |
| tree | a2897d9ffb05ea82b665dbfdbfb85590a560e225 /CommonLibs/debug.h | |
| parent | 928141b7d682a80b12875ef5d288646755dba44e (diff) | |
Use new libosmocore logging lock API
Since libosmocore Id7711893b34263baacac6caf4d489467053131bb, a new API
log_enable_multithread() is available which takes care of protecting
logging infrastructure from us (and actually does it correctly since we
cannot protect internal libosmocore structures from osmo-trx).
Let's drop all mutex related code from osmo-trx logging infra and simply
rely on libosmocore's.
Related: OS#4088
Change-Id: I519d0f30bce871005ca26b90177ea4aa4839360a
Diffstat (limited to 'CommonLibs/debug.h')
| -rw-r--r-- | CommonLibs/debug.h | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/CommonLibs/debug.h b/CommonLibs/debug.h index 760ab32..ad12bb8 100644 --- a/CommonLibs/debug.h +++ b/CommonLibs/debug.h @@ -15,21 +15,10 @@ enum { DLMS, }; - -bool log_mutex_init(); -void log_mutex_lock(); -void log_mutex_unlock(); -void log_mutex_lock_canceldisable(int *st); -void log_mutex_unlock_canceldisable(int st); - #define CLOGC(category, level, fmt, args...) do { \ - log_mutex_lock(); \ LOGP(category, level, "[tid=%lu] " fmt, pthread_self(), ##args); \ - log_mutex_unlock(); \ } while(0) #define CLOGCHAN(chan, category, level, fmt, args...) do { \ - log_mutex_lock(); \ LOGP(category, level, "[tid=%lu][chan=%lu] " fmt, pthread_self(), chan, ##args); \ - log_mutex_unlock(); \ } while(0) |