KhronosGroup / KhronosGroup/EGL-Registry
`QueryDmaBufModifiersEXT` does not guarantee obtained modifiers are actually usable
- Dominant language
- HTML
- Stars
- 151
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
`QueryDmaBufModifiersEXT` lets me query which modifiers are supported for a given format, but the information I provide to this API (i.e. format) is not sufficient to determine whether a modifier will actually work. For example, at allocation time, mesa AMDGPU will also check if the size of the buffer is within supported range (see: https://gitlab.freedesktop.org/mesa/mesa/-/blob/2487a875527f636565a7b39036690fbf7c5d46db/src/gallium/drivers/radeonsi/si_texture.c#L1564), and will fail if I try to allocate a texture that's too large.
Can `QueryDmaBufModifiersEXT` be extended to incorporate size info into the query as well? This will make it "complete" w.r.t, e.g. `gbm_bo_create_with_modifiers`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the QueryDmaBufModifiersEXT and gbm_bo_create_with_modifiers entry points named in the issue, and review the linked Mesa AMDGPU allocation check. Done means deciding whether and how size information should be incorporated so queried modifiers reflect allocation usability.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100