4 ms·
>Gamers and compute-oriented workloads won't be hurt hardly at all. Actually KPTI doesn't only affect syscall but also interrupts. It makes interrups slower, w
by int0x80 9y ago
>Gamers and compute-oriented workloads won't be hurt hardly at all.
Actually KPTI doesn't only affect syscall but also interrupts. It makes interrups slower, which affects every workload.
- cptskippy 9y agoGamers like to use PS/2 peripherals because they're interrupt based and thus more responsive than USB peripherals. Does this mean they could take a hit due to this bug?
- dfox 9y agoInterrupts from ps/2 are pretty insignificant in comparison to all other interrupt traffic on any PC. Edit: also "interrupt-based" in this case has nothing to do with interrupts seen by the CPU. Difference is that in ps/2 the device can send data to the controller (which then generates interrupt) at any time, while for usb the controller periodically polls devices for data (and possibly generates interrupt if there are some). In the early days of USB and UHCI host controllers this polling was done in software, but since USB 2.0 this is done in hardware and generates real cpu interrupts when usb device requests interrupt (although with somewhat unpredictable but bounded latency)
- cptskippy 9y agoThanks, that's really useful information. I wasn't aware that USB 2.0 switched to hardware based polling.