linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Chunyan Zhang <zhang.chunyan@linaro.org>,
	rostedt@goodmis.org, mathieu.poirier@linaro.org,
	alexander.shishkin@linux.intel.com, mingo@redhat.com
Cc: arnd@arndb.de, mike.leach@arm.com, tor@ti.com,
	philippe.langlais@st.com, nicolas.guion@st.com,
	zhang.lyra@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 0/3] Integration of function trace with System Trace IP blocks
Date: Thu, 08 Sep 2016 15:07:04 +0300	[thread overview]
Message-ID: <87inu6h9xz.fsf@linux.intel.com> (raw)
In-Reply-To: <1473303784-18262-1-git-send-email-zhang.chunyan@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]


Hi,

Chunyan Zhang <zhang.chunyan@linaro.org> writes:
> IP blocks allowing a variety of trace sources to log debugging
> information to a pre-defined area have been introduced on a couple of
> architecture [1][2]. These system trace blocks (also known as STM)
> typically follow the MIPI STPv2 protocol [3] and provide a system wide
> logging facility to any device, running a kernel or not, with access
> to the block's log entry port(s).  Since each trace message has a
> timestamp, it is possible to correlate events happening in the entire
> system rather than being confined to the logging facility of a single
> entity.
>
> This patchset is trying to use STM IP blocks to store function tracing
> information produced by Ftrace and I'm taking the Function trace
> (trace type is TRACE_FN) as the example in this patchset, but other
> types of traces also can be supported.
>
> Logging information generated by the Ftrace subsystem to STM and gathered
> in the sink device can be used in conjunction with trace data from other
> board components, also collected in the same trace sink.  
>
> This example is using ARM coresight STM but the same would apply to any
> other architecture wishing to do the same.
>
> Comments would be greatly appreciated.

showing up late to the bandwagon, but this is very good. I've been
toying with the idea of exporting ftrace via USB and this will help
quite a bit. Thanks :-)

I'll add to my TODO a look at this series. Great work.

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

  parent reply	other threads:[~2016-09-08 12:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08  3:03 [PATCH V6 0/3] Integration of function trace with System Trace IP blocks Chunyan Zhang
2016-09-08  3:03 ` [PATCH V6 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only Chunyan Zhang
2016-09-08  3:03 ` [PATCH V6 2/3] stm class: ftrace: Add ftrace-export-over-stm driver Chunyan Zhang
2016-09-08  3:03 ` [PATCH V6 3/3] stm: Mark the functions of writing buffer with notrace Chunyan Zhang
2016-09-08 12:07 ` Felipe Balbi [this message]
2016-09-08 13:09   ` [PATCH V6 0/3] Integration of function trace with System Trace IP blocks Chunyan Zhang

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=87inu6h9xz.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@arm.com \
    --cc=mingo@redhat.com \
    --cc=nicolas.guion@st.com \
    --cc=philippe.langlais@st.com \
    --cc=rostedt@goodmis.org \
    --cc=tor@ti.com \
    --cc=zhang.chunyan@linaro.org \
    --cc=zhang.lyra@gmail.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).