<div dir="ltr">
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Dear RTEMS
community,<span></span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">I’m part of
the team performing the Independent Software Verification and Validation (ISVV)
of the RTEMS SMP Qualification Data Pack (which is being provided through <a href="https://rtems-qual.io.esa.int/" style="color:rgb(5,99,193);text-decoration:underline">https://rtems-qual.io.esa.int/</a>).<span></span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">While
trying to setup tests to assert the overall “Timer Server” feature, one has
realized that:<span></span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<ul style="margin-top:0cm;margin-bottom:0cm" type="disc"><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Although rtems_timer_initiate_server() is mentioned within section
4.10 of the SW Configuration File (SCF) as a pre-qualified item (“<i>which
may be directly used by applications</i>”), one gets build issues while
trying to use it, as it depends on rtems_timer_create().<span></span></span></li><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">The same SCF (within section 4.9.3) also says: “<i>The rtems_task_create()
directive is pre-qualified, however, it is only available if a custom
stack allocator is configured. It is recommended to use
rtems_task_construct() instead</i>”:<span></span></span></li><ul style="margin-top:0cm;margin-bottom:0cm" type="circle"><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Isn’t this contradictory, as:<span></span></span></li><ul style="margin-top:0cm;margin-bottom:0cm" type="square"><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Both rtems_timer_initiate_server() and tems_task_create() are
listed within SCF section 4.10 and<span></span></span></li><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">at the start of section 4.10, it is said that listed items are “<i>pre-qualified
items .. which may be directly used by applications</i>”? <span></span></span></li></ul></ul><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Given this, shouldn’t rtems_timer_initiate_server() natively use of
rtems_task_construct() rather than rtems_timer_create() as advised?<span></span></span></li><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">This makes other two functions listed within SCF section 4.10 as
not directly usable, namely rtems_timer_server_fire_after() and
rtems_timer_server_fire_when() as those are to be used in conjunction with
rtems_timer_initiate_server().<span></span></span></li><li class="gmail-MsoListParagraph" style="margin:0cm 0cm 0cm 18pt;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">In a nutshell, this compromises the overall “Timer Server” feature
in the qual-only setup of the QDP.<span></span></span></li></ul>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Can the
community help to clarify these points, and tell us what and how can one
improve the RTEMS SMP QDP w.r.t. this (at the documentation and qual-only
implementation level)?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Thanks in
advance for the clarifications,<span></span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm;font-size:11pt;font-family:"Calibri",sans-serif"><span lang="EN-GB">Kind
Regards<span></span></span></p>
<div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div><br></div><div>Luís Alves</div><div>
<div style="font-family:arial,helvetica,sans-serif" class="gmail_default">Critical Software</div>
</div></div></div></div></div></div></div></div>