summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/selftests/i915_request.c
diff options
context:
space:
mode:
authorChris Wilson2019-04-24 22:07:15 +0200
committerChris Wilson2019-04-24 23:25:32 +0200
commit6eee33e87f6d1f6263162ce0874c1ef503eff041 (patch)
tree6df409ca2539ebdcac21e0d62bf661030f4ea798 /drivers/gpu/drm/i915/selftests/i915_request.c
parentdrm/i915: Pull the GEM powermangement coupling into its own file (diff)
downloadkernel-qcow2-linux-6eee33e87f6d1f6263162ce0874c1ef503eff041.tar.gz
kernel-qcow2-linux-6eee33e87f6d1f6263162ce0874c1ef503eff041.tar.xz
kernel-qcow2-linux-6eee33e87f6d1f6263162ce0874c1ef503eff041.zip
drm/i915: Introduce context->enter() and context->exit()
We wish to start segregating the power management into different control domains, both with respect to the hardware and the user interface. The first step is that at the lowest level flow of requests, we want to process a context event (and not a global GEM operation). In this patch, we introduce the context callbacks that in future patches will be redirected to per-engine interfaces leading to global operations as required. The intent is that this will be guarded by the timeline->mutex, except that retiring has not quite finished transitioning over from being guarded by struct_mutex. So at the moment it is protected by struct_mutex with a reminded to switch. v2: Rename default handlers to intel_context_enter_engine. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190424200717.1686-3-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/selftests/i915_request.c')
0 files changed, 0 insertions, 0 deletions