From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 14/15] drm/i915: Track frontbuffer invalidation/flushing
Date: Tue, 17 Jun 2014 11:33:41 +0200 [thread overview]
Message-ID: <20140617093341.GI5821@phenom.ffwll.local> (raw)
In-Reply-To: <20140617081014.GR17744@nuc-i3427.alporthouse.com>
On Tue, Jun 17, 2014 at 09:10:14AM +0100, Chris Wilson wrote:
> On Tue, Jun 17, 2014 at 09:52:17AM +0200, Daniel Vetter wrote:
> > On Tue, Jun 17, 2014 at 08:00:05AM +0100, Chris Wilson wrote:
> > > On Mon, Jun 16, 2014 at 07:51:34PM +0200, Daniel Vetter wrote:
> > > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > > index b8359f4a6dc4..dfdbf2a02844 100644
> > > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > > @@ -2755,6 +2755,8 @@ intel_pipe_set_base(struct drm_crtc *crtc, int x, int y,
> > > >
> > > > dev_priv->display.update_primary_plane(crtc, fb, x, y);
> > > >
> > > > + intel_frontbuffer_flush(dev, INTEL_FRONTBUFFER_PRIMARY(pipe));
> > >
> > > Conceptually all of these are just intel_fb_flip_complete. It may be
> > > easier in your tracking scheme to have:
> > >
> > > intel_fb_flip() { intel_fb_flip_prepare(); intel_fb_fip_complete(); }
> >
> > Yeah, this is just the direct flush for synchronous updates. Implementing
> > that as a prepare+complete is imo too confusing - the entire point of
> > prepare+complete is to catch an intermediate invalidates and not complete
> > the flush and so only really required for async flips. Hence why I prefer
> > to only do the full prepare+complete dance where needed. Otherwise there
> > is nothing special about flips.
>
> I just prefer to have the like operations having like names. The key
> point here is that we just want to treat the set-plane operations as a
> synchronous flip, which is distinct to the invalidate/flush operations on
> an active frontbuffer.
Well the main thing is the setplane is a flush operation. Flip is also a
flush, but an asynchronous one. Maybe s/flip/flush/ instead to make it
clear that the special part isn't that it's a flip, but that it's
two-stage?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-06-17 9:33 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 17:51 [PATCH 00/15] Accurate frontbuffer tracking and psr conversion Daniel Vetter
2014-06-16 17:51 ` [PATCH 01/15] drm/i915: Add missing statics to recent psr functions Daniel Vetter
2014-06-16 23:57 ` Rodrigo Vivi
2014-06-17 8:22 ` Daniel Vetter
2014-06-16 17:51 ` [PATCH 02/15] drm/i915: Drop unecessary complexity from psr_inactivate Daniel Vetter
2014-06-16 23:58 ` Rodrigo Vivi
2014-06-16 17:51 ` [PATCH 03/15] drm/i915: Ditch intel_edp_psr_update Daniel Vetter
2014-06-17 0:00 ` Rodrigo Vivi
2014-06-16 17:51 ` [PATCH 04/15] drm/i915: Run psr_setup unconditionally Daniel Vetter
2014-06-17 0:03 ` Rodrigo Vivi
2014-06-17 6:43 ` Chris Wilson
2014-06-17 7:23 ` Daniel Vetter
2014-06-17 8:26 ` Daniel Vetter
2014-06-16 17:51 ` [PATCH 05/15] drm/i915: Drop schedule_back from psr_exit Daniel Vetter
2014-06-17 0:06 ` Rodrigo Vivi
2014-06-17 7:25 ` Daniel Vetter
2014-06-16 17:51 ` [PATCH 06/15] drm/i915: Add a FIXME about drrs/psr interactions Daniel Vetter
2014-06-16 17:51 ` [PATCH 07/15] drm/i915: Track the psr dp connector in dev_priv->psr.enabled Daniel Vetter
2014-06-17 0:10 ` Rodrigo Vivi
2014-06-17 7:26 ` Daniel Vetter
2014-06-16 17:51 ` [PATCH 08/15] drm/i915: Don't try to disable psr harder from the work item Daniel Vetter
2014-06-17 0:20 ` Rodrigo Vivi
2014-06-17 7:29 ` Daniel Vetter
2014-06-16 17:51 ` [PATCH 09/15] drm/i915: Lock down psr sw/hw state tracking Daniel Vetter
2014-06-16 17:51 ` [PATCH 10/15] drm/i915: More checks for psr.enabled Daniel Vetter
2014-06-16 17:51 ` [PATCH 11/15] drm/i915: Add locking to psr code Daniel Vetter
2014-06-16 17:51 ` [PATCH 12/15] drm/i915: Introduce accurate frontbuffer tracking Daniel Vetter
2014-06-16 17:51 ` [PATCH 13/15] drm/i915: Use new frontbuffer bits to increase pll clock Daniel Vetter
2014-06-16 17:51 ` [PATCH 14/15] drm/i915: Track frontbuffer invalidation/flushing Daniel Vetter
2014-06-17 6:41 ` Chris Wilson
2014-06-17 7:32 ` Daniel Vetter
2014-06-17 7:36 ` Chris Wilson
2014-06-17 9:01 ` Daniel Vetter
2014-06-17 6:46 ` Chris Wilson
2014-06-17 7:33 ` Daniel Vetter
2014-06-17 6:49 ` Chris Wilson
2014-06-17 7:36 ` Daniel Vetter
2014-06-17 6:50 ` Chris Wilson
2014-06-17 7:37 ` Daniel Vetter
2014-06-17 7:40 ` Chris Wilson
2014-06-17 7:42 ` Chris Wilson
2014-06-17 6:52 ` Chris Wilson
2014-06-17 7:39 ` Daniel Vetter
2014-06-17 6:54 ` Chris Wilson
2014-06-17 7:45 ` Daniel Vetter
2014-06-17 7:53 ` Chris Wilson
2014-06-17 9:17 ` Daniel Vetter
2014-06-17 6:57 ` Chris Wilson
2014-06-17 7:48 ` Daniel Vetter
2014-06-17 7:55 ` Chris Wilson
2014-06-17 7:00 ` Chris Wilson
2014-06-17 7:52 ` Daniel Vetter
2014-06-17 8:10 ` Chris Wilson
2014-06-17 9:33 ` Daniel Vetter [this message]
2014-06-17 9:42 ` Chris Wilson
2014-06-17 9:54 ` Daniel Vetter
2014-06-17 10:00 ` Chris Wilson
2014-06-16 17:51 ` [PATCH 15/15] drm/i915: Fix up PSR frontbuffer tracking Daniel Vetter
2014-06-17 7:02 ` Chris Wilson
2014-06-17 8:06 ` Daniel Vetter
2014-06-17 7:07 ` Chris Wilson
2014-06-17 8:08 ` Daniel Vetter
2014-06-16 19:37 ` [PATCH 00/15] Accurate frontbuffer tracking and psr conversion Chris Wilson
2014-06-16 20:37 ` Daniel Vetter
2014-06-17 7:09 ` Chris Wilson
2014-06-17 9:30 ` 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=20140617093341.GI5821@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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