Open karolherbst opened 8 years ago
I have some nvidia-internal work in progress for a specific detail in zcull that should be polished enough for public review soon. The error you're seeing may or may not be related, but in recent chips there is a mode for saving and restoring zcull data automatically to a buffer on context switch, and if that mode is set but the address for this buffer is not, then you'd see an error.
thanks for your reply.
I don't even got zcull working at all. I think I figured out how I set the buffer and how to set the parameters for it, but that's pretty much it.
I don't know when to change the address and when to invalidate the zcull context and so on. Generally I am missing some kind of feedback from the zcull engine telling me how much it is doing and what is the issue it has with my input.
So maybe it would already help if I could read out the rejected fragments by zcull and by EarlyZ, so that I will know if it's partly working or not.
I think I managed to work out what I have to push to the gpu to configure zcull itself, but I kind of get the feeling, that either something is missing on the kernel side or some strange interactions with other engines on the gpu.
Anyway I get a "80000001" TRAP on the ZCULL, which means something we don't know yet. It is on the 0x0900 register of the GPC