From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, bing.niu@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Also perform gpu reset under execlist mode.
Date: Fri, 03 Jul 2015 13:52:10 +0300 [thread overview]
Message-ID: <87oajto6n9.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20150703090156.GC14231@nuc-i3427.alporthouse.com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> On Sat, Jul 04, 2015 at 12:27:34AM +0800, bing.niu@intel.com wrote:
>> From: "Niu,Bing" <bing.niu@intel.com>
>>
>> It is found that i915 will not reset gpu under execlist mode when
>> unload module. that will lead to some issues when unload/load module
>> with different submission mode. e.g. from execlist mode to ring
>> buffer mode via loading/unloading i915. Because HW is not in a reset
>> state and registers are not clean under such condition.
>>
>> Signed-off-by: Niu,Bing <bing.niu@intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> I think we may end up doing the reset unconditionally in
> i915_driver_unload() because this argument holds for almost everything
> we setup. It's a bigger risk because of doing the gpu-reset on more
> machines, but module-unloading is a "developer feature"!
And after that has been sorted, we should try reset on module load.
This way initial state would be identical to after reset/unload state.
Now we have this situation that we don't know how much we are leaning on
bios on state setup.
-Mika
> The only issue is making sure that the reset is ordered appropriately.
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-03 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 16:27 [PATCH v2] drm/i915: Also perform gpu reset under execlist mode bing.niu
2015-07-03 9:01 ` Chris Wilson
2015-07-03 10:52 ` Mika Kuoppala [this message]
2015-07-06 16:04 ` Zhi Wang
2015-07-07 8:58 ` Chris Wilson
2015-07-06 19:38 ` Zhi Wang
2015-07-07 11:17 ` Chris Wilson
2015-07-06 20:23 ` Zhi Wang
2015-07-07 12:00 ` Chris Wilson
2015-07-06 20:32 ` Zhi Wang
2015-07-07 12:10 ` Chris Wilson
2015-07-06 20:53 ` Zhi Wang
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=87oajto6n9.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox