[RTEMS Project] #3028: Run-Time Tracing

[RTEMS trac]

#3028: Run-Time Tracing
-----------------------------+-------------------------
 Reporter:  Spencer Goodwin  |       Owner:  chrisj@…
     Type:  project          |      Status:  new
 Priority:  normal           |   Milestone:  Indefinite
Component:  tools            |     Version:  4.12
 Severity:  normal           |  Resolution:
 Keywords:  SoC, statistics  |
-----------------------------+-------------------------

Comment (by Chris Johns):

 Excellent write up.

 The capture engine has  buffering support as well as filtering and
 triggering support to limit the data captured and to focus the trace to
 the specific area of interest. Is filtering and triggering handled by
 barectf and the YAML config file?

 The idea for the transport is to have a function call handler struct that
 is registered for each transport, ie a transport API. What the struct
 looks like and so the needed calls is unknown and I feel will be defined
 more and more over time. The simplest transport is a buffer in memory that
 can be written to a file when the trace run has finished. It would be nice
 to have a transport framework even if the detail is limited to simplest
 case.

--
Ticket URL: <http://devel.rtems.org/ticket/3028#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project