schedulersimplesmp priority lifo on executing

[Jennifer Averett]

Attached is a scheduler simulator scenario, expected, and output files from one of
the  tests for the smp simple scheduler.  It appears that tasks of
 the same priority running on different cores are no longer selected for
preemption in fifo order.  The executing list is FIFO per priority and the
search is from the rear so the newest at a priority is selected, not
the oldest.

This was confirmed on the simple SMP priority but should also be on
the regular SMP priority. I just haven't confirmed it yet.

This is the type of thing the scheduler simulator is very good at helping
to root out. I don't know if a test exists to verify this behaviour. But it changed
from the original implementation.

Jennifer Averett
On-Line Applications Research
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cpus4_pick_older.scen
Type: application/octet-stream
Size: 938 bytes
Desc: cpus4_pick_older.scen
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140512/3a3c6cbc/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cpus4_pick_older.output
Type: application/octet-stream
Size: 5375 bytes
Desc: cpus4_pick_older.output
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140512/3a3c6cbc/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: cpus4_pick_older.expected
Type: application/octet-stream
Size: 5375 bytes
Desc: cpus4_pick_older.expected
URL: <http://lists.rtems.org/pipermail/devel/attachments/20140512/3a3c6cbc/attachment-0002.obj>