About 63,600 results
- Viewed 6k times8answered Oct 12, 2011 at 19:58
Its common to use RDTSC to get fine-grained timing information, where the overhead of a virtualization trap would be quite significant. Most common use is to have two RDTSC instructions with a small amount of code between them, taking the difference of the times as the elapsed time (number of cycles) for the code sequence. So even the overhead of pipeline drains/flushes is quite significant.
Also, since all the instruction does is read a continuously running counter, virtualizing it is quite easy -- the hardware only needs to allow saving/relo...
Content Under CC-BY-SA license Timekeeping Virtualization for X86-Based Architectures
Explore further
Why is RDTSC a virtualized instruction on modern processors?
- People also ask
xuwd1/rdtsc-notes - GitHub
An introduction to timekeeping in Linux VMs | Opensource.com
RDTSC | x86 Instruction Set Reference
Resurrecting anti-virtualization and anti-debugging: Unhooking ...
Clocks, Timers and Virtualization :: silly onions ...
__rdtsc | Microsoft Learn
Related searches for rdtsc virtualization