On Sat, Feb 1, 2014 at 7:43 AM, Clemens Ladisch <clem...@ladisch.de> wrote: > Andy Lutomirski wrote: >> The HPET is so amazingly slow that this is barely a win. > > What happens on CPUs where the TSC cannot be used for the clock?
vclock_gettime, etc will fall back to using syscalls, just like they would on systems using the PIT timer. > >> it scares me a tiny bit to map a piece of crappy hardware where every >> userspace program can poke at it (even if said poking is read-only). >> Let's just remove it. > > So this mapping is a backdoor to bypass the restrictions on /dev/hpet? ;-) > Yes, except that it's read-only. At some point, someone will probably want to run code in a sandbox that can't tell time at all. That will be messy, but this is a decent first little step. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
