Changes between Version 2 and Version 3 of GCI/Coding/POSIXTimingTest


Ignore:
Timestamp:
Sep 10, 2018, 6:21:55 AM (8 months ago)
Author:
Maxul
Comment:

Beautify command lines instructions.

Legend:

Unmodified
Added
Removed
Modified
  • GCI/Coding/POSIXTimingTest

    v2 v3  
    99This task consists of adding a benchmark test to the RTEMS POSIX Timing Test Suite.  There are templates for each benchmark pattern we have identified.  The task consists of identifying the correct pattern, instantiating it using the "mktest" script, and then filling that in with the appropriate calls.
    1010For example:
     11{{{
    1112 ~/rtems/testsuites/psxtmtests>
    12 
     13}}}
    1314You'll need to specify the source (-s), the destination (-d), and the test number (-n). Change the location to match where you put rtems-testing. For example:
    14 
     15{{{
    1516 ~/rtems/testsuites/psxtmtests> ~/rtems-testing/rtems-test-template/mktest \
    1617 -s ~/rtems-testing/rtems-test-template/psxtmtest_unblocking_preempt \
    1718 -d psxtmcond04 \
    1819 -n 4
     20}}}
    1921===  Adding the Test to the Build System  ===
    2022
     
    2325Changes to Makefile.am
    2426                           rtems/testsuites/psxtmtests/Makefile.am
     27{{{
    2528  SUBDIRS += psxtmthread01
    2629  SUBDIRS += psxtmthread03
    2730  SUBDIRS += psxtmcond04 # Add a SUBDIRS entry to the bottom
    2831 endif
    29 
     32}}}
    3033Changes to configure.ac
    3134                           rtems/testsuites/psxtmtests/configure.ac
     35{{{
    3236  psxtmthread01/Makefile
    3337  psxtmthread03/Makefile
     
    3539 ])
    3640 AC_OUTPUT
    37 
     41}}}
    3842Now bootstrap it
    39 
     43{{{
    4044 cd ~/rtems
    4145 ~/rtems> ./bootstrap
    42 
     46}}}
    4347Now build...
    44 
     48{{{
    4549 cd ../b-sis
    4650 ../rtems/configure --options --used --to --configure
     51}}}
    4752===  Finding an Example  ===
    4853
    4954Now that the test has been added to the build system, find working examples of the functions to call.  One way to do that is to use grep -r.  From the terminal, there may be characters that have to be "escaped" \. For example to create a test of pthread_cond_init() put the following in the command line:
     55{{{
    5056 grep -r pthread\_cond\_init ~/rtems/testsuites/
     57}}}
    5158===  !Simulator/Emulator  ===
    5259
     
    5865
    5966After each change, clean the build directory, rebuild the source, and try again, depending on the simulator something like:
    60 
     67{{{
    6168 ~/b-sis make clean
    6269 ~/b-sis ../rtems/configure --options --to --configure
    6370 ~/b-sis make
    6471 ~/b-sis sparc-rtems4.11-gdb `find . -name ticker.exe`
    65 
     72}}}
    6673This is a particularly challenging task, so asking questions, and making suggestions for improving the directions on this task would be greatly appreciated.
    6774===  Posix Time Test Plan (for generating more GCI tasks)  ===