<html><head></head><body lang="en-US" style="background-color: rgb(255, 255, 255); line-height: initial;"> <div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Sorry for the top post.</div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br></div><div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Is there any dtrace support in RTEMS (assuming that it's even a possibility)?</div> <div style="width: 100%; font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);"><br style="display:initial"></div> <div style="font-size: initial; font-family: Calibri, 'Slate Pro', sans-serif, sans-serif; color: rgb(31, 73, 125); text-align: initial; background-color: rgb(255, 255, 255);">Sent from my BlackBerry 10 smartphone on the Virgin Mobile network.</div> <table width="100%" style="background-color:white;border-spacing:0px;"> <tbody><tr><td colspan="2" style="font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"> <div style="border-style: solid none none; border-top-color: rgb(181, 196, 223); border-top-width: 1pt; padding: 3pt 0in 0in; font-family: Tahoma, 'BB Alpha Sans', 'Slate Pro'; font-size: 10pt;"> <div><b>From: </b>Joel Sherrill</div><div><b>Sent: </b>Sunday, May 28, 2017 9:24 AM</div><div><b>To: </b>Andreas Kölbl</div><div><b>Reply To: </b>joel@rtems.org</div><div><b>Cc: </b>rtems-users@rtems.org</div><div><b>Subject: </b>Re: Rhealstone detailed benchmark</div></div></td></tr></tbody></table><div style="border-style: solid none none; border-top-color: rgb(186, 188, 209); border-top-width: 1pt; font-size: initial; text-align: initial; background-color: rgb(255, 255, 255);"></div><br><div id="_originalContent" style=""><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 28, 2017 at 6:43 AM, Andreas Kölbl <span dir="ltr"><<a href="mailto:andreas.koelbl@st.oth-regensburg.de" target="_blank">andreas.koelbl@st.oth-regensburg.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi guys,<br>
<br>
I've tried measuring the real time capability of a BSP using the<br>
Rhealstone benchmark. This benchmark only tells about the average time<br>
spent for e.g. task switching.<br>
Is there interest in a more fine-grained Rhealstone benchmark, which<br>
prints the Worst Case Execution Time (WCET) or the deviation of the<br>
measured values?<br>
Has there already been an attempt to modify Rhealstone in order to get<br>
the WCET from each benchmark?<br></blockquote><div><br></div><div>Rhealstone was a proposal from someone at Intel in 1989 that appeared</div><div>in Dr Dobbs Journal. </div><div><br></div><div><a href="http://www.drdobbs.com/article/print?articleId=184408081&siteSectionName=">http://www.drdobbs.com/article/print?articleId=184408081&siteSectionName=</a><br></div><div><br></div><div>There was a follow up article a year later with some code which I didn't</div><div>remember. I am not sure how closely the code written for RTEMS follows</div><div>that code. </div><div><br></div><div><a href="http://www.drdobbs.com/article/print?articleId=184408332&siteSectionName=cpp">http://www.drdobbs.com/article/print?articleId=184408332&siteSectionName=cpp</a><br></div><div><br></div><div>AFAIK there is no "standard" source for this benchmark -- just the definitions</div><div>and some odd code for a few RTOSes.</div><div><br></div><div>We would welcome a review of the code against the original articles</div><div>and the code they published as well as improvements in the numbers</div><div>gathered and their reporting. Statistical information and WCET would</div><div>be valuable if the code accurately reflects the intended measurement.</div><div><br></div><div>One thing I have noticed in benchmarks over the years is that they</div><div>may want to measure say blocking time of a semaphore with a </div><div>set of N threads. But they accidentally include the code associated</div><div>with the first execution of each thread. So you have to be careful</div><div>to not include unintended overhead.</div><div><br></div><div>Sorry for the long answer but if you are interested in these benchmarks,</div><div>you are encouraged to help improve them. </div><div><br></div><div>--joel</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
--<br>
Andreas Kölbl<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/users</a></blockquote></div><br></div></div>
<br><!--end of _originalContent --></div></body></html>