Is the laptop using the HPET for the QPC timer? (10MHz..) and the added latency[0] of calling into that is messing up the reported timings in the profiler?
I haven't checked. My workstation has a 2.53 MHz QPC that is expensive to call and (after stepping in to the function) I found that:
1) The 2.53 MHz QPC is just the rdtsc frequency divided by 1,024
2) The slowdown is from calling ReadTimeStampCounterFromEmulator, which it seems to discard the results of
My laptop doesn't run at 10.24 GHz so it probably is using HPET rather than rdtsc/1024. This makes QPC more expensive but I don't think it is messing up the reported timings - events are just outright being lost, as far as I can tell
1) The 2.53 MHz QPC is just the rdtsc frequency divided by 1,024 2) The slowdown is from calling ReadTimeStampCounterFromEmulator, which it seems to discard the results of
My laptop doesn't run at 10.24 GHz so it probably is using HPET rather than rdtsc/1024. This makes QPC more expensive but I don't think it is messing up the reported timings - events are just outright being lost, as far as I can tell