From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754853AbbCBUd4 (ORCPT ); Mon, 2 Mar 2015 15:33:56 -0500 Received: from mail-qa0-f41.google.com ([209.85.216.41]:55480 "EHLO mail-qa0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754657AbbCBUdz (ORCPT ); Mon, 2 Mar 2015 15:33:55 -0500 MIME-Version: 1.0 In-Reply-To: <54F4BECD.6030608@opersys.com> References: <20150302144520.72808a08@gandalf.local.home> <54F4BECD.6030608@opersys.com> From: Alexei Starovoitov Date: Mon, 2 Mar 2015 12:33:34 -0800 Message-ID: Subject: Re: [PATCH v2 00/15] tracing: 'hist' triggers To: Karim Yaghmour Cc: Steven Rostedt , Tom Zanussi , Masami Hiramatsu , Namhyung Kim , Andi Kleen , LKML , Ingo Molnar , Arnaldo Carvalho de Melo Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 2, 2015 at 11:49 AM, Karim Yaghmour wrote: > > On 15-03-02 02:45 PM, Steven Rostedt wrote: >> Interesting. The Android devices I have still have it enabled (rooted, >> but still running the stock system). > > I don't know that there's any policy to disable tracing on Android. The > Android framework in fact has generally been instrumented by Google > itself to output trace info into trace_marker. And the systrace/atrace > tools made available to app developers need to get access to this > tracing info. So, if Android had tracing disabled, systrace/atrace > wouldn't work. > https://developer.android.com/tools/debugging/systrace.html that's interesting. thanks for the link. I don't see tracing being explicitly enabled in defconfig: https://source.android.com/devices/tech/kernel.html or here: https://android.googlesource.com/kernel/common/+/android-3.10/android/configs/android-recommended.cfg