Redundant Logging on User Extensions

[Gedare Bloom]

On Wed, Oct 29, 2014 at 2:42 PM, Joel Sherrill
<joel.sherrill at oarcorp.com> wrote:
> Hi
>
> As Jennifer has reviewed the output from an SMP capture
> test, it is clear that something which was no big deal in
> the old fixed record uniprocessor version is now an issue.
> Most extensions have an "actor" and "acted upon" thread.
> For example, when a task is created, the calling task and
> new task are important. The actor and acted upon threads
> were logged in separate records.
>
> In an SMP system sorted by time, these two records can
> become disconnected. Since we now have variable length
> records, it makes sense to consolidate these into a single
> capture record.
>
> Any complaints?
>
You probably want to support multiple ways to view the capture log,
including sorting by core, or by some notion of "system call" e.g. the
entire chain of events for a single thread creation.

-Gedare

On Wed, Oct 29, 2014 at 2:42 PM, Joel Sherrill
<joel.sherrill at oarcorp.com> wrote:
> Hi
>
> As Jennifer has reviewed the output from an SMP capture
> test, it is clear that something which was no big deal in
> the old fixed record uniprocessor version is now an issue.
> Most extensions have an "actor" and "acted upon" thread.
> For example, when a task is created, the calling task and
> new task are important. The actor and acted upon threads
> were logged in separate records.
>
> In an SMP system sorted by time, these two records can
> become disconnected. Since we now have variable length
> records, it makes sense to consolidate these into a single
> capture record.
>
> Any complaints?
>
> --
> Joel Sherrill, Ph.D.             Director of Research & Development
> joel.sherrill at OARcorp.com        On-Line Applications Research
> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
> Support Available                (256) 722-9985
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel