All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhi Wang <zhi.a.wang@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Cc: "Niu, Bing" <bing.niu@intel.com>
Subject: Do we also need to reset HW when execlist mode is enabled?
Date: Wed, 24 Jun 2015 05:41:08 +0800	[thread overview]
Message-ID: <5589D274.8010306@intel.com> (raw)

Hi Experts:
	Recently we found that when i915 module got unloaded, when we were
debugging some bugs in XenGT. It would not reset HW under execlist mode.
I'm not sure if this is an issue. But if we keep loading/unloading
module with the different submission mode, e.g. from execlist mode to
ring buffer mode via loading/unloading i915, this should be a corner
case.... Maybe you can provide some advice, or make sure if we need to
fix it. :)

If so, we can submit a patch. :)

Code:
void i915_gem_context_fini(struct drm_device *dev)
{
        struct drm_i915_private *dev_priv = dev->dev_private;
        struct intel_context *dctx = dev_priv->ring[RCS].default_context;
        int i;

        if (dctx->legacy_hw_ctx.rcs_state) {
                /* The only known way to stop the gpu from accessing the
hw context is
                 * to reset it. Do this as the very last operation to
avoid confusing
                 * other code, leading to spurious errors. */
                intel_gpu_reset(dev);  // <------------ Move this one to
the beginning of the function.


Thanks,
Zhi.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 21:41 Zhi Wang [this message]
2015-06-24 13:47 ` Do we also need to reset HW when execlist mode is enabled? 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=5589D274.8010306@intel.com \
    --to=zhi.a.wang@intel.com \
    --cc=bing.niu@intel.com \
    --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.