drm/i915/selftests: Drop stale timeline constructor assert
authorChris Wilson <chris@chris-wilson.co.uk>
Fri, 31 Jul 2020 10:22:06 +0000 (11:22 +0100)
committerJoonas Lahtinen <joonas.lahtinen@linux.intel.com>
Mon, 7 Sep 2020 10:17:13 +0000 (13:17 +0300)
Since we pass around encoded parameters to the kernel context
constructor using the ce->timeline pointer, we can no longer assert that
it should be zero for mock timeline construction.

Fixes: d1bf5dd8f6d5 ("drm/i915/gt: Support multiple pinned timelines")
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200731102206.6793-1-chris@chris-wilson.co.uk
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
[Joonas: Updated Fixes: link after rebasing and reordering into drm-intel-gt-next branch]
Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
drivers/gpu/drm/i915/gt/mock_engine.c

index d5beb116261f02dc8b06bd4ea9b40e2e0210003d..027de53cd05b88f3b990053ac6c88717fb7b4e56 100644 (file)
@@ -152,7 +152,6 @@ static int mock_context_alloc(struct intel_context *ce)
        if (!ce->ring)
                return -ENOMEM;
 
-       GEM_BUG_ON(ce->timeline);
        ce->timeline = intel_timeline_create(ce->engine->gt);
        if (IS_ERR(ce->timeline)) {
                kfree(ce->engine);