public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mario Kleiner <mario.kleiner.de@gmail.com>
To: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Pageflipping bugs in drm-next on at least Ironlake and Ivybridge.
Date: Wed, 6 Jul 2016 12:17:55 +0200	[thread overview]
Message-ID: <577CDAD3.1030809@gmail.com> (raw)

Since i pulled the current drm-next tree i see strong flicker and visual 
corruption during pageflipping, both in my own app, but also in KDE4 and 
KDE5 Plasma with desktop composition enabled. This happens on both Intel 
HD Ironake mobile (Apple MBP 2010) and HD-4000 Ivybridge mobile (Apple 
macMini 2012).

It looks like page flips are not waiting properly for rendering to 
complete, showing partially rendered frames at flip time.

If i revert Daniel's commit that switches legacy pageflips from the old 
code path to the atomic code, all problems disappear, so apparently the 
atomic code for Intel is not quite ready at least on those parts?

In case this helps: As i was also testing DRI3/Present + PRIME on the 
hybrid graphics MBP, if i use the Intel HD as display gpu and the 
NVidia/nouveau as render offload gpu i don't get any corruption/flicker 
even with the atomic pageflip code for legacy pageflips. Iow. the path 
using dmabuf fence wait in intel_prepare_plane_fb works fine.

thanks,
-mario
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-07-06 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 10:17 Mario Kleiner [this message]
2016-07-06 13:05 ` Pageflipping bugs in drm-next on at least Ironlake and Ivybridge Chris Wilson
2016-07-06 13:43   ` Mario Kleiner

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=577CDAD3.1030809@gmail.com \
    --to=mario.kleiner.de@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --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