All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Fix frontbuffer false positve.
Date: Tue, 24 Feb 2015 13:01:29 -0800	[thread overview]
Message-ID: <20150224210129.GR594@intel.com> (raw)
In-Reply-To: <20150224203825.GD24485@phenom.ffwll.local>

On Tue, Feb 24, 2015 at 09:38:25PM +0100, Daniel Vetter wrote:
> On Tue, Feb 24, 2015 at 10:44:19AM -0800, Matt Roper wrote:
> > On Tue, Feb 24, 2015 at 10:36:32AM -0800, Rodrigo Vivi wrote:
> > > Atomic bits needs to be set when cursor check function is returning 0
> > > and intel_crtc is active.
> > > 
> > > v2: When putting more debug prints I notice the solution was simpler
> > > than I thought. AMS design is solid, just this return was wrong.
> > > Sorry for the noise.
> > > 
> > > Cc: Matt Roper <matthew.d.roper@intel.com>
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > 
> > Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
> > 
> > > ---
> > >  drivers/gpu/drm/i915/intel_display.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > > index 8ccf033..5fb83ba 100644
> > > --- a/drivers/gpu/drm/i915/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/intel_display.c
> > > @@ -12198,7 +12198,7 @@ intel_check_cursor_plane(struct drm_plane *plane,
> > >  	}
> > >  
> > >  	if (fb == crtc->cursor->fb)
> > > -		return 0;
> > > +		goto finish;
> 
> Shouldn't we just delete this check entirely? gcc will do it anyway for
> us. When you do that you can also append the history I've dug out for
> this.

Yeah, that seems reasonable too.  The only thing we're actually skipping
at the moment is a tiling check which should never come true in this
case (otherwise we would have already failed on a previous cursor
update).


Matt

> 
> The original regression seems to have been introduced in the original
> check/commit split:
> 
> commit 757f9a3e5b8a812af0c213099a5b31cb423f4d3c
> Author: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Date:   Wed Sep 24 14:20:24 2014 -0300
> 
>     drm/i915: move check of intel_crtc_cursor_set_obj() out
> 
> Which already cause other trouble, resulting in the check getting moved in
> 
> commit e391ea882b1a04fb3f559287ac694652a3cd9da9
> Author: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> Date:   Wed Sep 24 14:20:25 2014 -0300
> 
>     drm/i915: Fix not checking cursor and object sizes
> 
> The frontbuffer tracking itself only was broken when we shifted it into
> the check/commit logic with:
> 
> commit 32b7eeec4d1e861230b09d437e95d76c86ff4a68
> Author: Matt Roper <matthew.d.roper@intel.com>
> Date:   Wed Dec 24 07:59:06 2014 -0800
> 
>     drm/i915: Refactor work that can sleep out of commit (v7)
> 
> Cheers, Daniel
> > >  
> > >  	if (fb->modifier[0] != DRM_FORMAT_MOD_NONE) {
> > >  		DRM_DEBUG_KMS("cursor cannot be tiled\n");
> > > -- 
> > > 2.1.0
> > > 
> > 
> > -- 
> > Matt Roper
> > Graphics Software Engineer
> > IoTG Platform Enabling & Development
> > Intel Corporation
> > (916) 356-2795
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

-- 
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-24 21:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 23:38 [PATCH] drm/i915: Fix frontbuffer false positve Rodrigo Vivi
2015-02-03  7:06 ` shuang.he
2015-02-03 11:57 ` Daniel Vetter
2015-02-03 16:21   ` Matt Roper
2015-02-03 18:46     ` Rodrigo Vivi
2015-02-03 19:14       ` Matt Roper
2015-02-03 19:38         ` Daniel Vetter
2015-02-03 19:40       ` Daniel Vetter
2015-02-13  1:17         ` Rodrigo Vivi
2015-02-13  8:48           ` Daniel Vetter
2015-02-24  1:52             ` Rodrigo Vivi
2015-02-24  2:13               ` Matt Roper
2015-02-24 17:32                 ` Rodrigo Vivi
2015-02-24 18:00                   ` Matt Roper
2015-02-24 18:36                     ` Rodrigo Vivi
2015-02-24 18:44                       ` Matt Roper
2015-02-24 20:38                         ` Daniel Vetter
2015-02-24 21:01                           ` Matt Roper [this message]
2015-02-24 21:37                             ` Rodrigo Vivi
2015-02-24 21:42                               ` Matt Roper
2015-02-24 22:09                                 ` Daniel Vetter
2015-02-25  8:13                                   ` Jani Nikula
2015-02-26  9:15                               ` shuang.he
2015-02-26  5:11                       ` shuang.he
2015-02-24  2:14               ` [PATCH] drm/i915: Clear crtc atomic flags at beginning of transaction Matt Roper
2015-02-24 17:43                 ` Rodrigo Vivi
2015-02-24 17:52                   ` Rodrigo Vivi
2015-02-03 19:34     ` [PATCH] drm/i915: Fix frontbuffer false positve 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=20150224210129.GR594@intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=daniel@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 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.