Re: [Intel-gfx] [PATCH 16/16] drm/i915: Add selftests for object allocation, phys

2016-12-17 Thread Chris Wilson
On Tue, Dec 13, 2016 at 05:10:46PM +, Tvrtko Ursulin wrote: > >+int i915_gem_object_selftests(void) > >+{ > >+static const struct i915_subtest tests[] = { > >+SUBTEST(igt_gem_object), > >+SUBTEST(igt_phys_object), > >+}; > >+ > >+return i915_subtests(tests, N

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [v3,01/38] drm/i915: Use the MRU stack search after evicting (rev4)

2016-12-17 Thread Patchwork
== Series Details == Series: series starting with [v3,01/38] drm/i915: Use the MRU stack search after evicting (rev4) URL : https://patchwork.freedesktop.org/series/16934/ State : warning == Summary == Series 16934v4 Series without cover letter https://patchwork.freedesktop.org/api/1.0/series

[Intel-gfx] [PATCH] lib: Add a simple prime number generator

2016-12-17 Thread Chris Wilson
Prime numbers are interesting for testing components that use multiplies and divides, such as testing DRM's struct drm_mm alignment computations. v2: Move to lib/, add selftest v3: Fix initial constants (exclude 0/1 from being primes) v4: More RCU markup to keep 0day/sparse happy v5: Fix RCU unwin

Re: [Intel-gfx] [PATCH i-g-t] igt_kms: Use const parameters for igt_assert_crc_equal

2016-12-17 Thread Robert Foss
Looks good to me. Added t-b and pushed upstream. Rob. On 2016-12-16 03:35 PM, Lyude wrote: Since we're not modifying these anywhere, let's make them const so as to not break code doing comparisons against compile-time CRCs. Signed-off-by: Lyude _

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v3,01/38] drm/i915: Use the MRU stack search after evicting (rev3)

2016-12-17 Thread Patchwork
== Series Details == Series: series starting with [v3,01/38] drm/i915: Use the MRU stack search after evicting (rev3) URL : https://patchwork.freedesktop.org/series/16934/ State : success == Summary == Series 16934v3 Series without cover letter https://patchwork.freedesktop.org/api/1.0/series

[Intel-gfx] [PATCH] drm: kselftest for drm_mm and top-down allocation

2016-12-17 Thread Chris Wilson
Check that if we request top-down allocation from drm_mm_insert_node() we receive the next available hole from the top. v2: Flip sign on conditional assert. Signed-off-by: Chris Wilson Reviewed-by: Joonas Lahtinen --- drivers/gpu/drm/selftests/drm_mm_selftests.h | 1 + drivers/gpu/drm/selfte

[Intel-gfx] [PATCH] drm: kselftest for drm_mm_insert_node_in_range()

2016-12-17 Thread Chris Wilson
Exercise drm_mm_insert_node_in_range(), check that we only allocate from the specified range. v2: Use all allocation flags v3: Don't pass in invalid ranges - these will be asserted later. Signed-off-by: Chris Wilson Reviewed-by: Joonas Lahtinen --- drivers/gpu/drm/selftests/drm_mm_selftests.h