[QUESTION] Use with wsl2?

microsoft / OpenCLOn12

The OpenCL-on-D3D12 mapping layer

MIT License

108 stars 15 forks source link

[QUESTION] Use with wsl2? #32

Open lmeyerov opened 2 years ago

lmeyerov commented 2 years ago

The README.md shows build instructions on the windows side, but I'm unclear if/how to use this from wsl2. Our goal is to run an opencl app on nvidia hw. Any more guidance?

once built, do we need to move the generated files anywhere, on the windows host or ubuntu guest side?
- currently on our linux-native side we assume a nvidia driver + apt-get install ocl-icd-libopencl1 ocl-icd-opencl-dev opencl-headers
does this change how we need to install/link opencl headers?
- currently we do variants of https://github.com/mikeseven/node-opencl/blob/c059fee1fea1fb417c7e5b30fac78001826efb5e/binding.gyp#L44
are there tickets we should track for wsl2 + mesa integrations?

Blogposts suggest all this will be upstreamed to mesa, but I'm guessing for now, we should be doing something more manual along the lines of the above questions..

jenatali commented 2 years ago

Building for Linux is something we'd like to add, but is not currently supported.

oscarbg commented 1 year ago

any update?

jenatali commented 1 year ago

No, this hasn't been a priority yet.

MathiasMagnus commented 1 year ago

I would very much like to see this feature being supported. I can only dream of WSL2 and WSA both being supported. Local CI dreams come true...

Entropy512 commented 1 year ago

I am curious if there's any update on the roadmap here.

Is the future plan to upstream this component to Mesa as originally envisioned, or longterm move to a different architecture, since Rusticl supports various hardware acceleration backends now?

e.g. Rusticl with a D3D12 backend, or maturing https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24839 (Rusticl on Zink) and Dozen so that they work together?

jenatali commented 1 year ago

Is the future plan to upstream this component to Mesa as originally envisioned

This was never the intention. This component is intentionally separate.

I don't have any timeline updates. I'd still love it to happen, but it hasn't been prioritized yet. I could potentially see rusticl+zink+dozen arriving sooner.

Entropy512 commented 1 year ago

This was never the intention.

Ah, I must have misinterpreted https://devblogs.microsoft.com/directx/in-the-works-opencl-and-opengl-mapping-layers-to-directx/ which implies that it was.

rusticl+zink+dozen would be fine too - hopefully that becomes at least partially usable soon