From: Matt Roper <matthew.d.roper@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Fix frontbuffer false positve.
Date: Tue, 3 Feb 2015 08:21:33 -0800 [thread overview]
Message-ID: <20150203162133.GI21349@intel.com> (raw)
In-Reply-To: <CAKMK7uHjJZQ6=Ts0XyNnACvfZ0XmeF9fVTyHRKRPsnyiPpXCSg@mail.gmail.com>
On Tue, Feb 03, 2015 at 12:57:31PM +0100, Daniel Vetter wrote:
> On Mon, Feb 02, 2015 at 03:38:16PM -0800, Rodrigo Vivi wrote:
> > frontbuffer bits must be updated during commit times not on atomica prepare
> > one, otherwise we have a risk of false positive.
> >
> > Cc Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Sonika Jindal <sonika.jindal@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> atomic.fb_bits isn't used at all right now, instead the
> begin_crtc_commit function recomputes them. That looks wrong.
We build up the collection of bits in atomic.fb_bits while going through
the atomic pipeline for each plane, then do a single call to
intel_frontbuffer_flip(dev, intel_crtc->atomic.fb_bits);
in intel_finish_crtc_commit to flush them all out together (and if
check/prepare fail, we never actually get to that flush).
> Also for async commits we need
> to do the proper 2-stage flip stuff that current page_flip code does using
> frontbuffer_flip_prepare/complete.
I need to look at the frontbuffer stuff again...maybe we don't need
atomic.fb_bits at all and should just use intel_frontbuffer_flip_prepare
in the places we set the bits now and intel_frontbuffer_flip_complete
where we're calling the flip mentioned above?
Matt
>
> This patch here should have 0 effect (presuming I'm reading code
> correctly), so what kinf of bug exactly are you seeing?
>
> Adding Matt&Ander.
> -Daniel
> --
> 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
next prev parent reply other threads:[~2015-02-03 16:21 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 [this message]
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
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=20150203162133.GI21349@intel.com \
--to=matthew.d.roper@intel.com \
--cc=ander.conselvan.de.oliveira@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox