aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
diff options
context:
space:
mode:
authorDaniel Vetter <[email protected]>2020-07-09 14:33:38 +0200
committerDaniel Vetter <[email protected]>2020-07-21 09:42:19 +0200
commit72b6ede7362327c0cff8e159fbb8c8fd9611e26e (patch)
tree2b627a77868a92ac6d8e6770a7763f1e85ee3536 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
parentd0b9a9aef0a18e7ba473d0887e7ebd107ab84fe4 (diff)
dma-buf.rst: Document why indefinite fences are a bad idea
Comes up every few years, gets somewhat tedious to discuss, let's write this down once and for all. What I'm not sure about is whether the text should be more explicit in flat out mandating the amdkfd eviction fences for long running compute workloads or workloads where userspace fencing is allowed. v2: Now with dot graph! v3: Typo (Dave Airlie) Reviewed-by: Thomas Hellstrom <[email protected]> Acked-by: Jason Ekstrand <[email protected]> Acked-by: Christian König <[email protected]> Acked-by: Daniel Stone <[email protected]> Acked-by: Dave Airlie <[email protected]> Reviewed-by: Maarten Lankhorst <[email protected]> Cc: Jesse Natalie <[email protected]> Cc: Steve Pronovost <[email protected]> Cc: Jason Ekstrand <[email protected]> Cc: Felix Kuehling <[email protected]> Cc: Mika Kuoppala <[email protected]> Cc: Thomas Hellstrom <[email protected]> Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: [email protected] Cc: Chris Wilson <[email protected]> Cc: Maarten Lankhorst <[email protected]> Cc: Christian König <[email protected]> Signed-off-by: Daniel Vetter <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions