diff options
| author | Chris Wilson <[email protected]> | 2016-01-15 16:51:46 +0000 |
|---|---|---|
| committer | Tvrtko Ursulin <[email protected]> | 2016-01-21 11:00:35 +0000 |
| commit | 426960bed3217f72a1b7bb94f084d79cc616ec0f (patch) | |
| tree | f26fb2afc54529609c28397c43fdc1207fb33907 /drivers/gpu/drm/amd/amdgpu/amdgpu_test.c | |
| parent | drm/i915: Decouple execbuf uAPI from internal implementation (diff) | |
| download | kernel-426960bed3217f72a1b7bb94f084d79cc616ec0f.tar.gz kernel-426960bed3217f72a1b7bb94f084d79cc616ec0f.zip | |
drm/i915: Seal busy-ioctl uABI and prevent leaking of internal ids
Tvrtko was looking through the execbuffer-ioctl and noticed that the
uABI was tightly coupled to our internal engine identifiers. Close
inspection also revealed that we leak those internal engine identifiers
through the busy-ioctl, and those internal identifiers already do not
match the user identifiers. Fortuitiously, there is only one user of the
set of busy rings from the busy-ioctl, and they only wish to choose
between the RENDER and the BLT engines.
Let's fix the userspace ABI while we still can.
v2: Update the uAPI documentation to explain the identifiers.
Signed-off-by: Chris Wilson <[email protected]>
Testcase: igt/gem_busy
Cc: Tvrtko Ursulin <[email protected]>
Cc: Daniel Vetter <[email protected]>
Reviewed-by: Tvrtko Ursulin <[email protected]>
Acked-by: Daniel Vetter <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_test.c')
0 files changed, 0 insertions, 0 deletions