#asahi-gpu · 2023-08-17 21:16
i509vcbI learned of nir_lower_compute_system_values which seems to handle nir_intrinsic_load_num_workgroups#asahi-gpu · 2023-08-17 20:54
i509vcbthere was an agx opcode reference somewhere if I recall?#asahi-gpu · 2023-08-17 20:24
i509vcbindirect you are told how many workgroups you have?#asahi-gpu · 2023-08-17 20:21
i509vcbalthough that might not be whats good for vulkan#asahi-gpu · 2023-08-17 20:20
i509vcbin gallium you seem to load the number of workgroups in a sideband storage?#asahi-gpu · 2023-08-17 20:14
i509vcbHmm nvm I see something in asahi gallium#asahi-gpu · 2023-08-17 20:11
i509vcbNot sure where to look to handle nir_intrinsic_load_num_workgroups in agx_emit_intrinsic#asahi-gpu · 2023-08-17 19:19
i509vcbWhat's meant to be the intended way to do this?#asahi-gpu · 2023-08-17 19:18
i509vcb /s/ide/kde#asahi-gpu · 2023-08-17 19:18
i509vcbrestarting ide over ssh... I'd think just pkill -9 kwin_wayland but now am on a black screen#asahi-gpu · 2023-08-17 17:13
i509vcbWell there are other things I can do in the driver until then#asahi-gpu · 2023-08-17 17:07
i509vcbI was going to try to debug myself but I guess it happens with that's shipped so#asahi-gpu · 2023-08-17 16:59
i509vcbalyssa do you happen to know what kernel branch the timeline stuff is implemented in?#asahi-gpu · 2023-08-17 16:52
i509vcb3d not so sure#asahi-gpu · 2023-08-17 16:52
i509vcb1d and 2d have a depth of 1#asahi-gpu · 2023-08-17 16:52
i509vcbhttps://registry.khronos.org/vulkan/specs/1.3-extensions/html/vkspec.html#features-extentperimagetype#asahi-gpu · 2023-08-17 16:26
i509vcbwhere does the timeline kernel branch live again?#asahi-gpu · 2023-08-17 16:19
i509vcblina: assuming the driver supports timeline sync objects the branch I linked last night should be in a testable state#asahi-gpu · 2023-08-17 16:08
i509vcbBack before wgpu-hal and in the gfx-hal days, there was a proper GL 4.6 backend but that never really got ported over#asahi-gpu · 2023-08-17 16:06
i509vcbbut the fancy stuff will need vulkan for wgpu to expose it#asahi-gpu · 2023-08-17 16:06
i509vcbI do know that you can run wgpu in it's downlevel gles 3.0 mode currently#asahi-gpu · 2023-08-17 16:02
i509vcbfor extensions#asahi-gpu · 2023-08-17 16:02
i509vcbI think some parts of gallium also check the screen vtable as well#asahi-gpu · 2023-08-17 15:49
i509vcbbuffer object#asahi-gpu · 2023-08-17 03:49
i509vcbThe assert I hit has this ominous "We can only have one timeline mode" comment#asahi-gpu · 2023-08-17 03:47
i509vcbhowever other drivers seem to do fine with null at [2] and [1] being the timeline sync type#asahi-gpu · 2023-08-17 03:45
i509vcbIt's possible I don't exactly know what to do with the vk_sync stuff#asahi-gpu · 2023-08-17 03:45
i509vcbI also tested with setting sync_types[1] to &device->sync_timeline_type.sync and then putting NULL at [2] but that just fails on an assert in common code#asahi-gpu · 2023-08-17 03:44
i509vcbdEQP-VK.synchronization.basic.timeline_semaphore.* all hang I believe#asahi-gpu · 2023-08-17 03:43
i509vcbhttps://gitlab.freedesktop.org/i509VCB/mesa/-/commits/agxv/timeline-semaphore#asahi-gpu · 2023-08-17 03:40
i509vcbGive me a min and I'll push my current agxv branch so you can look at that#asahi-gpu · 2023-08-17 03:38
i509vcbI guess this isn't tested so no idea what could be wrong there#asahi-gpu · 2023-08-17 03:38
i509vcbFlipping the bits in agxv to turn on timeline semaphores just seems to hang forever on dEQP-VK.synchronization.basic.timeline_semaphore.one_queue#asahi-gpu · 2023-08-17 02:28
i509vcbThat seems weird#asahi-gpu · 2023-08-17 02:28
i509vcb> WorkQueue: Cannot submit, but queue is empty?#asahi-gpu · 2023-08-17 02:25
i509vcbI noticed that spam when I ran dEQP-VK.synchronization.basic.binary_semaphore.chain which failed before a reboot and works after a reboot#asahi-gpu · 2023-08-17 02:24
i509vcbWondering is there a reason why dmesg gets swamped with "Blocking due to compute queue full"?#asahi-gpu · 2023-08-17 02:15
i509vcbWayland compositor handover would be great for this type of situation...#asahi-gpu · 2023-08-17 02:13
i509vcbI think the compositor hung if I can't adjust volume, well I don't know the local IP off head so I guess I need to reboot anyways#asahi-gpu · 2023-08-17 02:11
i509vcbI'm guessing this type of hang I can't fix from just trying to ssh in...#asahi-gpu · 2023-08-17 02:09
i509vcbDidn't expect running a semaphore test to do that#asahi-gpu · 2023-08-17 02:09
i509vcbWell I knew it would happen eventually that I'd cause kde to hang#asahi-gpu · 2023-08-17 02:06
i509vcbok#asahi-gpu · 2023-08-17 02:04
i509vcbalyssa: looking at https://gitlab.freedesktop.org/asahi/mesa/-/blob/agxv/main/src/vulkan/runtime/vk_meta_copy.c#L558 multiple layers aren't handled yet, is this something more complicated than just run do_copy at different locations a few times or does some other part of agxv need to compensate for this?#asahi-gpu · 2023-08-16 23:09
i509vcbagxv_physical_device_try_create really makes me yearn for Rust's Result#asahi-gpu · 2023-08-16 20:58
i509vcbthe fun of dEQP-VK.api.device_init.create_instance_device_intentional_alloc_fail.basic, have to effectively rewrite agxv_physical_device_try_create to make the solution bearable#asahi-gpu · 2023-08-16 16:17
i509vcbseems like what v3dv is doing is fine given that the spec seems to says it's undefined behavior to pass an invalid fd#asahi-gpu · 2023-08-16 15:43
i509vcb(radv and nvk act correctly here since a prime fd could be from one of a few memory types and the memory type bits need to be set accordingly)#asahi-gpu · 2023-08-16 15:42
i509vcbSo the question is, which is right#asahi-gpu · 2023-08-16 15:42
i509vcbThe spec doesn't actually explicitly allow or forbid this