Added some function to read the tsc with start/stop semantics
authorKevin Klues <klueska@cs.berkeley.edu>
Thu, 21 May 2009 17:29:31 +0000 (10:29 -0700)
committerKevin Klues <klueska@cs.berkeley.edu>
Thu, 21 May 2009 17:29:31 +0000 (10:29 -0700)
commit78bfbcb9d2b0b0ae0755bafc3d7b7382dd6c2653
treed76fa7d308c597f75aa9b9fc6e6e422c844287ef
parent01200fd701a458716f1bd98c54af40f5b2ac4a2e
Added some function to read the tsc with start/stop semantics

In addition to these functions, there is a training function that figures out what the correct
overhead of making the calls is so that it can be factored out before returning the time
difference.  This has not been tested on real hardware yet, and is pretty flaky in my
bochs-inside-vmware environment.  Logic seems sound though...
kern/apic.c