From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/6] drm/i915: Reinitialize default context after reset
Date: Fri, 19 Sep 2014 17:43:05 +0200 [thread overview]
Message-ID: <20140919154305.GG15734@phenom.ffwll.local> (raw)
In-Reply-To: <20140918153647.GF23478@nuc-i3427.alporthouse.com>
On Thu, Sep 18, 2014 at 04:36:47PM +0100, Chris Wilson wrote:
> On Thu, Sep 18, 2014 at 05:58:30PM +0300, Mika Kuoppala wrote:
> > We don't know in what shape the default context was before reset.
> > The reset also dropped our changes that were done in
> > ring->init_context.
> >
> > Mark our default context as uninitialized for it to be properly
> > setup up on reset recovery .
>
> The fundamental problem here is that context_init is not correctly split
> into init/init_hw (or init/enable) pairs. That is we simply do not
> attempt to reset the default state after reset via i915_gem_init_hw(). I
> would rather we brought rationality to the gem init/init_hw sequence
> first.
Yeah I agree with Chris that context setup doesn't follow our established
split with _init doing the software setup (and doesn't touch the hw at
all) and _init_hw doing the hw setup. _init is run at driver load, while
_init_hw is run at driver load, resume, after gpu reset and maybe even
from runtime pm code.
But I don't mind if we do this after or before this series, whatever is
less fuzz is fine with me.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-09-19 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 14:58 [PATCH 0/6] RFC: Persistent workarounds across reset/resume Mika Kuoppala
2014-09-18 14:58 ` [PATCH 1/6] drm/i915: Reinitialize default context after reset Mika Kuoppala
2014-09-18 15:36 ` Chris Wilson
2014-09-19 15:43 ` Daniel Vetter [this message]
2014-09-19 17:46 ` Volkin, Bradley D
2014-10-07 14:54 ` Mika Kuoppala
2014-09-18 14:58 ` [PATCH 2/6] drm/i915: Reinitialize default context after resume Mika Kuoppala
2014-09-18 14:58 ` [PATCH 3/6] drm/i915: Disable render idle on user forcewake Mika Kuoppala
2014-09-18 15:30 ` Chris Wilson
2014-09-18 15:54 ` Mika Kuoppala
2014-09-18 16:03 ` Chris Wilson
2014-09-18 17:05 ` Ville Syrjälä
2014-09-18 14:58 ` [PATCH 4/6] drm/i915: Build workaround list in ring initialization Mika Kuoppala
2014-09-19 15:49 ` Daniel Vetter
2014-09-18 14:58 ` [PATCH 5/6] drm/i915: Add ivb workarounds into the wa list Mika Kuoppala
2014-09-18 14:58 ` [PATCH 6/6] drm/i915: Check workaround status on dfs read time Mika Kuoppala
2014-09-18 15:18 ` [PATCH] tests/gem_workarounds: adapt to constant wa list from driver Mika Kuoppala
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=20140919154305.GG15734@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
/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