00:22 <alyssa> ^^

03:10 <i509vcb> dEQP-VK.api.copy_and_blit.core.image_to_image.3d_images.2d_to_3d_whole does a per layer copy (only copying one layer at a time) but seems to just only ever write on the first layer?

03:10 <i509vcb> On possible issues, the PBE and TEXTURE descriptors look just like gallium's

03:12 <i509vcb> Using the dstSubresource just like the src image view in vk-meta didn't seem to change anything either: https://gitlab.freedesktop.org/i509VCB/mesa/-/commit/85f680952dc24685d39c049cf5ba968643a5a0ee#ccd82ce6d5431b9371915af7969698022e62444e_312_308

03:17 <alyssa> trace?

03:17 <i509vcb> Dimension: 2D

03:17 <i509vcb> Texture

03:17 <i509vcb> Depth: 256

03:17 <i509vcb> ...

03:18 <i509vcb> this shouldn't be possible?

03:26 <i509vcb> array copies start at .0032, up to ..0047 https://usercontent.irccloud-cdn.com/file/W8l9QzTm/dEQP-VK.api.copy_and_blit.core.image_to_image.3d_images.2d_to_3d_whole.zip

13:50 <alyssa> i509vcb: what you're seeing is that the Depth field overlaps the stride field

13:50 <alyssa> the hardware decodes the layout (Linear) first

13:51 <alyssa> we should probably make agxdecode smarter here but, effort

13:53 <alyssa> i509vcb: in those copies, you have layers = 1 in the UAPI, and the end-of-tile ("Store pipeline") writes to a non-arrayed 2D PBE descriptor with a non-layered 2D image write

13:53 <alyssa> so only layer 0 is ever touched