Cycles: improve oneAPI requirements text in the UI #109644

Xavier Hallade · 2023-07-03T13:41:19+02:00

Xavier Hallade commented

2023-07-03 13:41:19 +02:00

No response

_No response_

👍 1

Xavier Hallade added 1 commit 2023-07-03 13:41:31 +02:00

0fcc74bbd6 Cycles: improve oneAPI requirements text in the UI

Xavier Hallade requested review from Brecht Van Lommel 2023-07-03 13:42:23 +02:00

Xavier Hallade added this to the 4.0 milestone 2023-07-03 13:42:37 +02:00

Xavier Hallade added this to the Render & Cycles project 2023-07-03 13:42:42 +02:00

Xavier Hallade referenced this pull request from blender/blender-manual

2023-07-03 13:45:24 +02:00

Update oneAPI driver requirements for Cycles #104505

Alaska commented

2023-07-03 14:19:05 +02:00

I just wanted to bring up some points on the Linux side of things.

From my understanding on Linux we need intel-level-zero-gpu for oneAPI to work properly. And for many Linux distrobutions, the intel-level-zero-gpu isn't a stand alone package, but instead bundled with the intel-compute-runtime package. Hence why this Pull Request lists intel-level-zero-gpu or intel-compute-runtime as the requirements.

But this isn't true is it? We don't need intel-level-zero-gpu **OR** intel-compute-runtime, we need intel-level-zero-gpu and intel-compute-runtime is the most common way of obtaining this package on many distributions. But having intel-compute-runtime installed doesn't guarantee that you'll have intel-level-zero-gpu (E.G. Your package maintainer doesn't build the compute runtime with level zero). So it should be clarified that you need intel-level-zero-gpu and intel-compute-runtime is just a common way to get it.

So I think the wording on the Linux side should be changed. I feel like it should say:
Requires Intel GPU with Xe-HPG architecture and intel-level-zero-gpu XX.XX.25812 or newer, typically available through the intel-compute-runtime package XX.XX.25812 or newer

But you may want to wait for review from Brecht on this.

Please correct me if I got anything wrong.

The Windows side looks fine to me.

I just wanted to bring up some points on the Linux side of things. From my understanding on Linux we **need** `intel-level-zero-gpu` for oneAPI to work properly. And for many Linux distrobutions, the `intel-level-zero-gpu` isn't a stand alone package, but instead bundled with the `intel-compute-runtime` package. Hence why this Pull Request lists `intel-level-zero-gpu or intel-compute-runtime` as the requirements. But this isn't true is it? We don't need `intel-level-zero-gpu **OR** intel-compute-runtime`, we need `intel-level-zero-gpu` and `intel-compute-runtime` is the most common way of obtaining this package on many distributions. But having `intel-compute-runtime` installed doesn't guarantee that you'll have `intel-level-zero-gpu` (E.G. Your package maintainer doesn't build the compute runtime with level zero). So it should be clarified that you need `intel-level-zero-gpu` and `intel-compute-runtime` is just a common way to get it. So I think the wording on the Linux side should be changed. I feel like it should say: `Requires Intel GPU with Xe-HPG architecture and intel-level-zero-gpu XX.XX.25812 or newer, typically available through the intel-compute-runtime package XX.XX.25812 or newer` But you may want to wait for review from Brecht on this. Please correct me if I got anything wrong. --- The Windows side looks fine to me.

Xavier Hallade commented

2023-07-03 14:30:18 +02:00

having intel-compute-runtime installed doesn't guarantee that you'll have intel-level-zero-gpu

I wouldn't say that's true from an end-user perspective. It does guarantee it.*
intel-compute-runtime is the common source that provides the runtime libraries.
If a Linux distribution has intel-compute-runtime, it's expected that it brings everything from it, so OpenCL and Level-Zero runtimes.
If it doesn't have it, then the libraries split across OpenCL and Level-Zero runtime specific packages.
So from a user perspective, you can either find one or the other, not both separately. Unless compute-runtime is a virtual package that includes the split ones, and then it doesn't matter to pick one or the other or both.

*There is still one possible edge case if a maintainer chooses to package the whole compute-runtime but with the Level-Zero part disabled, but then, again there wouldn't be a separate intel-level-zero-gpu package available. I suppose the correct course of action is for the user to open a bug report and it gets fixed at the distribution level - there wouldn't be room in the UI to explain the requirement down to that level of details.

> having intel-compute-runtime installed doesn't guarantee that you'll have intel-level-zero-gpu I wouldn't say that's true from an end-user perspective. It does guarantee it.* intel-compute-runtime is the common source that provides the runtime libraries. If a Linux distribution has intel-compute-runtime, it's expected that it brings everything from it, so OpenCL and Level-Zero runtimes. If it doesn't have it, then the libraries split across OpenCL and Level-Zero runtime specific packages. So from a user perspective, you can either find one or the other, not both separately. Unless compute-runtime is a virtual package that includes the split ones, and then it doesn't matter to pick one or the other or both. *There is still one possible edge case if a maintainer chooses to package the whole compute-runtime but with the Level-Zero part disabled, but then, again there wouldn't be a separate intel-level-zero-gpu package available. I suppose the correct course of action is for the user to open a bug report and it gets fixed at the distribution level - there wouldn't be room in the UI to explain the requirement down to that level of details.

👍 1

Brecht Van Lommel approved these changes 2023-07-05 12:13:06 +02:00

Xavier Hallade referenced this issue from a commit

2023-07-05 12:16:09 +02:00

Cycles: improve oneAPI requirements text in the UI

Xavier Hallade merged commit d55cdb1b7a into main

2023-07-05 12:16:10 +02:00

Xavier Hallade deleted branch oneapi_reqs_ui

2023-07-05 12:16:11 +02:00

Christoph Lendenfeld referenced this issue from a commit

2023-07-06 10:15:00 +02:00

Cycles: improve oneAPI requirements text in the UI