From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: Add missing ring_mask to Pineview
Date: Fri, 29 Jul 2016 11:42:24 +0300 [thread overview]
Message-ID: <1469781744.4094.59.camel@linux.intel.com> (raw)
In-Reply-To: <1469749535-2382-1-git-send-email-chris@chris-wilson.co.uk>
On pe, 2016-07-29 at 00:45 +0100, Chris Wilson wrote:
> It appears that we never told Pineview it has a RENDER_RING. This was
> all fine until we started using the ring_mask for determining all the
> available rings to initialise for legacy ringbuffer submission in commit
> 88d2ba2e95c8 ("drm/i915: Unify engine init loop"). Though really it is a
> latent bug since the ring_mask inception in commit 73ae478cdf6a
> ("drm/i915: Replace has_bsd/blt/vebox with a mask").
>
> To prevent similar mishaps in future, add a WARN_ON() if we find
> ourselves with a device without any rings.
>
> Fixes: 73ae478cdf6a ("drm/i915: Replace has_bsd/blt/vebox with a mask")
> Fixes: 88d2ba2e95c8 ("drm/i915: Unify engine init loop")
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Ben Widawsky <ben@bwidawsk.net>
> ---
> drivers/gpu/drm/i915/i915_pci.c | 1 +
> drivers/gpu/drm/i915/intel_engine_cs.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c
> index 949c01686a66..2587b1bd41f4 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -173,6 +173,7 @@ static const struct intel_device_info intel_pineview_info = {
> .gen = 3, .is_g33 = 1, .is_pineview = 1, .is_mobile = 1, .num_pipes = 2,
> .need_gfx_hws = 1, .has_hotplug = 1,
> .has_overlay = 1,
> + .ring_mask = RENDER_RING,
> GEN_DEFAULT_PIPEOFFSETS,
> CURSOR_OFFSETS,
> };
> diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
> index 31d43dfa7469..e6422aac2919 100644
> --- a/drivers/gpu/drm/i915/intel_engine_cs.c
> +++ b/drivers/gpu/drm/i915/intel_engine_cs.c
> @@ -117,6 +117,7 @@ int intel_engines_init(struct drm_device *dev)
> unsigned int i;
> int ret;
>
> + WARN_ON(INTEL_INFO(dev_priv)->ring_mask == 0);
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> WARN_ON(INTEL_INFO(dev_priv)->ring_mask &
> GENMASK(sizeof(mask) * BITS_PER_BYTE - 1, I915_NUM_ENGINES));
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-29 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 23:45 [PATCH] drm/i915: Add missing ring_mask to Pineview Chris Wilson
2016-07-29 5:51 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-07-29 15:25 ` Chris Wilson
2016-07-29 8:42 ` Joonas Lahtinen [this message]
2016-07-29 8:57 ` [PATCH] " Daniel Vetter
2016-07-29 11:10 ` Chris Wilson
2016-07-29 18:54 ` Ben Widawsky
2016-08-02 14:34 ` Daniel Vetter
2016-08-02 14:47 ` Chris Wilson
2016-08-03 7:33 ` Daniel Vetter
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=1469781744.4094.59.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox