how to change the time on the muscle driver timer

Hence TSC ticks are counting the passage of time, not the number of CPU clock cycles elapsed. With these processors, the TSC ticks at the processor's nominal frequency, regardless of the actual CPU clock frequency due to turbo or power saving states. Recent Intel processors include a constant rate TSC (identified by the _tsc sysctl on FreeBSD or by the ' constant_tsc' flag in Linux's /proc/cpuinfo). Relying on the TSC also reduces portability, as other processors may not have a similar feature. In those latter cases, to stay relevant, the program must re-calibrate the counter periodically. Even then, the CPU speed may change because of power-saving measures taken by the OS or BIOS, or the system may be hibernated and later resumed, resetting the TSC.

Therefore, a program can get reliable results only by limiting itself to run on one specific CPU. There is no promise that the timestamp counters of multiple CPUs on a single motherboard will be synchronized. With the advent of multi-core/ hyper-threaded CPUs, systems with multiple CPUs, and hibernating operating systems, the TSC cannot be relied upon to provide accurate results - unless great care is taken to correct the possible flaws: rate of tick and whether all cores (processors) have identical values in their time-keeping registers. The Time Stamp Counter was once an excellent high-resolution, low-overhead way for a program to get CPU timing information.

4 Use in exploiting cache side-channel attacks.

How to change the time on the muscle driver timer