From: Chris Wilson <chris@chris-wilson.co.uk>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>, intel-gfx@lists.freedesktop.org
Subject: Re: Possible wrong flushes on SNB
Date: Tue, 11 Oct 2011 21:01:20 +0100 [thread overview]
Message-ID: <d08817$1qbu0n@azsmga001.ch.intel.com> (raw)
In-Reply-To: <20111011121316.GJ14679@ics.muni.cz>
On Tue, 11 Oct 2011 14:13:16 +0200, Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> Hi,
>
> I have SNB chip, with git driver 5913c90967091124e7c7b262782f0e99cf400eab,
> 3.1-rc9 kernel. I noticed that refresh of notification area or e.g., xosview
> refresh is linked with flashing. Looks like background exposing is synced with
> vertical refresh so it is visible and disturbing.
>
> This behaviour is more noticable at fresh start of system (after boot). If
> I run my desktop for several days, the problem disappears.
>
> Is it something new? Or something interesting so I should create a bug on fdo?
If you are using SNA, the likely cause of the flash is the flush, read,
modify, write of a fallback. That is we flush pending operations in the
batchbuffer (likely a fill to the scanout), read back from the scanout
the just modified region and perform the fallback with the CPU. That
modification is then queued up to be written out sometime in the near
future. That delay between the fill and the final write can cause
flickering.
By contrast UXA performs its fallbacks inplace and so such flicker
should not be any more perceivable than any other drawing operation.
File a bug. If you are using SNA, I'd like to prevent the fallback and
so avoid the flicker. Or I may have misdiagnosed it entirely, so in any
case I want sufficient information to reproduce.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-11 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 12:13 Possible wrong flushes on SNB Lukas Hejtmanek
2011-10-11 20:01 ` Chris Wilson [this message]
2011-10-12 13:56 ` Lukas Hejtmanek
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='d08817$1qbu0n@azsmga001.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=xhejtman@ics.muni.cz \
/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