On Thu, Feb 02, 2017 at 11:48:21AM +0100, Daniel Vetter wrote:
On Thu, Feb 02, 2017 at 10:47:11AM +0100, Juergen Gross wrote:
Commit 920cf4194954ec ("drm/i915: Introduce an internal allocator for disposable private objects") introduced a regression for the kernel running as Xen dom0: when switching to graphics mode a GPU HANG occurred.
Reason seems to be a missing adaption similar to that done in commit 7453c549f5f648 ("swiotlb: Export swiotlb_max_segment to users") to i915_gem_object_get_pages_internal().
So limit the maximum page order to be used according to the maximum swiotlb segment size instead to the complete swiotlb size.
Signed-off-by: Juergen Gross jgross@suse.com
Fixes: 920cf4194954 ("drm/i915: Introduce an internal allocator for disposable private objects") Cc: Chris Wilson chris@chris-wilson.co.uk Cc: Tvrtko Ursulin tvrtko.ursulin@linux.intel.com Cc: Daniel Vetter daniel.vetter@intel.com Cc: Jani Nikula jani.nikula@linux.intel.com Cc: intel-gfx@lists.freedesktop.org Cc: drm-intel-fixes@lists.freedesktop.org # v4.10-rc1+
We have a nice script for these :-)
Pffifle. 7453c549f5f648 allowed Xen to change it and silently conflicted with those that already used the previous limits, which didn't land in our tree until v4.10-rc3. -Chris