Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel@ffwll.ch>, Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: use semaphores for the display plane
Date: Sat, 31 Mar 2012 00:42:06 +0100	[thread overview]
Message-ID: <1333150952_162983@CP5-2952> (raw)
In-Reply-To: <20120330233824.GA5922@phenom.ffwll.local>

On Sat, 31 Mar 2012 01:38:24 +0200, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Mar 21, 2012 at 05:19:13PM -0700, Ben Widawsky wrote:
> > In theory this will have performance and power improvements. Performance
> > because we don't need to stall when the scanout BO is busy, and power
> > because we don't have to stall when the BO is busy ie. we can get the
> > work done sooner and put the CPU to sleep (and one less interrupt
> > required).
> > 
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > ---
> >  drivers/gpu/drm/i915/i915_gem.c |    8 +++-----
> >  1 file changed, 3 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> > index ce2fee5..96ad162 100644
> > --- a/drivers/gpu/drm/i915/i915_gem.c
> > +++ b/drivers/gpu/drm/i915/i915_gem.c
> > @@ -3041,9 +3041,7 @@ int i915_gem_object_set_cache_level(struct drm_i915_gem_object *obj,
> >   * any flushes to be pipelined (for pageflips).
> >   *
> >   * For the display plane, we want to be in the GTT but out of any write
> > - * domains. So in many ways this looks like set_to_gtt_domain() apart from the
> > - * ability to pipeline the waits, pinning and any additional subtleties
> > - * that may differentiate the display plane from ordinary buffers.
> > + * domains. So in many ways this looks like set_to_gtt_domain().
> >   */
> 
> For the comment bikeshed, what about:
> 
> "Prepare buffer for display plane (scanout, cursors, etc).
> Can be called from an uninterruptible phase (modesetting).
> 
> "For display planes we need to flush, synchronize with any outstanding
> rendering (pipelined using semaphores, if available, in case of a
> pageflip) and additionally need to ensure that the cache_level is coherent
> for the scanout engine."

It's an improvement over what we have certainly. Still doesn't explain
the why, but I've writers block as well.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-03-30 23:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  0:19 [PATCH 0/2] semaphorify the pageflip BO (if possible) Ben Widawsky
2012-03-22  0:19 ` [PATCH 1/2] drm/i915: extract ring sync code Ben Widawsky
2012-03-22  9:50   ` Chris Wilson
2012-03-22  0:19 ` [PATCH 2/2] drm/i915: use semaphores for the display plane Ben Widawsky
2012-03-22  9:56   ` Chris Wilson
2012-03-22 16:07     ` Ben Widawsky
2012-03-22 16:18       ` Chris Wilson
2012-03-22 16:48         ` Ben Widawsky
2012-03-30 23:38   ` Daniel Vetter
2012-03-30 23:42     ` Chris Wilson [this message]
2012-03-29  0:23 ` [PATCH 0/2] semaphorify the pageflip BO (if possible) Ben Widawsky
2012-03-29  8:49   ` 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=1333150952_162983@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --cc=daniel@ffwll.ch \
    --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