Skip to content

iris: Update comment about 2GB dynamic state range

Kenneth Graunke requested to merge kwg/mesa:bufmgr-comment into main

We tracked this down with the HW teams back in 2020 and there's now a documented workaround. Comments from the HW team say this applies all the way through XeHP but we're not sure beyond that.

This is a bug that we hit but the Windows drivers didn't because Jason decided to allocate our memory structures from the top end of the VMA range explicitly to catch bugs like this, while Windows allocates from zero and up, so they would need to allocate more than 2GB of dynamic state before running into it.

Closes: #4880 (closed)

Merge request reports