All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93216] Artifacts with DCC when render target also texture
Date: Wed, 20 Jan 2016 00:33:03 +0000	[thread overview]
Message-ID: <bug-93216-502-kpJceHM4VL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93216-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93216

--- Comment #5 from Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl> ---
I think we have cache coherency issues within a single draw call. One of the
situations in which a feedback loop is allowed is if we read and write every
texel at most once and we read the texel from the fragment shader invocation
that writes that texel.

My guess is that this is the case here, with two triangles. The problem is that
while every pixel is written at most once, every block of pixels can be
modified multiple times on the edges of a triangle.

This results in garbage if a later invocation for a tile sees modified pixel
data but stale DCC compression data, or stale pixel data and modified DCC
compression data.


This can be fixed by decompressing the framebuffer and disabling DCC
decompression for the framebuffer. I would like to avoid decompressing, but I
do not know how.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1767 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-01-20  0:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 17:17 [Bug 93216] Artifacts with DCC when render target also texture bugzilla-daemon
2015-12-02 17:18 ` bugzilla-daemon
2015-12-02 17:20 ` bugzilla-daemon
2015-12-02 17:37 ` bugzilla-daemon
2015-12-02 18:12 ` bugzilla-daemon
2016-01-20  0:33 ` bugzilla-daemon [this message]
2016-05-31 16:07 ` bugzilla-daemon
2018-04-05  0:20 ` bugzilla-daemon
2018-04-05  5:34 ` bugzilla-daemon

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=bug-93216-502-kpJceHM4VL@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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 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.