All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Record default HW state in the GPU error state
Date: Mon, 27 Nov 2017 14:02:03 +0200	[thread overview]
Message-ID: <1511784123.4627.28.camel@linux.intel.com> (raw)
In-Reply-To: <20171126220901.14735-1-chris@chris-wilson.co.uk>

On Sun, 2017-11-26 at 22:09 +0000, Chris Wilson wrote:
> It may be of interest to both compare the active HW context against the
> default (or NULL) context, to see what has been changed and if either are
> corrupt.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>

<SNIP>

> @@ -1414,6 +1417,23 @@ static void request_record_user_bo(struct drm_i915_gem_request *request,
>  	ee->user_bo_count = count;
>  }
>  
> +static struct drm_i915_error_object *
> +capture_object(struct drm_i915_private *dev_priv,
> +	       struct drm_i915_gem_object *obj)
> +{
> +	if (obj && i915_gem_object_has_pages(obj)) {
> +		struct i915_vma vma = {

fake_vma to put emphasis this is a trick?

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
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

  parent reply	other threads:[~2017-11-27 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 22:09 [PATCH] drm/i915: Record default HW state in the GPU error state Chris Wilson
2017-11-26 22:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-26 23:54 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-11-27 12:02 ` Joonas Lahtinen [this message]
2017-11-27 12:17   ` [PATCH] " Chris Wilson

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=1511784123.4627.28.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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 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.