[Intel-gfx] [PATCH] drm/i915: Prefer to report ENOMEM rather than incur the oom for gfx allocations

[Joonas Lahtinen]

On ke, 2017-03-22 at 11:05 +0000, Chris Wilson wrote:
> Since gfx allocations tend to be large, unmovable and disposable, report
> the allocation failure back to userspace as an ENOMEM rather than incur
> the oomkiller. We have already tried to make room by purging our own
> cached gfx objects, and the oomkiller doesn't attribute ownership of gfx
> objects so will likely pick the wrong candidate. Instead, let userspace
> see the ENOMEM.
> 
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

A-b from Daniel.

Reviewed-by: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation