| 64a1e08b86d72cb375f9dfdf4eb6307f71817350 |
|
20-Apr-2012 |
Mathias Agopian <mathias@google.com> |
SF doesn't need more than a few binder threads
Change-Id: Ic4659fb81f9990cc7caf84a496a8ae659a1d16a9
/frameworks/native/include/binder/BinderService.h
|
| a94f129a7bbaa8ea45c50e49ba3e6127ca2a15ec |
|
10-Feb-2012 |
Dianne Hackborn <hackbod@google.com> |
Some hardening of isolated processes by restricting access to services.
Services now must explicitly opt in to being accessed by isolated
processes. Currently only the activity manager and surface flinger
allow this. Activity manager is needed so that we can actually
bring up the process; SurfaceFlinger is needed to be able to get the
display information for creating the Configuration. The SurfaceFlinger
should be safe because the app doesn't have access to the window
manager so can't actually get a surface to do anything with.
The activity manager now protects most of its entry points against
isolated processes.
Change-Id: I0dad8cb2c873575c4c7659c3c2a7eda8e98f46b0
/frameworks/native/include/binder/BinderService.h
|
| a1e6bc864fb821c1b470b7aad9b75c441f54eeb4 |
|
15-Jul-2010 |
Mathias Agopian <mathias@google.com> |
added BinderService<> template to help creating native binder services
Change-Id: Id980899d2647b56479f8a27c89eaa949f9209dfe
/frameworks/native/include/binder/BinderService.h
|