But SiDeLoADiNg is what is threatening users’ security.
Why?
Other hybrid kernels include Windows and BeOS, though on Windows the kernel/extension separation is less clearly defined.
https://en.wikipedia.org/wiki/Hybrid_kernel
> "Microsoft move drivers, such as GPU, to user space, to escape exactly issues like these. This is likely done for the sake of DRM, which is even worse."
Heck... NO. Drivers are still in kernel space like ever. I don't know where you got that impression. Windows isn't a microkernel, it's got plenty of kernel drivers for everything. Only UMDF Drivers are userspace, and while there are many of them, none of them are as complex as a GPU. A GPU Driver in userspace on Windows would be massively performance bottlenecked. Microsoft even states in their documentation "File system drivers, display drivers (for full display devices, not display-only display devices), and print drivers cannot be UMDF drivers."
https://docs.microsoft.com/en-us/windows-hardware/drivers/wd...
https://docs.microsoft.com/en-us/windows-hardware/drivers/di...
This has been the case since Windows Vista WDDM.
> This is likely done for the sake of DRM
The reason is hardware acceleration. No sane OS vendor is going to place every single piece of code in the kernel where DRM is involved.
> But SiDeLoADiNg
Not disagreeing, but do you have to bring it up on every single issue? I don't see the connection here.