00:43 fdobridge: <a​irlied> Test case 'dEQP-VK.api.copy_and_blit.core.buffer_to_depthstencil.d32_sfloat_s8_uint_DS'..
00:43 fdobridge: <a​irlied> Pass (CopiesAndBlitting test)
00:44 fdobridge: <a​irlied> leet haxor
01:00 fdobridge: <a​irlied> @gfxstrand care to throw https://gitlab.freedesktop.org/nouveau/mesa/-/merge_requests/217 at a cts run on your hw and see if anything explodes?
01:00 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> Let's try this with Overwatch 2 😅
02:24 fdobridge: <k​arolherbst🐧🦀> I wonder if that's indeed cheaper than using shaders...
02:24 fdobridge: <k​arolherbst🐧🦀> but maybe it is
02:28 fdobridge: <a​irlied> I've no idea if that path is even something apps would care about in practice
02:28 fdobridge: <k​arolherbst🐧🦀> some probably do
02:29 fdobridge: <a​irlied> like reading back depth stencil to the CPU side doesn't seem like a major thing to do
02:29 fdobridge: <a​irlied> maybe uploading preinited stencil textures is a thing though
02:30 fdobridge: <k​arolherbst🐧🦀> yeah.. no idea
02:30 fdobridge: <k​arolherbst🐧🦀> at least the copy engine is real, so I wouldn't be surprised it runs alongside shaders
02:30 fdobridge: <k​arolherbst🐧🦀> *if it
02:31 fdobridge: <k​arolherbst🐧🦀> heck.. there are GPUs with like 10 of those things
02:31 fdobridge: <k​arolherbst🐧🦀> really wondering if we have to do something to get automatic parallelism going or if there is some magic we have to do
02:35 HdkR: Titan V with its ten async copy engines is great
02:35 karolherbst: probably
02:36 karolherbst: mhhhhh
02:36 HdkR: As long as you know that the copy can be async, otherwise it'll be worthless
02:36 karolherbst: I wonder...
02:36 karolherbst: sooo
02:36 karolherbst: wild guess
02:36 karolherbst: NVC7B5_LAUNCH_DMA_DATA_TRANSFER_TYPE_PIPELINED + setting a sempahore we can wait on is the way to do it
02:36 karolherbst: whatever
02:38 karolherbst: mhhh we only use NON_PIPELINED
02:38 karolherbst: I wonder....
02:39 karolherbst: If I'd have time I'd even look into it :)
02:40 fdobridge: <k​arolherbst🐧🦀> @gfxstrand if you feel bored, it might be worth checking if PIPELINED dma copies can be make to work if we set a semaphore we wait on when the result is needed
02:40 fdobridge: <g​fxstrand> Mind filing a bug?
02:40 fdobridge: <k​arolherbst🐧🦀> sure
02:41 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> After some sleep of course 🐸
02:46 fdobridge: <k​arolherbst🐧🦀> https://gitlab.freedesktop.org/nouveau/mesa/-/issues/69
03:11 fdobridge: <g​fxstrand> Thanks
03:11 fdobridge: <g​fxstrand> Yeah, right now we're REALLY WFI-happy.
03:11 fdobridge: <g​fxstrand> We need to clean that up
03:12 fdobridge: <k​arolherbst🐧🦀> I suspect for that to properly work we kinda have to be able to reorder things
03:12 fdobridge: <g​fxstrand> I've been more focused on correctness than those details so far. That really needs to be cleaned up.
03:12 fdobridge: <k​arolherbst🐧🦀> yeah, fair
04:32 fdobridge: <a​irlied> @gfxstrand !202 is probably also trivial to land
04:39 fdobridge: <g​fxstrand> I'm run them tomorrow
05:39 fdobridge: <a​irlied> cool thx
08:22 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> This commit was remade with code styling changes (I think)
10:07 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> `m Files (x86)/Overwatch/_retail_/Overwatch.exe: ../mesa/src/nouveau/nil/nil_image.c:407: nil_image_init: Assertion 'nil_format_supports_color_targets(dev, info->format)' failed.` 🤔
10:10 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> The modifier change strikes again 🐸
10:21 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> After reverting that I now get this classic error: `m Files (x86)/Overwatch/_retail_/Overwatch.exe: ../mesa/src/nouveau/vulkan/nvk_descriptor_set.c:64: write_image_view_desc: Assertion 'view->storage_desc_index < (1 << 11)' failed.`
10:40 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> And after disabling the asserts I get this: `kernel: nouveau 0000:01:00.0: fifo: PBDMA0: 00040000 [PBENTRY] ch 4 [00ffa33000 Overwatch.exe[252519]] subc 0 mthd 1d00 data 00000000`
10:50 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> I think I got a bit further with `NV50_PROG_OPTIMIZE=0`: https://pastebin.com/as80zRPM
13:50 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> Apparently older DXVK versions need VK_FORMAT_R4G4B4A4_UNORM_PACK16 🫃
13:50 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹>
13:50 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> Let's add this if possible
14:00 mntirc: hmm, trying blender 3.4 on an arm machine with GeForce NV106 (0x800b) results in: nir_alu_instr only supported with 1 component!
14:00 mntirc: (and segfault)
14:02 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> Or maybe swizzles are problematic for some reason: https://github.com/doitsujin/dxvk/commit/a6d554615e5f939826db758263f9b59ea2333ecc
14:11 mntirc: i also get these errors in chromium
14:12 mntirc: is that expected, i.e. is NV106 now unsupported, or could this be arm platform specific?
14:15 DodoGTA: mntirc: The current nouveau compiler is just not good (that's why NAK is being worked on)
14:16 mntirc: DodoGTA: oh :( is there a workaround? can i switch back to TGSI or something?
14:26 mntirc: ah, it works with mesa 22.3.6
14:26 mntirc: i think the compiler i used to build mesa on this platform might be broken
14:33 mntirc: hmm, does nv106 even require firmware?
14:35 mntirc: looks like no (???)
14:36 DodoGTA: mntirc: This might be the problematic commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/47251d28527371aeb82f9db7592cff5e78bfcd55
14:39 mntirc: DodoGTA: thanks!
14:41 mntirc: did kepler gpus not have required firmware?
14:43 karolherbst: I really have to look into this one component thing because that got to be a nir regression or something...
14:43 karolherbst: we scalarize everything, so I'm surprised we even hit this
14:44 mntirc: other than that, i'm surprised how well this gpu+nouveau works with an arm cpu
19:42 fdobridge: <!​[NVK Whacker] Echo (she) 🇱🇹> First DXVK checkbox has been ticked
21:57 fdobridge: <g​fxstrand> I ran it. CTS is mostly good. I just haven't had a chance to look at the code. I've been in meetings literally all day.
21:57 fdobridge: <g​fxstrand> @airlied On the upside, @sima and I may have solved synchronization.