From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix crash in error state readout on non-execlist platforms v2
Date: Wed, 23 Sep 2015 10:34:57 +0200 [thread overview]
Message-ID: <20150923083457.GP3383@phenom.ffwll.local> (raw)
In-Reply-To: <1442336581-12442-1-git-send-email-jbarnes@virtuousgeek.org>
On Tue, Sep 15, 2015 at 10:03:01AM -0700, Jesse Barnes wrote:
> Looks like this was introduced in:
> commit d1675198ed1f21aec6e036336e4340c40b726497
> Author: Alex Dai <yu.dai@intel.com>
> Date: Wed Aug 12 15:43:43 2015 +0100
>
> drm/i915: Integrate GuC-based command submission
>
> This patch assumed LRC contexts and HWS layout, which is incorrect on
> platforms without execlists. This can lead to a crash in GPU error
> state readout on those platforms.
>
> I don't see a bug filed for this, but there may be one that I haven't
> found.
>
> v2: fixup offset handling for error capture fix (Dave)
>
> Cc: Alex Dai <yu.dai@intel.com>
> Reviewed-by: Dave Gordon <david.s.gordon@intel.com>
> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Queued for -next, thanks for the patch.
-Daniel
> ---
> drivers/gpu/drm/i915/i915_gpu_error.c | 18 ++++++++++++------
> 1 file changed, 12 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
> index 3379f9c..f95de05 100644
> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
> @@ -457,17 +457,23 @@ int i915_error_state_to_str(struct drm_i915_error_state_buf *m,
> }
>
> if ((obj = error->ring[i].hws_page)) {
> + u64 hws_offset = obj->gtt_offset;
> + u32 *hws_page = &obj->pages[0][0];
> +
> + if (i915.enable_execlists) {
> + hws_offset += LRC_PPHWSP_PN * PAGE_SIZE;
> + hws_page = &obj->pages[LRC_PPHWSP_PN][0];
> + }
> err_printf(m, "%s --- HW Status = 0x%08llx\n",
> - dev_priv->ring[i].name,
> - obj->gtt_offset + LRC_PPHWSP_PN * PAGE_SIZE);
> + dev_priv->ring[i].name, hws_offset);
> offset = 0;
> for (elt = 0; elt < PAGE_SIZE/16; elt += 4) {
> err_printf(m, "[%04x] %08x %08x %08x %08x\n",
> offset,
> - obj->pages[LRC_PPHWSP_PN][elt],
> - obj->pages[LRC_PPHWSP_PN][elt+1],
> - obj->pages[LRC_PPHWSP_PN][elt+2],
> - obj->pages[LRC_PPHWSP_PN][elt+3]);
> + hws_page[elt],
> + hws_page[elt+1],
> + hws_page[elt+2],
> + hws_page[elt+3]);
> offset += 16;
> }
> }
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-09-23 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 21:40 [PATCH] drm/i915: fix crash in error state readout on non-execlist platforms Jesse Barnes
2015-09-10 21:56 ` Yu Dai
2015-09-10 21:58 ` Jesse Barnes
2015-09-10 22:07 ` Yu Dai
2015-09-14 9:21 ` Daniel Vetter
2015-09-14 16:45 ` Dave Gordon
2015-09-15 17:03 ` [PATCH] drm/i915: fix crash in error state readout on non-execlist platforms v2 Jesse Barnes
2015-09-23 8:34 ` Daniel Vetter [this message]
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=20150923083457.GP3383@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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