Summary: | [bsw] i915_gem_context_free WARN_ON(!list_empty(&ppgtt->base.active_list)) | ||
---|---|---|---|
Product: | DRI | Reporter: | Chris Wilson <chris> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | BSW/CHT | i915 features: | GEM/Other |
Description
Chris Wilson
2015-10-23 13:18:03 UTC
The WARN is indeed invalid in the current codebase. For the record, proposed fix, although with a bit of disagreement on what is logical: http://patchwork.freedesktop.org/patch/62884/ commit b0decaf75bd902a11c932005c88924947ac00b8c Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Aug 4 07:52:44 2016 +0100 drm/i915: Track active vma requests Hook the vma itself into the i915_gem_request_retire() so that we can accurately track when a solitary vma is inactive (as opposed to having to wait for the entire object to be idle). This improves the interaction when using multiple contexts (with full-ppgtt) and eliminates some frequent list walking when retiring objects after a completed request. A side-effect is that we get an active vma reference for free. The consequence of this is shown in the next patch... |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.