From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 34778] New: [r600g, wine] FEAR / depth-stencil rendering triggers SW fallback
Date: Sat, 26 Feb 2011 12:58:54 -0800 (PST) [thread overview]
Message-ID: <bug-34778-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=34778
Summary: [r600g, wine] FEAR / depth-stencil rendering triggers
SW fallback
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
URL: http://www.gamershell.com/download_10167.shtml
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: liquid.acid@gmx.net
System:
ATI Technologies Inc Radeon HD 4770 [RV740]
drm-radeon-testing kernel (git tip)
libdrm, mesa and xf86-video-intel git master
xorg-server-1.9.4
mesa git master = 99b9019716d0a5cfc7438677d2e11090d676c054
Hi there,
this is sort of copy&paste from bug #34674. The problem (fallback to software
rendering) described there also happens on r600g, and probably (judging from
the state tracker code) on all gallium drivers.
Anyway, from profiling I found out that pipe_put_tile_z and pipe_get_tile_z
consume like 90% of the CPU time. These two get called by
fallback_copy_texsubimage, which is called from st_copy_texsubimage.
Greets,
Tobias
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-26 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 20:58 bugzilla-daemon [this message]
2011-05-07 0:41 ` [Bug 34778] [r600g, wine] FEAR / depth-stencil rendering triggers SW fallback bugzilla-daemon
2011-07-12 0:08 ` 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-34778-502@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.