Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: 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: Thu, 22 Mar 2012 16:18:54 +0000	[thread overview]
Message-ID: <c55c5d$2cnmfu@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120322090709.59f3f5f2@bwidawsk.net>

On Thu, 22 Mar 2012 09:07:09 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> On Thu, 22 Mar 2012 09:56:07 +0000
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 
> > On Wed, 21 Mar 2012 17:19:13 -0700, Ben Widawsky <ben@bwidawsk.net>
> > wrote:
> > >   * 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().
> > ...apart from the whole pinning and pipelining. It looks less like
> > set-to-gtt-domain over time.
> > 
> > Not an improvement. I'll be the first to admit that it is not a great
> > comment, but at least it does try to capture why we don't just treat
> > the display plane as GTT. A better comment would explain our concept
> > of display plane and pipelining.
> 
> Separate patch though, don't you think? And it is now pipe-lining the
> waits, so I'm confused why you don't think it's an improvement.

Right. So how does removing the hint of why pin-to-display is different
from set-to-gtt when it now performs said function help improve the
comment? I completely agree that changing that comment is outside of the
scope of this patch.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-03-22 16:18 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 [this message]
2012-03-22 16:48         ` Ben Widawsky
2012-03-30 23:38   ` Daniel Vetter
2012-03-30 23:42     ` Chris Wilson
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='c55c5d$2cnmfu@AZSMGA002.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=ben@bwidawsk.net \
    --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