Microsoft Posts Updated "DXGKRNL" Linux Kernel Driver For WSL/WSA

[Quackdoc]

no there isnt a full oss path, i already checked.

They were also told ioctls would be rejected and its rammed with them.

What do you mean you checked? any evidence? they have a foss kernel, and foss userland.

also calling BS on ioctls, last time I checked, "one-patch-per-ioctl", does not mean they will be rejected

https://lore.kernel.org/lkml/[email protected]/

[mSparks]

What do you mean you checked? any evidence? they have a foss kernel, and foss userland.

also calling BS on ioctls, last time I checked, "one-patch-per-ioctl", does not mean they will be rejected

https://lore.kernel.org/lkml/[email protected]/

https://lkml.org/lkml/2022/2/5/64

requires libdxcore. source?

[Quackdoc]

https://lkml.org/lkml/2022/2/5/64

requires libdxcore. source?

https://github.com/microsoft/libdxg

[mSparks]

https://github.com/microsoft/libdxg

did you actually look at the src include folder?
Thats not libdxcore, its a wrapper for it.

[Quackdoc]

did you actually look at the src include folder?
Thats not libdxcore, its a wrapper for it.

this provides necessary bits to talk to "compute device abstraction layer" it's stripped down, but you do not any longer need the full dxgcore for the kernel bits to function

[mSparks]

this provides necessary bits to talk to "compute device abstraction layer" it's stripped down, but you do not any longer need the full dxgcore for the kernel bits to function

so it works on linux hosts now?

[Quackdoc]

so it works on linux hosts now?

does any hyperv bit work on a linux host?

[mSparks]

does any hyperv bit work on a linux host?

you said there was a full oss path. Since hyperv the kernel policy chaged to require a full oss path to upstream it.

Upstream will test it on linux hosts. They care exactly zero percent about any other hosts.

[Quackdoc]

you said there was a full oss path. Since hyperv the kernel policy chaged to require a full oss path to upstream it.

Upstream will test it on linux hosts. They care exactly zero percent about any other hosts.

uh, no. they are still receiving and implementing hyper-v patches. they only care about linux side. as far as I am aware

[mSparks]

uh, no. they are still receiving and implementing hyper-v patches. they only care about linux side. as far as I am aware

Heres what they were told back in may 2020. including not to use ioctls
https://lists.freedesktop.org/archiv...ay/266642.html

None of this has been done afaict. still requires libdxcore (even says so in the latest patch notes) which is still closed source. So is the hardware specific part.

Anyway. Not me that needs convincing, its older more experienced stubborn dudes with beards that wouldnt install windows if you paid them.

If you think "you maintain hyperv from more than a decade ago so must do this even though its against your current policy and you hate it" will sway them, all I can say is "good luck with that".