Age | Commit message (Collapse) | Author |
|
Instead of having this library, libbinder/libhwbinder can keep track of
stack pointers so that when they recurse, we know which one was visited
most recently.
As with the original implementation of libbinderthreadstate, this is
somewhat of a hack. An explanation of why this is and what to do instead
is added in CallerUtils.h.
Bug: 148692216
Test: libbinderthreadstateutils_test
Change-Id: Ief28663728fb8786b06bf9e72238052b9af81d87
|
|
being served.""
This reverts commit d2e4de2a0c99031fd7227f162517de313fd29262.
Reason for revert: Dependencies which broke tests due to exclusion from
LOCAL_JNI_SHARED_LIBS have been added.
Change-Id: If400a48214274d121e79135ac5d573fcb1a4a4c2
|
|
being served."
This reverts commit 0397face57629e778b2bafe276afa0ca7479236b.
Reason for revert: This breaks framework tests and blocks presubmit
Change-Id: Iead3f828deea1245e43d7e27162b149dfbd56bb9
|
|
This can be useful when common code can be executed by both hwbinder and
binder threads, and, they want to access (hardware::)IPCThreadState
specific information. Eg: cameraserver.
This commit adds a vndk private library 'libbinderthreadstate' which
serves as common ground for both libbinder and libhwbinder to inform
them about the nature of the IPC call being served (if at all) on the current
thread.
Bug: 110364143
Test: Boot device, use GCA
Change-Id: Ifefb273c9a1f545417a82e9511a45bda00f701aa
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
|