<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 9/4/2014 12:57 PM, Jennifer Averett
wrote:<br>
</div>
<blockquote
cite="mid:84DFB03DEB1A9C49AC40B1F3F18E72B104BCA87BD6D9@OARmail.OARCORP.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Chris suggested the following approach:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">>Another approach could involve adding
the task data to the trace buffer when the first reference <o:p></o:p></p>
<p class="MsoNormal">> to the task is added to the trace
buffer. You would add the task data tagging it with some sort
of "id". <o:p></o:p></p>
<p class="MsoNormal">> When added events related to the task
the "id" is used. The trace buffer decoder extracts the task
data <o:p></o:p></p>
<p class="MsoNormal">> building a suitable table to decode
the following "id" references. There is a small extra bump
filling the <o:p></o:p></p>
<p class="MsoNormal">> trace buffer with the task details but
this is the cost of tracing in software. This approach helps
solves <o:p></o:p></p>
<p class="MsoNormal">> the problem of off board streaming of
the trace data.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Using this approach are there any
suggestions for how the capture control information currently<o:p></o:p></p>
<p class="MsoNormal">accessed through the capture task would be
handled?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</blockquote>
Piling on... most of the information in the capture engine's task
control blocks<br>
can be logged statically on task create. BUT... there is also
trigger information<br>
in there. Where should that be now?<br>
<br>
Jennifer is plowing ahead logging variable length records and
eliminating<br>
fields in the capture task control but we don't see how to get rid
of all of it.<br>
<pre class="moz-signature" cols="72">--
Joel Sherrill, Ph.D. Director of Research & Development
<a class="moz-txt-link-abbreviated" href="mailto:joel.sherrill@OARcorp.com">joel.sherrill@OARcorp.com</a> On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985</pre>
</body>
</html>