From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>, stable@vger.kernel.org
Subject: Re: [PATCH 1/9] drm/i915: Make user contexts bannable again!
Date: Mon, 18 Feb 2019 12:45:32 +0200 [thread overview]
Message-ID: <87y36dxtmb.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190217161159.815-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Since moving the bannable boolean into the context flags, we lost the
> default setting of contexts being bannable. Oops.
>
> Sadly because we have multi-level banning scheme, our testcase for being
> banned cannot distinguish between the expected ban on the context and
> the applied banned via the fd.
>
> Fixes: 6095868a271d ("drm/i915: Complete kerneldoc for struct i915_gem_context")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: <stable@vger.kernel.org> # v4.11+
> ---
> drivers/gpu/drm/i915/i915_gem_context.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 280813a4bf82..102866967998 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -364,6 +364,7 @@ __create_hw_context(struct drm_i915_private *dev_priv,
> list_add_tail(&ctx->link, &dev_priv->contexts.list);
> ctx->i915 = dev_priv;
> ctx->sched.priority = I915_USER_PRIORITY(I915_PRIORITY_NORMAL);
> + ctx->user_flags = BIT(UCONTEXT_BANNABLE);
>
But it is there, after setting the ring size.
-Mika
> for (n = 0; n < ARRAY_SIZE(ctx->__engine); n++)
> intel_context_init(&ctx->__engine[n], ctx, dev_priv->engine[n]);
> --
> 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>, stable@vger.kernel.org
Subject: Re: [PATCH 1/9] drm/i915: Make user contexts bannable again!
Date: Mon, 18 Feb 2019 12:45:32 +0200 [thread overview]
Message-ID: <87y36dxtmb.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190217161159.815-1-chris@chris-wilson.co.uk>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Since moving the bannable boolean into the context flags, we lost the
> default setting of contexts being bannable. Oops.
>
> Sadly because we have multi-level banning scheme, our testcase for being
> banned cannot distinguish between the expected ban on the context and
> the applied banned via the fd.
>
> Fixes: 6095868a271d ("drm/i915: Complete kerneldoc for struct i915_gem_context")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Cc: <stable@vger.kernel.org> # v4.11+
> ---
> drivers/gpu/drm/i915/i915_gem_context.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c
> index 280813a4bf82..102866967998 100644
> --- a/drivers/gpu/drm/i915/i915_gem_context.c
> +++ b/drivers/gpu/drm/i915/i915_gem_context.c
> @@ -364,6 +364,7 @@ __create_hw_context(struct drm_i915_private *dev_priv,
> list_add_tail(&ctx->link, &dev_priv->contexts.list);
> ctx->i915 = dev_priv;
> ctx->sched.priority = I915_USER_PRIORITY(I915_PRIORITY_NORMAL);
> + ctx->user_flags = BIT(UCONTEXT_BANNABLE);
>
But it is there, after setting the ring size.
-Mika
> for (n = 0; n < ARRAY_SIZE(ctx->__engine); n++)
> intel_context_init(&ctx->__engine[n], ctx, dev_priv->engine[n]);
> --
> 2.20.1
next prev parent reply other threads:[~2019-02-18 10:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 16:11 [PATCH 1/9] drm/i915: Make user contexts bannable again! Chris Wilson
2019-02-17 16:11 ` [PATCH 2/9] drm/i915: Prevent user context creation while wedged Chris Wilson
2019-02-17 16:11 ` [PATCH 3/9] drm/i915: Optionally disable automatic recovery after a GPU reset Chris Wilson
2019-02-17 17:05 ` [PATCH] " Chris Wilson
2019-02-17 16:11 ` [PATCH 4/9] drm/i915/selftests: Move local mock_ggtt allocations to the heap Chris Wilson
2019-02-17 18:40 ` Matthew Auld
2019-02-17 20:22 ` Chris Wilson
2019-02-17 16:11 ` [PATCH 5/9] drm/i915: Move verify_wm_state() to heap Chris Wilson
2019-02-17 16:11 ` [PATCH 6/9] drm/i915: Avoid reset lock in writing fence registers Chris Wilson
2019-02-17 16:11 ` [PATCH 7/9] drm/i915: Reorder struct_mutex-vs-reset_lock in i915_gem_fault() Chris Wilson
2019-02-17 16:11 ` [PATCH 8/9] drm/i915: Trim i915_do_reset() to minimum delays Chris Wilson
2019-02-17 16:11 ` [PATCH 9/9] drm/i915: Trim delays for wedging Chris Wilson
2019-02-17 16:36 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915: Make user contexts bannable again! Patchwork
2019-02-17 16:39 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-17 17:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-17 17:31 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915: Make user contexts bannable again! (rev2) Patchwork
2019-02-17 17:34 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-02-17 17:51 ` ✓ Fi.CI.BAT: success " Patchwork
2019-02-17 23:12 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-02-18 10:45 ` Mika Kuoppala [this message]
2019-02-18 10:45 ` [PATCH 1/9] drm/i915: Make user contexts bannable again! Mika Kuoppala
2019-02-18 10:51 ` Chris Wilson
2019-02-22 15:24 ` Sasha Levin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y36dxtmb.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.