[RTEMS SMP ISVV] : rtems_clock_get_ticks_per_second and rtems_clock_get_ticks_since_boot

[Luis Alves]

Dear RTEMS community,



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 https://rtems-qual.io.esa.int/).



While analysing in the Software Configuration File (SCF) which items are or
not pre-qualified, the following has been noticed:



   - rtems_clock_get_ticks_per_second() and
   rtems_clock_get_ticks_since_boot() functions are listed in section 4.10 of
   the SCF (which list pre-qualified items “which may be directly used by
   applications”).
   - In the ICD there are duplicated items described with these names, a
   function, and a macro. Moreover:
      - In the ICDs the macros using these names are described with the
      “The directive is not included in the pre-qualified feature set of RTEMS.
      Applications which are restricted to only use interfaces of the
      pre-qualified feature set of RTEMS shall not use the directive.”
   - Looking at the code (at retems-qual-only), the macros are defined
   alongside and right after the function’s declarations (redirecting function
   calls to the values of the _Watchdog_Ticks_per_second and
   _Watchdog_Ticks_since_boot, respectively).
      - So, rtems_clock_get_ticks_per_second and
      rtems_clock_get_ticks_since_boot  macros will be used in the qual-only
      setup, whereas ICD tells us that these macros are “not included in the
      pre-qualified feature set”.



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)?



Thanks in advance for the clarifications,



Kind Regards

Luís Alves
Critical Software
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20220923/416deef8/attachment.htm>