diff options
author | Chris Wilson <chris@chris-wilson.co.uk> | 2019-04-24 21:07:17 +0100 |
---|---|---|
committer | Chris Wilson <chris@chris-wilson.co.uk> | 2019-04-24 22:26:49 +0100 |
commit | 79ffac8599c4d8aa84d313920d3d86d7361c252b (patch) | |
tree | 3352bc82c4d7bb7cd9caaf42fda9ee97e0e88bde /drivers/gpu/drm/i915/intel_uc.c | |
parent | 2ccdf6a1c3f7ff51d721ee7a5bed96e03da77205 (diff) | |
download | linux-stable-79ffac8599c4d8aa84d313920d3d86d7361c252b.tar.gz linux-stable-79ffac8599c4d8aa84d313920d3d86d7361c252b.tar.bz2 linux-stable-79ffac8599c4d8aa84d313920d3d86d7361c252b.zip |
drm/i915: Invert the GEM wakeref hierarchy
In the current scheme, on submitting a request we take a single global
GEM wakeref, which trickles down to wake up all GT power domains. This
is undesirable as we would like to be able to localise our power
management to the available power domains and to remove the global GEM
operations from the heart of the driver. (The intent there is to push
global GEM decisions to the boundary as used by the GEM user interface.)
Now during request construction, each request is responsible via its
logical context to acquire a wakeref on each power domain it intends to
utilize. Currently, each request takes a wakeref on the engine(s) and
the engines themselves take a chipset wakeref. This gives us a
transition on each engine which we can extend if we want to insert more
powermangement control (such as soft rc6). The global GEM operations
that currently require a struct_mutex are reduced to listening to pm
events from the chipset GT wakeref. As we reduce the struct_mutex
requirement, these listeners should evaporate.
Perhaps the biggest immediate change is that this removes the
struct_mutex requirement around GT power management, allowing us greater
flexibility in request construction. Another important knock-on effect,
is that by tracking engine usage, we can insert a switch back to the
kernel context on that engine immediately, avoiding any extra delay or
inserting global synchronisation barriers. This makes tracking when an
engine and its associated contexts are idle much easier -- important for
when we forgo our assumed execution ordering and need idle barriers to
unpin used contexts. In the process, it means we remove a large chunk of
code whose only purpose was to switch back to the kernel context.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Cc: Imre Deak <imre.deak@intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20190424200717.1686-5-chris@chris-wilson.co.uk
Diffstat (limited to 'drivers/gpu/drm/i915/intel_uc.c')
-rw-r--r-- | drivers/gpu/drm/i915/intel_uc.c | 22 |
1 files changed, 9 insertions, 13 deletions
diff --git a/drivers/gpu/drm/i915/intel_uc.c b/drivers/gpu/drm/i915/intel_uc.c index 30a8e376d19f..01ea36e3150c 100644 --- a/drivers/gpu/drm/i915/intel_uc.c +++ b/drivers/gpu/drm/i915/intel_uc.c @@ -481,26 +481,22 @@ void intel_uc_reset_prepare(struct drm_i915_private *i915) intel_uc_sanitize(i915); } -int intel_uc_suspend(struct drm_i915_private *i915) +void intel_uc_suspend(struct drm_i915_private *i915) { struct intel_guc *guc = &i915->guc; + intel_wakeref_t wakeref; int err; - if (!USES_GUC(i915)) - return 0; - if (guc->fw.load_status != INTEL_UC_FIRMWARE_SUCCESS) - return 0; - - err = intel_guc_suspend(guc); - if (err) { - DRM_DEBUG_DRIVER("Failed to suspend GuC, err=%d", err); - return err; - } + return; - guc_disable_communication(guc); + with_intel_runtime_pm(i915, wakeref) { + err = intel_guc_suspend(guc); + if (err) + DRM_DEBUG_DRIVER("Failed to suspend GuC, err=%d", err); - return 0; + guc_disable_communication(guc); + } } int intel_uc_resume(struct drm_i915_private *i915) |