From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, Harsh Chheda <harsh.j.chheda@intel.com>
Subject: Re: [PATCH] drm/i915/guc: make forwarding of VBlanks conditional
Date: Fri, 17 Jun 2016 16:14:48 +0200 [thread overview]
Message-ID: <20160617141448.GS23520@phenom.ffwll.local> (raw)
In-Reply-To: <20160617135134.GL4329@intel.com>
On Fri, Jun 17, 2016 at 04:51:34PM +0300, Ville Syrjälä wrote:
> On Fri, Jun 17, 2016 at 02:42:39PM +0100, Dave Gordon wrote:
> > Apparently we shouldn't forward VBlanks to the GuC unconditionally,
> > as it may trigger a race condition in the GuC's internal dispatcher.
> >
> > From an internal message from Harsh Chheda <harsh.j.chheda@intel.com>
> > >
> > > If the context has switched out the [GuC] scheduler should know so
> > > that it can put the context in wait state and schedule something
> > > else. If the context which is waiting on Vblank is still on the CS
> > > then [the GuC] scheduler does not need to know. If in this case wait
> > > on Vblank is sent to Guc while the context is still on CS there is
> > > an edge condition when the Vblank may get satisfied right after
> > > sending interrupt to guc and context may complete. Scheduler will
> > > then incorrectly mark the context to be in wait state.
> >
> > So we need to change this register setting to GFX_FORWARD_VBLANK_COND.
>
> No one has ever managed to explain why the guc needs to get vblanks
> in the first place. The original commit message adding this stuff is
> not helpful at all.
It's used for the guc's magic slpc so that it can try to hit flips at
vrefresh. I maintain that this design is bonghits, and we should forward
_any_ display interrupts to guc. Instead the kernel should tell guc when
it's doing a sloppy job and missing deadlines. Because the kernel actually
knows, and doesn't have to infer what might be going on by watching
vblanks and flip_complete interrupts.
Also, with atomic we won't be using cs flips any more, who knows whether
that guc magic even still works with that ...
So I'd vote to just stop telling guc this stuff and be done with it.
-Daniel
>
> >
> > Signed-off-by: Dave Gordon <david.s.gordon@intel.com>
> > Cc: Harsh Chheda <harsh.j.chheda@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_guc_loader.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_guc_loader.c b/drivers/gpu/drm/i915/intel_guc_loader.c
> > index 8fe96a2..af9f51e 100644
> > --- a/drivers/gpu/drm/i915/intel_guc_loader.c
> > +++ b/drivers/gpu/drm/i915/intel_guc_loader.c
> > @@ -106,7 +106,7 @@ static void direct_interrupts_to_guc(struct drm_i915_private *dev_priv)
> > u32 tmp;
> >
> > /* tell all command streamers to forward interrupts and vblank to GuC */
> > - irqs = _MASKED_FIELD(GFX_FORWARD_VBLANK_MASK, GFX_FORWARD_VBLANK_ALWAYS);
> > + irqs = _MASKED_FIELD(GFX_FORWARD_VBLANK_MASK, GFX_FORWARD_VBLANK_COND);
> > irqs |= _MASKED_BIT_ENABLE(GFX_INTERRUPT_STEERING);
> > for_each_engine(engine, dev_priv)
> > I915_WRITE(RING_MODE_GEN7(engine), irqs);
> > --
> > 1.9.1
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-06-17 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 13:42 [PATCH] drm/i915/guc: make forwarding of VBlanks conditional Dave Gordon
2016-06-17 13:51 ` Ville Syrjälä
2016-06-17 14:14 ` Daniel Vetter [this message]
2016-06-17 15:00 ` Ville Syrjälä
2016-06-20 10:23 ` [PATCH] drm/i915/guc: don't ever forward VBlank to the GuC Dave Gordon
2016-06-20 12:58 ` Daniel Vetter
2016-06-20 12:57 ` [PATCH] drm/i915/guc: make forwarding of VBlanks conditional Daniel Vetter
2016-06-17 14:37 ` ✗ Ro.CI.BAT: failure for " Patchwork
2016-06-20 10:41 ` ✓ Ro.CI.BAT: success for drm/i915/guc: make forwarding of VBlanks conditional (rev2) 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=20160617141448.GS23520@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=harsh.j.chheda@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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