2aa19dcb59
The marked library(ies) were available to the APEXes via the hand-written whitelist in build/soong/apex/apex.go. Trying to remove the whitelist by adding apex_available property to the Android.bp of the libraries. Bug: 150999716 Test: m Change-Id: I6ea7fee2a135298085d3965d3578d9ecd53ee405 |
||
|---|---|---|
| .. | ||
| include/async_safe | ||
| Android.bp | ||
| async_safe_log.cpp | ||
| README.md | ||
async_safe logging
This library provides an async_safe implementation for formatting and writing log messages to logd.
Note that the liblog implementation connects a single socket to logd and uses a RWLock to manage it among threads, whereas these functions connect to liblog for each log message. While it's beneficial to have this lock-free and therefore async_safe mechanism to write to logd, connecting a socket for each message does not scale well under load. It was also determined to be too costly to connect a socket for each thread as some processes, such as system_server, have over 100 threads. Therefore, we maintain these two separate mechanisms.