All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/i915: Reduce fence usage for scanout
Date: Tue, 28 Jan 2014 20:39:29 +0100	[thread overview]
Message-ID: <20140128193929.GG7444@phenom.ffwll.local> (raw)
In-Reply-To: <20140128135106.GY9454@intel.com>

On Tue, Jan 28, 2014 at 03:51:06PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 28, 2014 at 01:12:44PM +0000, Chris Wilson wrote:
> > On Tue, Jan 28, 2014 at 02:51:53PM +0200, ville.syrjala@linux.intel.com wrote:
> > >   drm/i915: Don't waste fences for scanout when not needed
> > 
> > But it's gen2/3 that is short of fences (and we've a... I feel this is a
> > micro-optimisation, but now that it is done...
> 
> Yeah well, this will only "help" gen4 desktop parts and VLV since
> everything else has FBC AFAIK.

tbh I was afraid a bit that this will reduce testing coverage for that
rather nifty fence accounting bug in ppgtt. But it looks like we'll still
be ok.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

      reply	other threads:[~2014-01-28 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28 12:51 [PATCH 0/3] drm/i915: Reduce fence usage for scanout ville.syrjala
2014-01-28 12:51 ` [PATCH 1/3] drm/i915: Don't waste fences on sprite buffers ville.syrjala
2014-01-28 12:51 ` [PATCH 2/3] drm/i915: Fix fence leaks if fbdev setup fails ville.syrjala
2014-01-28 12:51 ` [PATCH 3/3] drm/i915: Don't waste fences for scanout when not needed ville.syrjala
2014-01-28 13:12 ` [PATCH 0/3] drm/i915: Reduce fence usage for scanout Chris Wilson
2014-01-28 13:51   ` Ville Syrjälä
2014-01-28 19:39     ` Daniel Vetter [this message]

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=20140128193929.GG7444@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.