kernel/drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c, branch linux-4.17.y

drm/etnaviv: replace hangcheck with scheduler timeout

2018-02-12T15:31:01Z

This replaces the etnaviv internal hangcheck logic with the job timeout handling provided by the DRM scheduler. This simplifies the driver further and allows to replay jobs after a GPU reset, so only minimal state is lost. This introduces a user-visible change in that we don't allow jobs to run indefinitely as long as they make progress anymore, as this introduces quality of service issues when multiple processes are using the GPU. Userspace is now responsible to flush jobs in a way that the finish in a reasonable time, where reasonable is currently defined as less than 500ms. Signed-off-by: Lucas Stach

drm/etnaviv: lock BOs after all other submit work is done

2018-02-12T15:31:00Z

Populating objects, adding them to the GPU VM and patching/validating the command stream might take a lot of CPU time. There is no reason to hold all object reservations during that time. Signed-off-by: Lucas Stach

drm/etnaviv: move dependency handling to scheduler

2018-02-12T15:31:00Z

Move the fence dependency handling to the scheduler where it belongs. Jobs with unsignaled dependencies just get to sit in the scheduler queue without holding any locks. Signed-off-by: Lucas Stach

drm/etnaviv: hook up DRM GPU scheduler

2018-02-12T15:30:59Z

This hooks in the DRM GPU scheduler. No improvement yet, as all the dependency handling is still done in etnaviv_gem_submit. This just replaces the actual GPU submit by passing through the scheduler. Allows to get rid of the retire worker, as this is now driven by the scheduler. Signed-off-by: Lucas Stach

drm/etnaviv: track fences by IDR instead of seqno

2018-02-12T15:30:58Z

This moves away from using the internal seqno as the userspace fence reference. By moving to a generic ID, we can later replace the internal fence by something different than the etnaviv seqno fence. Signed-off-by: Lucas Stach Reviewed-by: Philipp Zabel

drm/etnaviv: couple runtime PM management to submit object lifetime

2018-01-02T16:34:59Z

As long as there is an active submit, we want the GPU to stay awake. This is slightly complicated by the fact that we really want to wake the GPU at the last possible moment to achieve maximum power savings. Signed-off-by: Lucas Stach

drm/etnaviv: move GPU active handling to bo pin/unpin

2018-01-02T16:34:10Z

The active count is used to check if the BO is idle, where idle is defined as not active on the GPU and all VM mappings and reference counts dropped to the initial state. As the idling of the mappings and references now only happens in the submit cleanup, the active state handling must be moved to the same location in order to keep the userspace semantics. Signed-off-by: Lucas Stach

drm/etnaviv: move cmdbuf into submit object

2018-01-02T16:33:36Z

Less dynamic allocations and slims down the cmdbuf object to only the required information, as everything else is already available in the submit object. This also simplifies buffer and mappings lifetime management, as they are now exlusively attached to the submit object and not additionally to the cmdbuf. Signed-off-by: Lucas Stach

drm/etnaviv: move exec_state to submit object

2018-01-02T16:32:40Z

We'll need this in some places where only the submit is available. Also this is a first step at slimming down the cmdbuf object. Signed-off-by: Lucas Stach

drm/etnaviv: move PMRs to submit object

2018-01-02T16:31:59Z

To make them available to the event worker even after the actual command stream execution has finished. Signed-off-by: Lucas Stach