summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/Kconfig.debug
diff options
context:
space:
mode:
authorTvrtko Ursulin <tvrtko.ursulin@intel.com>2017-02-21 12:01:42 +0100
committerTvrtko Ursulin <tvrtko.ursulin@intel.com>2017-02-21 14:18:14 +0100
commit354d036fcf70654cff2e2cbdda54a835d219b9d2 (patch)
tree1fe5b60f3d9efbc26496624ed603642eddc6f5ef /drivers/gpu/drm/i915/Kconfig.debug
parentdrm/i915/tracepoints: Remove unused i915_gem_request_complete (diff)
downloadlinux-354d036fcf70654cff2e2cbdda54a835d219b9d2.tar.xz
linux-354d036fcf70654cff2e2cbdda54a835d219b9d2.zip
drm/i915/tracepoints: Add request submit and execute tracepoints
These new tracepoints are emitted once the request is ready to be submitted to the GPU and once the request is about to be submitted to the GPU, respectively. Former condition triggers as soon as all the fences and dependencies have been resolved, and the latter once the backend is about to submit it to the GPU. New tracepoint are enabled via the new DRM_I915_LOW_LEVEL_TRACEPOINTS Kconfig option which is disabled by default to alleviate the performance impact concerns. v2: Move execute tracepoint to __i915_gem_request_submit. (Chris Wilson) Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Diffstat (limited to 'drivers/gpu/drm/i915/Kconfig.debug')
-rw-r--r--drivers/gpu/drm/i915/Kconfig.debug11
1 files changed, 11 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/Kconfig.debug b/drivers/gpu/drm/i915/Kconfig.debug
index 68ff072f8b76..e091809a9a9e 100644
--- a/drivers/gpu/drm/i915/Kconfig.debug
+++ b/drivers/gpu/drm/i915/Kconfig.debug
@@ -76,3 +76,14 @@ config DRM_I915_SELFTEST
Recommended for driver developers only.
If in doubt, say "N".
+
+config DRM_I915_LOW_LEVEL_TRACEPOINTS
+ bool "Enable low level request tracing events"
+ depends on DRM_I915
+ default n
+ help
+ Choose this option to turn on low level request tracing events.
+ This provides the ability to precisely monitor engine utilisation
+ and also analyze the request dependency resolving timeline.
+
+ If in doubt, say "N".