Re: "Think of it more as a workaround than a resolution" @LDS
It's a long time since I've had to read an Intel CPU data sheet.
Was (prior to this) mapping kernel code into every application's virtual memory space their recommended way of calling kernel functions from an application for better performance, or did they advocate a proper separation and context switch?
Biting the hand that feeds IT
