[PATCH 04/34] drm: Add some kselftests for the DRM range manager (struct drm_mm)

2016-12-13 Thread Joonas Lahtinen
On ti, 2016-12-13 at 10:21 +, Chris Wilson wrote: > On Tue, Dec 13, 2016 at 11:58:54AM +0200, Joonas Lahtinen wrote: > > > > This could be build time, depending on the intended use. > > I was thinking module param for the seed, just in case we want different > patterns. As discussed in IRC, g

[PATCH 04/34] drm: Add some kselftests for the DRM range manager (struct drm_mm)

2016-12-13 Thread Joonas Lahtinen
On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > First we introduce a smattering of infrastructure for writing selftests. > The idea is that we have a test module that exercises a particular > portion of the exported API, and that module provides a set of tests > that can either be run as an

[PATCH 04/34] drm: Add some kselftests for the DRM range manager (struct drm_mm)

2016-12-13 Thread Chris Wilson
On Tue, Dec 13, 2016 at 11:58:54AM +0200, Joonas Lahtinen wrote: > On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > > +++ b/drivers/gpu/drm/selftests/test-drm_mm.c > > @@ -0,0 +1,47 @@ > > +/* > > + * Test cases for the drm_mm range manager > > + */ > > + > > +#define pr_fmt(fmt) "drm_mm: "

[PATCH 04/34] drm: Add some kselftests for the DRM range manager (struct drm_mm)

2016-12-12 Thread Chris Wilson
First we introduce a smattering of infrastructure for writing selftests. The idea is that we have a test module that exercises a particular portion of the exported API, and that module provides a set of tests that can either be run as an ensemble via kselftest or individually via an igt harness (in