On Fri, 4 Mar 2016, Andy Lutomirski wrote: > Thomas, I still think we should consider just deleting the HPET vclock > code and accept the syscall overhead on systems that are stuck using > HPET. If fast syscalls are available (which should include every > system with HPET, unless there are some 32-bit AMD systems lying > around), then the overhead in a syscall is *tiny* compared to the code > of the HPET read itself.
No objection from my side, really.
Thanks,
tglx
