Add the power virus executable. Add a test mode to the pwr sensor plugin for cases (like mine) where the chipset isn't supported - just fake the power reading in those cases. Use that capability to debug the pwr sensor plugin so it is working correctly. Integrate the diag framework into the orcmd, and add a command to the orcmd_recv to run the diagnostics.
Add the new otestcmd tool to send cmds to a specified orcmd. Cleanup bugs in the power diagnostic plugin so it can run.
Minor cleanups to resolve a segfault in sensor_freq and reset governor and freq upon completing the calibration
Complete the power calibration subsystem. The power virus likely needs work to get it "viral" enough, and the database interface needs to sync'd with the database framework as it evolves.
Checkpoint new provisioning framework
Sync to r31904
Cleanup kill of power virus and remove debug
Resolve the 100% cpu problem. Creating progress threads is fine, but the event library needs something upon which it can block - otherwise, it just falls thru. So for each progress thread we create, create a pipe and set an event to fire when the read end is ready - but never write anything into it. This will block the event progress thread, but still allow other events to fire.
Cleanup the repeated code to support progress thread creation and stopping by putting it in a common place in orcm/runtime/orcm_progress.[h|c]. Modify all the current uses to use the new functions.

Also, cleanup some CRLF ends to two files as it keeps getting flagged by git.