Real-Time Scheduling Etudes Part 3

1. For the scheduling project, it will be very helpful to generate your own events at interesting times during execution of your experiments. QNX provides a user event mechanism that can insert events into the kernel event logging data that you analyze with the System Analysis Tool. Bring back the Simple project and add a user event that you can use to measure the period of the simple task. Run an experiment to gather timing information for your user events. Compute the mean and standard deviation of the period of simple. Before the end of class, deposit your Simple.c file into the User Events dropbox with your names and the mean and standard deviation for the period of simple in the dropbox description field.
   
   
2. Discuss your individual ideas for the scheduling test fixture. From these ideas, design your team's test fixture architecture and describe that design in a Word document. In addition to what you considered for your individual test fixture ideas, among other things, you will want to also think about: a tasking structure; how to do synchronization; how to make sure that each task computes, i.e. burns CPU cycles, for its compute time; what you will do when a task completes, when a task's next period starts; how to determine when the next period starts. Before the start of the next class, deposit that document into the Scheduling Test Fixture Architecture dropbox. Put the names of both team members at the top of the document and in the description area when you deposit the file in the dropbox.