Re: [Intel-gfx] [PATCH] drm/i915/selftests: Report ENOMEM clearly for an allocation failure

On 17 November 2017 at 15:31, Chris Wilson wrote: > If we can not run the drunk_hole test because we couldn't allocate the > memory for the permutation array (even after we tried trimming the > size), report a clear ENOMEM. Similary, if we are asked to operate on a >

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Report ENOMEM clearly for an allocation failure

On 17 November 2017 at 15:31, Chris Wilson wrote: > If we can not run the drunk_hole test because we couldn't allocate the > memory for the permutation array (even after we tried trimming the > size), report a clear ENOMEM. Similary, if we are asked to operate on a >

[Intel-gfx] [PATCH] drm/i915/selftests: Report ENOMEM clearly for an allocation failure

If we can not run the drunk_hole test because we couldn't allocate the memory for the permutation array (even after we tried trimming the size), report a clear ENOMEM. Similary, if we are asked to operate on a hole too small for ourselves, make it skip quietly. v2: Avoid malloc(0) since that

Re: [Intel-gfx] [PATCH] drm/i915/selftests: Report ENOMEM clearly for an allocation failure

On 17 November 2017 at 10:17, Chris Wilson wrote: > If we can not run the drunk_hole test because we couldn't allocate the > memory for the permutation array (even after we tried trimming the > size), report a clear ENOMEM. Similary, if we are asked to operate on a >

[Intel-gfx] [PATCH] drm/i915/selftests: Report ENOMEM clearly for an allocation failure

If we can not run the drunk_hole test because we couldn't allocate the memory for the permutation array (even after we tried trimming the size), report a clear ENOMEM. Similary, if we are asked to operate on a hole too small for ourselves, make it skip quietly. Signed-off-by: Chris Wilson