public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 02/26] drm/i915: don't stop+start FBC at every flip
Date: Wed, 28 Oct 2015 16:58:49 +0000	[thread overview]
Message-ID: <1446051528.2750.5.camel@intel.com> (raw)
In-Reply-To: <20151027195044.GA24419@nuc-i3427.alporthouse.com>

Em Ter, 2015-10-27 às 19:50 +0000, Chris Wilson escreveu:
> On Tue, Oct 27, 2015 at 02:50:04PM -0200, Paulo Zanoni wrote:
> > @@ -1021,13 +1078,48 @@ void intel_fbc_flush(struct
> > drm_i915_private *dev_priv,
> >  	if (origin == ORIGIN_GTT)
> >  		return;
> >  
> > +	/* Hardware tracking already recompresses the CFB (nuke)
> > for us if FBC
> > +	 * is enabled and we do a page flip, so we can safely
> > ignore it here.
> > +	 * FBC may be disabled in case we got an invalidate()
> > before the
> > +	 * flush(), so we'll still have to check that case below.
> > */
> 
> I feel like I understand what is going on a bit better now, thanks!
> 
> > +	if (origin == ORIGIN_FLIP && dev_priv->fbc.enabled)
> > +		return;
> > +
> >  	mutex_lock(&dev_priv->fbc.lock);
> >  
> >  	dev_priv->fbc.busy_bits &= ~frontbuffer_bits;
> >  
> >  	if (!dev_priv->fbc.busy_bits) {
> > -		__intel_fbc_disable(dev_priv);
> > -		__intel_fbc_update(dev_priv);
> > +		if (origin == ORIGIN_FLIP) {
> 
> Note this test here is redundant.
> 
> We know that for an origin == FLIP to be here, FBC is disabled and
> calling intel_fbc_disable() is then a no-op.
> 
> So it turns out that the origin two lines of disable(); update()
> works
> just as well. Or is there some later patch that tweaks this branch
> further?

Right, you commented about this on the patch that is currently 04/26 an
I only fixed it there.

> -Chris
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-28 16:59 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27 16:50 [PATCH 00/26] Yet another FBC series, v2 Paulo Zanoni
2015-10-27 16:50 ` [PATCH 01/26] drm/i915: change no_fbc_reason from enum to string Paulo Zanoni
2015-10-27 16:50 ` [PATCH 02/26] drm/i915: don't stop+start FBC at every flip Paulo Zanoni
2015-10-27 18:32   ` Ville Syrjälä
2015-10-28 16:56     ` Zanoni, Paulo R
2015-10-28 17:20       ` Ville Syrjälä
2015-10-29 12:05         ` Maarten Lankhorst
2015-10-29 17:30         ` Ville Syrjälä
2015-10-29 17:52           ` Zanoni, Paulo R
2015-10-29 18:14             ` Ville Syrjälä
2015-10-27 19:50   ` Chris Wilson
2015-10-28 16:58     ` Zanoni, Paulo R [this message]
2015-10-27 16:50 ` [PATCH 03/26] drm/i915: rename intel_fbc_nuke to intel_fbc_recompress Paulo Zanoni
2015-10-27 16:50 ` [PATCH 04/26] drm/i915: only nuke FBC when a drawing operation triggers a flush Paulo Zanoni
2015-10-27 16:50 ` [PATCH 05/26] drm/i915: extract fbc_on_pipe_a_only() Paulo Zanoni
2015-10-29 12:05   ` Maarten Lankhorst
2015-10-29 15:55     ` Zanoni, Paulo R
2015-10-27 16:50 ` [PATCH 06/26] drm/i915: remove unnecessary check for crtc->primary->fb Paulo Zanoni
2015-10-27 16:50 ` [PATCH 07/26] drm/i915: extract crtc_is_valid() on the FBC code Paulo Zanoni
2015-10-27 16:50 ` [PATCH 08/26] drm/i915: set dev_priv->fbc.crtc before scheduling the enable work Paulo Zanoni
2015-10-27 16:50 ` [PATCH 09/26] drm/i915: use struct intel_crtc *crtc at __intel_fbc_update() Paulo Zanoni
2015-10-27 16:50 ` [PATCH 10/26] drm/i915: fix the __intel_fbc_update() comments Paulo Zanoni
2015-10-27 16:50 ` [PATCH 11/26] drm/i915: pass the crtc as an argument to intel_fbc_update() Paulo Zanoni
2015-10-27 16:50 ` [PATCH 12/26] drm/i915: don't disable_fbc() if FBC is already disabled Paulo Zanoni
2015-10-27 16:50 ` [PATCH 13/26] drm/i915: introduce is_active/activate/deactivate to the FBC terminology Paulo Zanoni
2015-10-27 16:50 ` [PATCH 14/26] drm/i915: refactor FBC deactivation at init Paulo Zanoni
2015-10-27 16:50 ` [PATCH 15/26] drm/i915: introduce intel_fbc_{enable, disable} Paulo Zanoni
2015-10-27 16:50 ` [PATCH 16/26] drm/i915: remove too-frequent FBC debug message Paulo Zanoni
2015-10-27 16:50 ` [PATCH 17/26] drm/i915: fix the CFB size check Paulo Zanoni
2015-10-27 16:50 ` [PATCH 18/26] drm/i915: alloc/free the FBC CFB during enable/disable Paulo Zanoni
2015-10-27 16:50 ` [PATCH 19/26] drm/i915: move adjusted_mode checks from fbc_update to fbc_enable Paulo Zanoni
2015-10-29 12:59   ` Maarten Lankhorst
2015-10-29 17:58     ` Zanoni, Paulo R
2015-11-02  8:53       ` Maarten Lankhorst
2015-10-27 16:50 ` [PATCH 20/26] drm/i915: move clock frequency " Paulo Zanoni
2015-10-27 16:50 ` [PATCH 21/26] drm/i915: check for FBC planes in the same place as the pipes Paulo Zanoni
2015-10-27 16:50 ` [PATCH 22/26] drm/i915: clarify that checking the FB stride for CFB is intentional Paulo Zanoni
2015-10-27 16:50 ` [PATCH 23/26] drm/i915: use a single intel_fbc_work struct Paulo Zanoni
2015-10-27 20:29   ` Chris Wilson
2015-10-28 17:24     ` Zanoni, Paulo R
2015-10-28 17:40       ` chris
2015-10-27 16:50 ` [PATCH 24/26] drm/i915: wait for a vblank instead of 50ms when enabling FBC Paulo Zanoni
2015-10-27 16:50 ` [PATCH 25/26] drm/i915: remove in_dbg_master check from intel_fbc.c Paulo Zanoni
2015-10-27 16:50 ` [PATCH 26/26] drm/i915: kill fbc.uncompressed_size Paulo Zanoni

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=1446051528.2750.5.camel@intel.com \
    --to=paulo.r.zanoni@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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