Disabled unless explicitly requested at configure time. We can assume RDTSCP for now and user-specified TSC to avoid the complexity of detecting available cycle counter methods and reference cycle rate.
The benchmark routine should also use RDTSCP (and a conversion to nanoseconds based on the TSC frequency) to self validate and report if the total elapsed time for all iterations roughly matches the time reported by clock_gettime().
carns
commented
3 years ago
Disabled unless explicitly requested at configure time. We can assume RDTSCP for now and user-specified TSC to avoid the complexity of detecting available cycle counter methods and reference cycle rate.
The benchmark routine should also use RDTSCP (and a conversion to nanoseconds based on the TSC frequency) to self validate and report if the total elapsed time for all iterations roughly matches the time reported by
clock_gettime().