summaryrefslogtreecommitdiffstats
path: root/fs/tracefs
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2019-01-29 19:54:50 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2019-01-29 20:59:59 +0100
commit8547444137ec6138ce52fc1938980b737a0d4d9e (patch)
treec5c09d1d025754f73b11a95ccd3a7922ff62f388 /fs/tracefs
parentdrm/i915/selftests: Apply a subtest filter (diff)
downloadlinux-8547444137ec6138ce52fc1938980b737a0d4d9e.tar.xz
linux-8547444137ec6138ce52fc1938980b737a0d4d9e.zip
drm/i915: Identify active requests
To allow requests to forgo a common execution timeline, one question we need to be able to answer is "is this request running?". To track whether a request has started on HW, we can emit a breadcrumb at the beginning of the request and check its timeline's HWSP to see if the breadcrumb has advanced past the start of this request. (This is in contrast to the global timeline where we need only ask if we are on the global timeline and if the timeline has advanced past the end of the previous request.) There is still confusion from a preempted request, which has already started but relinquished the HW to a high priority request. For the common case, this discrepancy should be negligible. However, for identification of hung requests, knowing which one was running at the time of the hang will be much more important. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190129185452.20989-2-chris@chris-wilson.co.uk
Diffstat (limited to 'fs/tracefs')
0 files changed, 0 insertions, 0 deletions