Repository navigation
run: Add /dev/kfd to dri device permission - #6648
Conversation
3866d6b to
af178e8
Compare
|
We didn't add anything to the docs for the nvidia compute things either. Maybe we should make this very generic and just say "GPU graphics and compute (including DRI render devices, vendor specific render devices, and vendor specific compute devices)" |
|
Who's the target audience for this doc? If it's app devs, they likely won't know what |
|
I mean, one issue is that new drivers emerge, old ones get unimportant, so this has to change over time anyway. If you really need to know the exhaustive list, you can find it in the code or just inspect the sandbox. |
af178e8 to
b17efd9
Compare
|
Adopted your wording and added the tags into it. |
| Support for <filename>/dev/kfd</filename> was | ||
| added in 1.17.8. |
There was a problem hiding this comment.
I think the intention was to drop this line so that we don't have to keep updating the doc as things are added.
There was a problem hiding this comment.
So no documentation, which version added an extension?
There was a problem hiding this comment.
They are all optional anyway, so clients must handle them not being available, so the version does not add any value.
/dev/kfd is used for AMD ROCm/OpenCL compute. Add it to the dri device list so apps can request GPU compute access without needing --device=all. Fixes: flatpak#5383
b17efd9 to
da4e6e2
Compare
3 participants
/dev/kfd is used for AMD ROCm/OpenCL compute. Add it to the dri device list so apps can request GPU compute access without needing --device=all.
Fixes: #5383
A bit unsure about the wording in docs