From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755124AbbCBUtc (ORCPT <rfc822;w@1wt.eu>);
	Mon, 2 Mar 2015 15:49:32 -0500
Received: from mail-qa0-f52.google.com ([209.85.216.52]:44196 "EHLO
	mail-qa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754526AbbCBUtN (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 2 Mar 2015 15:49:13 -0500
MIME-Version: 1.0
In-Reply-To: <20150302154311.3f14c949@gandalf.local.home>
References: <CAMEtUuzutNB39NQH3WCnrG8bFSVmG3O17TGw8gpHXTvU_YMg9w@mail.gmail.com>
 <20150302144520.72808a08@gandalf.local.home> <54F4BECD.6030608@opersys.com>
 <CAMEtUuxAbVryGgP0GSszjNY_M=Sxwpi5NkwO9GExi4uWpdLnmg@mail.gmail.com>
 <20150302153948.7fb62a58@gandalf.local.home> <20150302154311.3f14c949@gandalf.local.home>
From: Alexei Starovoitov <ast@plumgrid.com>
Date: Mon, 2 Mar 2015 12:48:52 -0800
Message-ID: <CAMEtUuyFppG7H1LBzRSXeCn3Ftqs9BYYSxyndvw0h1M1+8HpHQ@mail.gmail.com>
Subject: Re: [PATCH v2 00/15] tracing: 'hist' triggers
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Karim Yaghmour <karim.yaghmour@opersys.com>,
        Tom Zanussi <tom.zanussi@linux.intel.com>,
        Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
        Namhyung Kim <namhyung@kernel.org>, Andi Kleen <andi@firstfloor.org>,
        LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>,
        Arnaldo Carvalho de Melo <acme@infradead.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Mar 2, 2015 at 12:43 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 2 Mar 2015 15:39:48 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
>> On Mon, 2 Mar 2015 12:33:34 -0800
>> Alexei Starovoitov <ast@plumgrid.com> wrote:
>>
>> > On Mon, Mar 2, 2015 at 11:49 AM, Karim Yaghmour
>> > <karim.yaghmour@opersys.com> 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
>>
>> CONFIG_SCHED_TRACER=y
>>
>> That alone will enable tracing.
>>
>> -- Steve
>>
>> > or here:
>> > https://android.googlesource.com/kernel/common/+/android-3.10/android/configs/android-recommended.cfg
>>
>
> CONFIG_ENABLE_DEFAULT_TRACERS=y
>
> And so will that.

good. thanks for explaining.
all makes sense now.

btw, that fancy systrace seems to be parsing text from trace_pipe
https://android.googlesource.com/platform/external/chromium-trace/+/jb-dev/src/tracing/linux_perf_importer.js
with a bunch of regex...
including sched_switch: next_prio...