From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Ftrace Data Export
Date: Wed, 17 May 2017 11:08:18 +0300 [thread overview]
Message-ID: <87a86bx5vx.fsf@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
Hi Chunyan,
When you wrote your patchset to provide ftrace exports, why did you
choose to export only function trace? Why not tracepoints,
function_graph, hwlat, irqsoff and all the other possibilities?
Is there an underlying reason why you chose to export only function
trace?
Thanks
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2017-05-17 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 8:08 Felipe Balbi [this message]
2017-05-17 12:45 ` Ftrace Data Export Chunyan Zhang
2017-06-02 10:24 ` Felipe Balbi
2017-06-02 12:22 ` Chunyan Zhang
2017-06-05 6:17 ` Felipe Balbi
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=87a86bx5vx.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=zhang.chunyan@linaro.org \
/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).