From: Chris Wilson <chris@chris-wilson.co.uk>
To: Chia-I Wu <olvaffe@gmail.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix current fb blocking for page flip.
Date: Thu, 21 Oct 2010 11:09:56 +0100 [thread overview]
Message-ID: <c6d829$pa46eb@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <AANLkTikm01fEHgfo1b86vd3V70d447giCk3XD85ud417@mail.gmail.com>
On Thu, 21 Oct 2010 17:55:13 +0800, Chia-I Wu <olvaffe@gmail.com> wrote:
> Hi list,
>
> According to the doc for page_flip, intel_crtc_page_flip should
>
> ... block all rendering to the current fb until the flip has
> completed.
>
> I am not entirely sure, but it seems that it is
> work->old_fb_obj->pending_flip that needs to be incremented instead of
> work->pending_flip_obj->pending_flip. This patch does fix the
> rendering artifacts with my Android on i915 project. Any thought?
My understanding is that we want to block any attempts to render to the
new back-buffer, i.e. the current front-buffer, until the flip has
occurred. Following that logic we need to increment pending flip on the
existing fb, which at first glance is indeed the fix you propose.
Jesse, Kirstian, thoughts?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-21 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 9:55 [PATCH] drm/i915: Fix current fb blocking for page flip Chia-I Wu
2010-10-21 10:09 ` Chris Wilson [this message]
2010-10-21 16:18 ` Jesse Barnes
2010-10-21 17:49 ` Chia-I Wu
2010-10-21 17:52 ` Jesse Barnes
2010-10-21 18:15 ` Kristian Høgsberg
2010-10-21 18:41 ` Chris Wilson
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='c6d829$pa46eb@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=olvaffe@gmail.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