Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
drivers/gpu/drm/i915/intel_pm.c between commit 6bc55a67bd4b (drm/i915:
drop WaSetupGtModeTdRowDispatch:snb) from the drm-intel-fixes tree and
commits (not sure which ones - the code seems to have been rearranged
quite a bit) from
On Thursday 13 November 2014 03:57 PM, Thomas Daniel wrote:
No longer create a work item to clean each execlist queue item.
Instead, move retired execlist requests to a queue and clean up the
items during retire_requests.
v2: Fix legacy ring path broken during overzealous cleanup
v3: Update
On Thursday 13 November 2014 03:58 PM, Thomas Daniel wrote:
Same as with the context, pinning to GGTT regardless is harmful (it
badly fragments the GGTT and can even exhaust it).
Unfortunately, this case is also more complex than the previous one
because we need to map and access the
On Tuesday 18 November 2014 12:07 PM, Deepak S wrote:
On Thursday 13 November 2014 03:58 PM, Thomas Daniel wrote:
Same as with the context, pinning to GGTT regardless is harmful (it
badly fragments the GGTT and can even exhaust it).
Unfortunately, this case is also more complex than the
On Thursday 13 November 2014 03:58 PM, Thomas Daniel wrote:
From: Oscar Mateo oscar.ma...@intel.com
Up until now, we have pinned every logical ring context backing object
during creation, and left it pinned until destruction. This made my life
easier, but it's a harmful thing to do, because we
