All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhi Wang <zhi.a.wang@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	"Niu, Bing" <bing.niu@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Also perform gpu reset under execlist mode.
Date: Thu, 25 Jun 2015 05:56:58 +0800	[thread overview]
Message-ID: <558B27AA.9020404@intel.com> (raw)
In-Reply-To: <20150625123716.GK30757@nuc-i3427.alporthouse.com>

Hi Chris:
     Thanks for the reply! I just dig the code. It looks there is no 
special code path for execlist shutdown. It has init_rings(), but 
doesn't have cleanup_rings(), only clean_ring(), which are called for 
each ring one by one when i915_gem_cleanup_ringbuffer() gets called.

Do you have any advice? :)

Thanks,
Zhi.

于 06/25/15 20:37, Chris Wilson 写道:
> On Thu, Jun 25, 2015 at 12:24:59PM +0000, Wang, Zhi A wrote:
>> Hi Chris:
>>      Thanks for the comments that extends our knowledge about this modification. Really appreciate the help. But is it possible that we still need an ordinary gpu reset here? Consider that we may modprobe i915 with i915.enable_execlists=1 then unload it, then modprobe i915.enable_execlists=0, according to bspec, changing execlist mode to ringbuffer mode, a hardware reset is needed?
>
> Sounds credible that execlist -> execbuffer requires a reset. That reset
> should be called in execlist shutdown and documented appropriately.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-25 13:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 14:40 [PATCH] drm/i915: Also perform gpu reset under execlist mode bing.niu
2015-06-25  8:13 ` Chris Wilson
2015-06-25 12:24   ` Wang, Zhi A
2015-06-25 12:37     ` Chris Wilson
2015-06-24 21:56       ` Zhi Wang [this message]
2015-06-25 13:42         ` Chris Wilson
2015-06-24 22:13           ` Zhi Wang
2015-06-25 13:20   ` 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=558B27AA.9020404@intel.com \
    --to=zhi.a.wang@intel.com \
    --cc=bing.niu@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.