From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755450AbbCBTtj (ORCPT ); Mon, 2 Mar 2015 14:49:39 -0500 Received: from mail-qc0-f172.google.com ([209.85.216.172]:36393 "EHLO mail-qc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754466AbbCBTth (ORCPT ); Mon, 2 Mar 2015 14:49:37 -0500 Message-ID: <54F4BECD.6030608@opersys.com> Date: Mon, 02 Mar 2015 14:49:33 -0500 From: Karim Yaghmour User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Steven Rostedt , Alexei Starovoitov CC: Tom Zanussi , Masami Hiramatsu , Namhyung Kim , Andi Kleen , LKML , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: [PATCH v2 00/15] tracing: 'hist' triggers References: <20150302144520.72808a08@gandalf.local.home> In-Reply-To: <20150302144520.72808a08@gandalf.local.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 -- Karim Yaghmour CEO - Opersys inc. / www.opersys.com http://twitter.com/karimyaghmour