From c954fde0b6e31ec99509faf0bbc33c4c9e4d012a Mon Sep 17 00:00:00 2001 From: Mark Salyzyn Date: Mon, 9 Nov 2015 17:56:42 -0800 Subject: [PATCH] jni: is loggable speedup, not within signal Speedup by telling __android_is_loggable interface it will not be called within a signal handler. This saves two system calls. Bug: 25563384 Change-Id: Ib8188641c8c76e5aa848476da98596be6b8e5040 --- core/jni/android_util_Log.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/core/jni/android_util_Log.cpp b/core/jni/android_util_Log.cpp index 2d23cda5ff15d..c89f293c05a28 100644 --- a/core/jni/android_util_Log.cpp +++ b/core/jni/android_util_Log.cpp @@ -42,7 +42,9 @@ struct levels_t { static levels_t levels; static jboolean isLoggable(const char* tag, jint level) { - return __android_log_is_loggable(level, tag, ANDROID_LOG_INFO); + return __android_log_is_loggable(level, tag, + ANDROID_LOG_INFO | + ANDROID_LOGGABLE_FLAG_NOT_WITHIN_SIGNAL); } static jboolean android_util_Log_isLoggable(JNIEnv* env, jobject clazz, jstring tag, jint level)