diff options
| author | 2021-06-25 21:50:50 +0000 | |
|---|---|---|
| committer | 2021-06-25 22:41:06 +0000 | |
| commit | 1f1bed66b99b2cd6b7dc8db441fa492ec18d12f4 (patch) | |
| tree | 60414ad7ce8a1d71b8fc1f66fda2fd5e6b30bf73 /libs/binder/ProcessInfoService.cpp | |
| parent | 9e759e81a53bd0f5027f3a0a37661206d46774a3 (diff) | |
libbinder_ndk: eradicate global lock
Let the nightmares cease!
Without contention, peace.
Note, in the case that an ABpBinder is backed by a BBinder (this happens
when you talk in-process to something between the NDK backend and either
the C++, Rust, or Java backends of AIDL), this introduces an additional
allocation b/c the BBinder's mExtra needs to be allocated for
BBinder::withLock to work. Since this is generally frowned upon, and the
thrashing in this case is already pretty egregious, I don't mind it.
Now, binder proxies can be allocated simultaneously in a process.
Bug: 192023359
Test: CtsNdkBinderTestCases
Change-Id: Ib1c28c9488f7a03579ea9d18347a8fc08cc3f48a
Diffstat (limited to 'libs/binder/ProcessInfoService.cpp')
0 files changed, 0 insertions, 0 deletions