dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72685] [radeonsi hyperz] Artifacts in Unigine Sanctuary
Date: Sun, 17 Aug 2014 11:40:45 +0000	[thread overview]
Message-ID: <bug-72685-502-XaB6hwSwFl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-72685-502@http.bugs.freedesktop.org/>


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

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

--- Comment #25 from Marek Olšák <maraeo@gmail.com> ---
smoki, you can ignore that document. Sanctuary doesn't use shadow volumes for
shadows. It also doesn't use stencil.

There are 2 issues here:

1) HTILE doesn't seem to support rendering to an array texture with SLICE_START
== SLICE_MAX != 0 (non-zero layer). The workaround is to set
SLICE_START=SLICE_MAX=0 and add slice_size*slice_start to the base address.
This won't work with layered rendering, but we should still use the workaround
for non-layered rendering, because the performance improvement is really worth
it.

Note: r600g doesn't use HTILE for array textures, so it may see lower
performance increase from HyperZ in Sanctuary.

With the workaround above, the rendering is still broken, so it needs one more
workaround:

2) In-place DB flushing is broken with HTILE. The DB->CB copy can be used
instead.

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

[-- Attachment #1.2: Type: text/html, Size: 1822 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:[~2014-08-17 11:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 17:24 [Bug 72685] New: [radeonsi] artifacts and/or GPU crashes with htile bugzilla-daemon
2013-12-13 18:40 ` [Bug 72685] " bugzilla-daemon
2013-12-13 22:07 ` bugzilla-daemon
2013-12-13 22:10 ` bugzilla-daemon
2013-12-17 22:14 ` bugzilla-daemon
2013-12-18  2:31 ` [Bug 72685] [radeonsi hyperz] Artifacts in Unigine Sanctuary bugzilla-daemon
2013-12-18 22:58 ` bugzilla-daemon
2013-12-18 22:59 ` bugzilla-daemon
2013-12-18 23:00 ` bugzilla-daemon
2013-12-18 23:22 ` bugzilla-daemon
2013-12-18 23:27 ` bugzilla-daemon
2013-12-19  1:17 ` bugzilla-daemon
2014-01-22 12:02 ` bugzilla-daemon
2014-01-22 12:04 ` bugzilla-daemon
2014-01-22 13:15 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-05-17 14:06 ` bugzilla-daemon
2014-05-17 14:07 ` bugzilla-daemon
2014-05-19  3:54 ` bugzilla-daemon
2014-05-20 19:36 ` bugzilla-daemon
2014-05-22 21:19 ` bugzilla-daemon
2014-05-26 17:32 ` bugzilla-daemon
2014-08-11  6:30 ` bugzilla-daemon
2014-08-11  8:21 ` bugzilla-daemon
2014-08-11  8:33 ` bugzilla-daemon
2014-08-11  8:56 ` bugzilla-daemon
2014-08-16 16:58 ` bugzilla-daemon
2014-08-17 11:40 ` bugzilla-daemon [this message]
2014-08-17 14:00 ` bugzilla-daemon
2014-08-17 14:04 ` bugzilla-daemon
2014-08-17 14:45 ` bugzilla-daemon
2014-08-18  1:23 ` bugzilla-daemon
2014-08-24 13:44 ` bugzilla-daemon
2014-08-25  8:51 ` bugzilla-daemon
2014-09-01 19:32 ` 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-72685-502-XaB6hwSwFl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).