| 1723f3fcd1073896cc8d941a1e3b7d48f9a31af5 |
|
20-Sep-2016 |
Mark Salyzyn <salyzyn@google.com> |
Revert "Restrict pmsg use to eng builds."
This reverts commit f894b96a9211dcefb83b175720b53a2e49b8e463.
Kernel binaries have incorporated the performance-enhanced pmsg driver
that has removed the bounce buffer.
Bug: 31057326
Bug: 30375418
Change-Id: Id6cec3ac144f57e8e5465aa48bbdc829cf29e283
/system/core/liblog/pmsg_writer.c
|
| f894b96a9211dcefb83b175720b53a2e49b8e463 |
|
22-Aug-2016 |
Tim Murray <timmurray@google.com> |
Restrict pmsg use to eng builds.
bug 30375418
Change-Id: I50c6c74a2373593495cf6a3b94b31f9a865c950c
/system/core/liblog/pmsg_writer.c
|
| ad3fdd34074ac7c41dae3ade0a8bb7816291018f |
|
13-Jul-2016 |
Mark Salyzyn <salyzyn@google.com> |
liblog: reset pid and uid cache after a vfork()
(cherry pick from commit ec4f5c776d2bde026e2a74128218924be7b3f46a)
Bionic getuid() and getpid() calls cache to reduce the need to
perform a syscall, and also reset their own cache after a vfork().
No more need for liblog to be performing this flawed cache operation.
Bug: 30085794
Change-Id: I70feed8bff0ddd919c2885a348ba67b14ddc0e0d
/system/core/liblog/pmsg_writer.c
|
| 2b409c9bc73a333373d58dd4f8a0fd77537da29c |
|
29-Apr-2016 |
Mark Salyzyn <salyzyn@google.com> |
liblog: O_CLOEXEC flag on opens
(cherry pick from commit 78786da116064e6a2b7bb768e1eb77f3804eace4)
Bug: 28455828
Change-Id: Ic00101a6192aab7271cb0c3461e249a77d7f29ed
/system/core/liblog/pmsg_writer.c
|
| f58e58a15cea7ba39249093e924a0a6e293c26aa |
|
25-Mar-2016 |
Mark Salyzyn <salyzyn@google.com> |
liblog: suppress pmsg on user builds
(cherry pick from commit 7ef5249afacffe3901e3a602372c7d34cf655675)
- add optimized & cached LIBLOG_HIDDEN __android_log_is_debuggable()
- check when writing, either LOG_ID_SECURITY, SafetyNet or
debuggable when pushing content to the pmsg buffer.
Bug: 27566046
Change-Id: I85f1b55ec329b38e00f4183836b6ed53046c323d
/system/core/liblog/pmsg_writer.c
|
| 10bdf61e5ffbd99efec4d4168aee73a93c5e88be |
|
10-Mar-2016 |
Mark Salyzyn <salyzyn@google.com> |
liblog: add __android_log_pmsg_file_write
(cherry pick from commit d4b061bde280fce9b5426b5738a02d42ec263c48)
- This is considered an Android Private function, not exported
for general use.
- goal is to record a file's content into a series of log
messages into pmsg, to be retrieved after a reboot for
transfer to a persistent location.
- filename reference is converted to a tag-unique
"<dirbase>:<filebase>".
- buffer and length representing the filename contents are
recorded, along with a sequence number placed into the nsec
time field to ANDROID_LOG_PMSG_FILE_MAX_SEQUENCE.
- Add a gTest for this function.
Bug: 27176738
Change-Id: If93df3ae8bfc1bb75516d4a1fd8dae0301af644b
/system/core/liblog/pmsg_writer.c
|
| facf94c74a2cc44f294c4789d36d5c7281c7bc3f |
|
01-Mar-2016 |
Mark Salyzyn <salyzyn@google.com> |
liblog: split out transports into separate files
(cherry pick from commit 018a96d03f0d452bf078084eedcd5693da42308d)
Create config_logger, logger and logger_read to house the log
interfaces. Add fake_logger, logd_logger and pmsg_logger to
house the write and read transports. Allows for an easier and
direct path to add new transports to the library.
SideEffects: None, logger benchmark performance unaffected
Bug: 27176738
Bug: 27405083
Change-Id: I01b38637334a5242905c8c89f6ab0a92e2540008
/system/core/liblog/pmsg_writer.c
|