5 ms·
...and extend. I'm sure this architecture was easier for MS but it opens the door to code that runs on WSL2 that doesn't run on regular Linux.
by wmf 7y ago
...and extend. I'm sure this architecture was easier for MS but it opens the door to code that runs on WSL2 that doesn't run on regular Linux.
- deleted 7y ago[deleted]
- modeless 7y agoThis patch adds WDDM (Windows Display Driver Model) as a Linux kernel API. The implementation just forwards to the Windows kernel, but it seems to me like someone could implement it natively in Linux. Then Windows user mode graphics drivers would work natively in Linux without WSL, and DX12 too.
- wmf 7y agosomeone could implement it natively in Linux This is exactly what we don't want. There's already plenty of effort wasted on GBM vs. EGLStream so introducing a third API would just lower quality even more.
- int_19h 7y agoThis isn't merely another API, though. It's the one against which most graphics drivers are written.
- atq2119 7y agoThis is actually debatable. How many different GPUs are supported on Windows vs ob Linux? There are really only three vendors left on PC, while Linux supports these as well as a bunch of mobile GPUs...
- modeless 7y agoThis "third API" is already well supported by every relevant graphics vendor. Adopting it would actually reduce the number of APIs vendors need to deal with. And the quality of WDDM drivers has always been higher than anything Linux has.
- Lammy 7y ago> And the quality of WDDM drivers has always been higher than anything Linux has. And the outcome of implementing this seems to ensure it will stay that way.
- Hello71 7y agoReally? The experience of AMD users has historically tended to be at odds with that statement.
- kelnos 7y agoGreat, just what I want, vendors to be incentivized to force me to run closed binary blobs on my Linux box because they'll just repackage their Windows driver and still not release its source.
- rasz 7y agoWe definitely wouldnt want a stable driver API! NDISwrapper was a huge step in the right direction.
- jfkebwjsbx 7y agoGPU vendors could expose their driver to the WDDM API in Linux, though.
- mappu 7y agoPresumably the NVIDIA Linux driver can be replaced with a shim over this, and we can all forget about EGLStreams.
- pkulak 7y agoIt doesn't just open the door, it absolutely requires it.
- belltaco 7y agoHow? For example code that uses CUDA on Linux, calls the GPU CUDA driver, which passes it on to the Windows part of the interface. How does that require user code that doesn't run on normal Linux to take advantage of this?
- Analemma_ 7y ago> it opens the door to code that runs on WSL2 that doesn't run on regular Linux That's a strange complaint. Would you be happier if this was merged into the mainline kernel instead?
- wmf 7y agoWhat I mean is imagine an app that supports "Linux" but it only runs on WSL2; it doesn't run on real Linux. That would be bad IMO.
- josteink 7y agoThis emulates a GPU driver. If I understand it correctly, it just means that GPU-accelerated code that previously only ran on "proper" Linux now can run on WSL too, being powered by DirectX behind the scenes. What's bad about that?
- diffeomorphism 7y agoYou don't understand it correctly. Nobody is complaining or even talking about the gpu driver. > DxCore & D3D12 on Linux Projecting a WDDM compatible abstraction for the GPU inside of Linux allowed us to recompile and bring our premiere graphics API to Linux when running in WSL. This is the real and full D3D12 API, no imitations, pretender or reimplementation here… this is the real deal. l > libd3d12.so and libdxcore.so are closed source, pre-compiled user mode binaries that ship as part of Windows. These binaries are compatible with glibc based distros and are automatically mounted under /usr/lib/wsl/lib and made visible to the loader. In other words, these APIs work right out of the box without the need to install additional packages or tweak the distro’s configuration. Support is currently limited to glibc based distros such as Ubuntu, Debian, Fedora, Centos, SUSE, etc… So you can use it with MS blessed distros and only when running under WSL2. You can't use it without WSL2.
- josteink 7y agoOK. That's different. That sounds extendish indeed.
- blasdel 7y agoIn a previous life I wrote code that only ran in Cygwin, it depended on a dummy networking driver to talk to the WinCE core of a sonogram machine. Running Windows VMs as kernels for Cygwin environments felt less weird than most modern container architectures.
- Rusky 7y agoIn the linked thread the Microsoft developers explicitly deny that this is the intent, if that's worth anything to you. The goal, rather, is to take all the usual (for the Linux side) GPU stuff and give it access to the Windows host's GPU, when running on WSL. That is, they are already working on getting OpenGL/Vulkan/etc. to run on top of this: https://www.collabora.com/news-and-blog/news-and-events/introducing-opencl-and-opengl-on-directx.html https://www.collabora.com/news-and-blog/news-and-events/intr... Rather than "get people to write code that runs on WSL2 but not regular Linux," the goal is "get code that runs on regular Linux but not WSL to run on WSL2."
- ghostpepper 7y agoDoes the intent matter if the result is the same?
- xabotage 7y agoThe developers' word is irrelevant. Microsoft is a business. Microsoft will pursue its long term business interests. Developers are hired to do what the business directs. So the question is really, "what would best serve Microsoft's business interests?" and not "what do the developers intend?" because in time only one question matters and unfortunately it's not the one with the best interests of non-windows-users in mind.
- Rusky 7y agoThe developers' intent does align with Microsoft's current interests -- as you say, they are hired to do what the business directs. Perhaps their interests will shift in the future, as they clearly have in the past. But the things they build now are not from the "extend" phase of an EEE arc. At worst they are in the "embrace" phase.
- squarefoot 7y ago> but it opens the door to code that runs on WSL2 that doesn't run on regular Linux. Which is exactly what I was expecting since day one when WSL was announced. WSL is going to slowly kill Linux, or to be more accurate, it will kill any Linux (be it on servers or desktops) not Microsoft branded and distributed. Forks on smaller embedded systems will resist for a while, until one day MS decides to port some killer technology de facto embracing them as well.
- dade_ 7y agoYeah, but right now it solves the problem of not being able to run code on WSL that does run fine in Linux. What really stops me from using Linux on the Desktop is compatibility issues with my laptop(s), reliable sleep/wake and rendering issues with High DPI display. Microsoft released an MS Teams client for Linux which astonished me. So, I am giving them the benefit of the doubt for the time being.
- wvenable 7y agoMicrosoft hasn't given up on Windows but having lost the mobile space I think they've decided to go back to their roots of developing software for many operating systems. It doesn't matter if you run Windows, Mac OS, Android, or iOS if they can sell you an Office 365 subscription. The Windows protectionism that dominated the 2000's doesn't help Microsoft sell more product anymore. It's not so much that Microsoft has changed but that the world has changed and Microsoft is changing with it.
- turbinerneiter 7y agoThe Teams client in Linux sucks, it is missing half the features and you have to pkill it after use, because simply closing it doesn't actually stop the program + it spins your fan like crazy doing God knows what in the background. Still, thanks, I guess.
- _ph_ 7y agoAgree. I am also looking for a laptop to mainly run Linux on. This quite widens the choices for me. Also, what keeps me and probably many others from running 100% Linux is the requirement of some commercial applications which are not available for Linux. So far using a Mac with a Linux VM was the best compromise for me, but now Windows becomes an appealing alternative.
- empath75 7y agoMicrosoft doesn’t consider desktop Linux its competition, it considers MacOs its competition. It’s going after macbook’s position as the default developer laptop and Apple deserves what’s coming to them IMO, for neglecting it for so long.
- jfkebwjsbx 7y ago> after macbook’s position as the default developer laptop Perhaps in your country/field. Certainly not in mine...
- iphone_elegance 7y agoSorry I can't hear you over the airplane engine that's apparently inside the 16inch mbp
- zozbot234 7y ago> that doesn't run on regular Linux. DirectX does run on regular Linux, courtesy of Wine/Proton. It's just a matter of reimplementing the userspace .so interface that MS will provide for access to this facility, so that it hooks into that support instead.
- kristopolous 7y agoThat's not the point. They are trying to not IBM themselves. They and the clones won the war with IBM in the 80s and 90s because IBM was worried about things that didn't matter: they wasted time with things like an operating system CP/X86 that ran DOS and 3270 emulators to their mainframes on top of a GUI system called mermaid (3270 PC) while Microsoft was writing Windows 3. Oh yeah did I mention some configurations cost $20,000 each? some configurations cost $20,000 each. Because IBM wanted to secure its AS/400 minicomputers, mainframe, and microcomputer line and make them interoperable, as if a PC user sitting in their den would be connecting with $500,000 or so of other IBM machines, everyone else ran circles around IBM. They kept up the "whole kitchen sink" system way way past its due date. This also happened to DEC, which responded way too late in the game to be relevant, SUN, SGI, and Wang. And it may eventually take down Oracle. So they're intentionally taking an uncommitted, decoupled approach. I'm paying Microsoft as a result. I pay GitHub and Azure bills every month and run exclusively Linux. They can't sway around as a monopoly like they could in 2000, once Ballmer left things changed rapidly. It's not going back. They have effectively zero cloud software (database/operating system etc), effectively zero mobile presence, and most people don't really like Windows. In a tightly coupled stack you're only as strong as your weakest link, and MS has a bunch. Their biggest risk now is to HP or GM themselves; basically gobble up a bunch of things, blend it into indifferentiable blandness and collapse while waving a giant sceptre labelled "greatest company of 30 years ago" (HP bought DEC, Cray, Tandem, Apollo, Convex, 3Com, Phoenix, Palm and SGI and did effectively nothing with them beyond slapping an HP logo on their final pre acquisition product line and then just rode it out without any followup. HP knowing only how to fumble the ball every time for 20 years is why big business switched to Linux. HP took all the alternatives behind the barn one by one, cut them a fat check and then shot them. Simply crazy) So yeah, it's a different game now.
- TheRealDunkirk 7y ago> And it may eventually take down Oracle. Oracle is basically a department of the NSA/CIA/FBI. Sales to companies are just cover for the real game. It will never go away.