Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=5840
Summary: Mesa does not remove no-op state changes occuring
outside rendering commands
Product: Mesa
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P4
Component: Mesa core
AssignedTo: mesa3d-dev@lists.sourceforge.net
ReportedBy: [EMAIL PROTECTED]
I guess this puts an end to one witch hunt.
As far as I can see, fixing this inside Mesa would make state atom system used
in radeon disappear as it wouldnt serve any use. Instead, the state would be
fetched in prior to rendering.
This might however be little problematic as certain regs (might) need to be
written in some defined order.
Another solution would be to have low level state machine that sits in drm or
user space. In theory it might be possible to systematicly provide protection
against DOS attacks as the hardware state is always known. (It is very common
that certain register value is only valid in conjunction with rest of the
hardware state)
Caveat of this is obviously the amount of extra CPU overhead.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
