diff options
author | Chris Wilson <[email protected]> | 2016-10-28 13:58:27 +0100 |
---|---|---|
committer | Chris Wilson <[email protected]> | 2016-10-28 20:53:43 +0100 |
commit | e95433c73a11759203af1cae5958f998c9673370 (patch) | |
tree | 021dc483a7beff3d2924089cf1c6d20105f11b8a /tools/perf/scripts/python/net_dropmonitor.py | |
parent | c92ac094a9c647ebcff56c0535f865bc7f2aa052 (diff) |
drm/i915: Rearrange i915_wait_request() accounting with callers
Our low-level wait routine has evolved from our generic wait interface
that handled unlocked, RPS boosting, waits with time tracking. If we
push our GEM fence tracking to use reservation_objects (required for
handling multiple timelines), we lose the ability to pass the required
information down to i915_wait_request(). However, if we push the extra
functionality from i915_wait_request() to the individual callsites
(i915_gem_object_wait_rendering and i915_gem_wait_ioctl) that make use
of those extras, we can both simplify our low level wait and prepare for
extending the GEM interface for use of reservation_objects.
v2: Rewrite i915_wait_request() kerneldocs
Signed-off-by: Chris Wilson <[email protected]>
Cc: Matthew Auld <[email protected]>
Reviewed-by: Joonas Lahtinen <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions