binder: Stub out debug prints by default

Binder code is very hot, so checking frequently to see if a debug
message should be printed is a waste of cycles. We're not debugging
binder, so just stub out the debug prints to compile them out entirely.

Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
fourteen
Sultan Alsawaf 4 years ago committed by Jenna
parent 4c7659aa15
commit caf6b06015
  1. 11
      drivers/android/binder.c

@ -147,6 +147,7 @@ static int binder_set_stop_on_user_error(const char *val,
module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
param_get_int, &binder_stop_on_user_error, 0644);
#ifdef DEBUG
#define binder_debug(mask, x...) \
do { \
if (binder_debug_mask & mask) \
@ -160,6 +161,16 @@ module_param_call(stop_on_user_error, binder_set_stop_on_user_error,
if (binder_stop_on_user_error) \
binder_stop_on_user_error = 2; \
} while (0)
#else
static inline void binder_debug(uint32_t mask, const char *fmt, ...)
{
}
static inline void binder_user_error(const char *fmt, ...)
{
if (binder_stop_on_user_error)
binder_stop_on_user_error = 2;
}
#endif
#define binder_set_extended_error(ee, _id, _command, _param) \
do { \

Loading…
Cancel
Save