From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/5] drm/i915/gt: Call intel_gt_sanitize() directly
Date: Fri, 1 Nov 2019 16:04:50 +0200 [thread overview]
Message-ID: <20191101140450.GC4215@intel.intel> (raw)
In-Reply-To: <20191030103827.2413-2-chris@chris-wilson.co.uk>
Hi Chris,
On Wed, Oct 30, 2019 at 10:38:24AM +0000, Chris Wilson wrote:
> Assume all responsibility for operating on the HW to sanitize the GT
> state upon load/resume in intel_gt_sanitize() itself.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Looks correct, Thanks
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
PS even though I sent you my rob in the reverse order, I read
them in the correct order :P
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915/gt: Call intel_gt_sanitize() directly
Date: Fri, 1 Nov 2019 16:04:50 +0200 [thread overview]
Message-ID: <20191101140450.GC4215@intel.intel> (raw)
Message-ID: <20191101140450.IrhbboyT-YpYmSxRirGclg8G27Eh0-W77s9qcsDyYbw@z> (raw)
In-Reply-To: <20191030103827.2413-2-chris@chris-wilson.co.uk>
Hi Chris,
On Wed, Oct 30, 2019 at 10:38:24AM +0000, Chris Wilson wrote:
> Assume all responsibility for operating on the HW to sanitize the GT
> state upon load/resume in intel_gt_sanitize() itself.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Looks correct, Thanks
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
PS even though I sent you my rob in the reverse order, I read
them in the correct order :P
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-01 14:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 10:38 [PATCH 1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive() Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-10-30 10:38 ` [PATCH 2/5] drm/i915/gt: Call intel_gt_sanitize() directly Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-11-01 14:04 ` Andi Shyti [this message]
2019-11-01 14:04 ` Andi Shyti
2019-10-30 10:38 ` [PATCH 3/5] drm/i915/gem: Leave reloading kernel context on resume to GT Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-11-01 13:47 ` Andi Shyti
2019-11-01 13:47 ` [Intel-gfx] " Andi Shyti
2019-10-30 10:38 ` [PATCH 4/5] drm/i915/gt: Move user_forcewake application " Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-11-01 13:42 ` Andi Shyti
2019-11-01 13:42 ` [Intel-gfx] " Andi Shyti
2019-10-30 10:38 ` [PATCH 5/5] drm/i915: Defer rc6 shutdown to suspend_late Chris Wilson
2019-10-30 10:38 ` [Intel-gfx] " Chris Wilson
2019-10-30 23:57 ` Andi Shyti
2019-10-30 23:57 ` [Intel-gfx] " Andi Shyti
2019-10-30 11:06 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gt: Always track callers to intel_rps_mark_interactive() Patchwork
2019-10-30 11:06 ` [Intel-gfx] " Patchwork
2019-10-30 11:30 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-30 11:30 ` [Intel-gfx] " Patchwork
2019-10-30 12:34 ` [PATCH 1/5] " Andi Shyti
2019-10-30 12:34 ` [Intel-gfx] " Andi Shyti
2019-10-31 11:55 ` ✓ Fi.CI.IGT: success for series starting with [1/5] " Patchwork
2019-10-31 11:55 ` [Intel-gfx] " Patchwork
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=20191101140450.GC4215@intel.intel \
--to=andi.shyti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox