From: Karim Yaghmour <karim.yaghmour@opersys.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Alexei Starovoitov <ast@plumgrid.com>
Cc: 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>
Subject: Re: [PATCH v2 00/15] tracing: 'hist' triggers
Date: Mon, 02 Mar 2015 14:49:33 -0500 [thread overview]
Message-ID: <54F4BECD.6030608@opersys.com> (raw)
In-Reply-To: <20150302144520.72808a08@gandalf.local.home>
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
next prev parent reply other threads:[~2015-03-02 19:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 19:36 [PATCH v2 00/15] tracing: 'hist' triggers Alexei Starovoitov
2015-03-02 19:45 ` Steven Rostedt
2015-03-02 19:49 ` Karim Yaghmour [this message]
2015-03-02 20:33 ` Alexei Starovoitov
2015-03-02 20:37 ` Karim Yaghmour
2015-03-02 20:39 ` Steven Rostedt
2015-03-02 20:43 ` Steven Rostedt
2015-03-02 20:48 ` Alexei Starovoitov
2015-03-02 20:52 ` Karim Yaghmour
2015-03-02 20:54 ` Karim Yaghmour
-- strict thread matches above, loose matches on Subject: below --
2015-03-03 2:31 Alexei Starovoitov
2015-03-03 15:47 ` Tom Zanussi
2015-03-04 2:22 ` Alexei Starovoitov
2015-03-04 5:01 ` Tom Zanussi
2015-03-03 0:01 Alexei Starovoitov
2015-03-03 1:18 ` Tom Zanussi
2015-03-02 19:14 Alexei Starovoitov
2015-03-02 19:31 ` Steven Rostedt
2015-03-02 19:55 ` Tom Zanussi
2015-03-09 11:38 ` He Kuang
2015-03-02 16:00 Tom Zanussi
2015-03-03 2:25 ` Masami Hiramatsu
2015-03-03 14:47 ` Tom Zanussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F4BECD.6030608@opersys.com \
--to=karim.yaghmour@opersys.com \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=ast@plumgrid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).