Microsoft Reworks The "DXGKRNL" Driver It Wants To Get Into The Linux Kernel

[phoronix]

Phoronix: Microsoft Reworks The "DXGKRNL" Driver It Wants To Get Into The Linux Kernel

Back in 2020 Microsoft announced the DXGKRNL driver as the kernel driver component for supporting GPU accelerated use-cases within Windows Subsystem for Linux (WSL2). That original DXGKRNL driver was quickly shot down by upstream kernel developers and various issues raised while now for the past year Microsoft has been reworking this kernel driver and on Wednesday published the new version...

https://www.phoronix.com/scan.php?page=news_item&px=Microsoft-DXGKRNL-2022

[-MacNuke-]

Is there any plan from Microsoft to make to opposite implementation too? DirectX support in Windows VMs on a Linux host?

[GI_Jack]

Is there any plan from Microsoft to make to opposite implementation too? DirectX support in Windows VMs on a Linux host?

Until there is, these changes should not be mainlined. Simply put, does not contribute anything any of us need or want, and does nothing but encouraging migrating OFF linux.

[Quackdoc]

literally just talking about how they could extend it to support vulkan the other day. if they actually make it work for vulkan, ill be happy with it myself

[Quackdoc]

Is there any plan from Microsoft to make to opposite implementation too? DirectX support in Windows VMs on a Linux host?

lol no chance. however with vulkan venus, there is incentive to get that working within windows do to high preformance, and mesa already has a d3d10umd gallium state tracker, it would need work, but getting it to work with zink... not an impossible task

[incepted]

Until there is, these changes should not be mainlined. Simply put, does not contribute anything any of us need or want, and does nothing but encouraging migrating OFF linux.

Actually, for those of us that have to run Windows due to corporate policies but want a sane and familiar development environment; this is a major need. However, I agree that the opposite implementation is definetly a requirement as well.

[-MacNuke-]

Until there is, these changes should not be mainlined. Simply put, does not contribute anything any of us need or want, and does nothing but encouraging migrating OFF linux.

Well, one could argue that is makes the entry in Linux ecosystem easier since you don't need to move anywhere in the first place. Just download an app and start to learn instead of "repartition your drive and setup dualboot". Since the major blocker for a Desktop Linux in a VM is always the graphics performance.

[Sonadow]

Until there is, these changes should not be mainlined. Simply put, does not contribute anything any of us need or want, and does nothing but encouraging migrating OFF linux.

Typical Linux copium and whining with the "Oh boo hoo we are not capable enough to make something as good as DirectX by ourselves so Microsoft is bad and they must give away the API they spent billions to create and maintain for free because I say so"

[-MacNuke-]

lol no chance. however with vulkan venus, there is incentive to get that working within windows do to high preformance, and mesa already has a d3d10umd gallium state tracker, it would need work, but getting it to work with zink... not an impossible task

The problem is that Windows drivers need to be signed and it gets harder and harder to install non-signed drivers. And signing drivers cost money. That's why you get signed virtio-drivers for Windows from RedHat only if you have a subscription.

So having something official would be great.

And due to the advancements in containerization my personal need for hardware-accellerated Linux VMs on Linux is nearing 0.

[ssokolow]

Typical Linux copium and whining with the "Oh boo hoo we are not capable enough to make something as good as DirectX by ourselves so Microsoft is bad and they must give away the API they spent billions to create and maintain for free because I say so"

More "If they're going to make it difficult to run Windows on Linux, why should we make it easy to run Linux on Windows?" After all, this is essentially Microsoft trying to make it unnecessary for people to shrink their market share and migrate off whatever Ring 0 equivalents to Intel ME they decide to build in.

Do remember that Windows 11 is the next tightening of the "must Secure Boot" ratchet and, with Windows 8, they originally wanted to make Secure Boot on x86 something you couldn't disable or re-key before the backlash forced them to limit that to ARM.