00:19SolarAquarion: bnieuwenhuizen: that was fast, lmao
00:22karolherbst:thinks running the CTS just like that is only for beginners, pros run it compiled against libasan with mesa also compiled against libasan
00:23bnieuwenhuizen: hmm, I have never tried running Vulkan-CTS with asan
00:24bnieuwenhuizen: karolherbst: how do you make sure dependencies are compiled with asan?
00:25karolherbst: bnieuwenhuizen: doesn't matter
00:25bnieuwenhuizen: well, that is easy :P
00:25karolherbst: if you have one library you have to make sure to preload it, but if a binary was compiled against it, it will just load it :p
00:26karolherbst: bnieuwenhuizen: :D
00:26karolherbst: let's say.. the CTS has a weird way of using sizeof
00:26karolherbst: bnieuwenhuizen: https://github.com/karolherbst/VK-GL-CTS/commit/36a13458342d53608abd1ffd950b620edbd343b1
00:26karolherbst: but there are a few more issues
00:27karolherbst: anyway.. just wanted to get rid of all memory corruption bugs inside the CTS and mesa to at least get rid of those annoying fails
00:27karolherbst: like running the CTS for hours just so that something fails in the 50th iteration or so
01:00SolarAquarion: i'm getting a segmentation fault, but that may be because of ld
01:01SolarAquarion: gnu ld
02:35SolarAquarion: got a crash backtrace thanks to lld https://paste.debian.net/plain/1157371
02:36SolarAquarion: something is going on with OSMesa that's causing the linker to crash at that point
03:08dcbaker[m]: Are you using lto?
04:10airlied: jekstrand: any reason anv doesn't use I915_EXEC_BATCH_FIRST?
04:14airlied: ah I guess the batch bo can be anywhere in the list
04:26jekstrand: airlied: Because it doesn't really buy us anything. It's easy enough to swap two things.
04:27jekstrand: And, since we have to carry the swapping code anyway....
04:28airlied: jekstrand: I just thought it was always swapping 0 and last, but I'm not sure the code guarantees it's at 0 in the first place
04:29jekstrand: airlied: It doesn't
04:29jekstrand: airlied: In fact, I'm pretty sure we put state pools first.
04:29jekstrand: It's ok, one of these days VM_BIND is going to be a thing and then there will only be one BO in the list so it won't matter. :)
04:33airlied: vm_bind over uring :-P
07:00MrCooper: tomeu: looks like some of the new traces might be flaky: https://gitlab.freedesktop.org/mesa/mesa/-/jobs/3735818
07:45tomeu: MrCooper: cool, those are interesting artifacts, thanks
07:48tomeu: MrCooper: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6023
08:18icecream95: With panfrost, MSAA works for anything using EGL, but not GLX - glxgears -samples 4 fails with "couldn't get an RGB, Double-buffered, Multisample visual"
08:18icecream95: Any ideas for what needs to be changed or where to investigate? glxinfo doesn't show any multisample visuals.
08:21daniels: ajax: ^
08:32MrCooper: icecream95: which version of which X server?
08:36icecream95: MrCooper: Both X and Xwayland, 1.20.8
08:36MrCooper: with Xwayland it can only work with xserver Git master
08:36MrCooper: Xorg should work though, assuming its glx module can find the DRI driver
08:38MrCooper: grep the log file for "AIGLX"
08:39icecream95: AIGLX: Loaded and initialized rockchip, AIGLX: Screen 1 is not DRI2 capable
09:09MrCooper: the latter is likely related; would need to drill down why DRI2Connect returns FALSE
09:10icecream95: MrCooper: That seems to be related to fbdev - I uninstalled xf86-video-fbdev and it doesn't appear anymore
09:11MrCooper: hmm, can you pastebin the full Xorg log file and the output of glxinfo?
09:18icecream95: MrCooper: https://gitlab.freedesktop.org/snippets/1111/raw
09:25MrCooper: there are no GLXFBConfigs with multiple samples, looks like you need to dig into that in Mesa after all
09:26daniels: I wonder if we need to expose a higher GL version at some level?
09:27daniels: icecream95: how about MESA_GL_VERSION_OVERRIDE=3.1?
09:30MrCooper: daniels: lots of 'Branch cannot be merged' again since yesterday, maybe the workaround isn't that effective after all :(
09:36MrCooper: worth trying an even longer sleep, say 60s?
09:37daniels: mmm, that could help in some cases, but given there's a cache in play, it doesn't just rely on the background job (when CI completes, trigger a background job to check if the MR is now mergeable) to complete, but also something to invalidate the cache
09:38daniels: but sure, if you spin a new container with 60sec then I'll apply that - it's no worse than what we already have
09:41icecream95: It looks like my LD_LIBRARY_PATH isn't getting set for the Xorg process - where do I set environment variables for Xorg?
09:48MrCooper: icecream95: note that LD_LIBRARY_PATH won't affect where Xorg's glx module loads rockchip_dri.so from
09:49MrCooper: need LIBGL_DRIVERS_PATH for that
09:59icecream95: MrCooper: Where do I set them? Putting them in /etc/environment doesn't have any effect
10:00MrCooper: I'd expect that to work, check in /proc/<Xorg PID>/environ
10:05icecream95: MrCooper: /proc/`pidof Xorg`/environ only has PWD, SHLVL and PATH
10:07MrCooper: in the worst case, rename the Xorg binary and replace it with a wrapper script which exports the variables and then execs the real Xorg
10:12icecream95: MrCooper: /usr/bin/Xorg is already a wrapper script, so I just exported LD_LIBRARY_PATH and LIBGL_DRIVERS_PATH in there and now MSAA works :)
10:15karolherbst: mhh.. this TGSI seems pretty invalid to me: https://gist.githubusercontent.com/karolherbst/45584c8f36070ce84c2deacdb7c6102d/raw/2e66a837c016daffed34fcc69b19c0be2f17dfc6/gistfile1.txt
10:16karolherbst: "TEMP" accesses
10:19karolherbst: "double array;" in glsl ...
10:20karolherbst: but that still looks fine..
10:27MrCooper: daniels: pushed a new 0.9.2-sleep-60 tag to https://gitlab.freedesktop.org/daenzer/marge-bot/container_registry
10:53daniels: MrCooper: running now, ta
10:54MrCooper: thank you
10:54MrCooper: tomeu: another possibly flaky trace: https://gitlab.freedesktop.org/GL/mesa/-/jobs/3739208
11:03icecream95: tomeu: panfrost-t760-traces only seems to fail with rk3288-veyron-jaq-cbg-0
11:07daniels: icecream95: it works reliably on -1?
11:10icecream95: daniels: it appears so
11:12karolherbst: is there any way of properly debugging glsl_to_tgsi?
11:18daniels: icecream95: uhh
11:22daniels: goddamn, you're right. every execution of demo.trace on cbg-0 has killed the GPU; every execution of demo.trace on cbg-1 has succeeded
11:24daniels: tomeu: ^ can we please temporarily remove pathfinder demo.trace from the rotation (your 'flaky-trace' branch removed the next one down in the list instead) until we can figure out why that is?
11:25daniels: I wonder if there's some bizzare kind of silicon revision thing going on; I don't think it can be power since they both run through dEQP totally fine, and it's not anything else environmental since they're on the same rack with the same config, plus I'd expect power/memory/whatever issues to manifest much more randomly throughout runs, not specifically always on one trace
11:59haasn: https://0x1.st/5.txt wow, now there's a new one
12:02bnieuwenhuizen: haasn: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3242 ?
12:03haasn: neat, thanks
12:04haasn: I'll revert that commit until the gcc update is out
12:08tomeu: daniels: I think I would disable traces on 760 for now
12:09daniels: tomeu: so weird that it seems to only be the one pathfinder trace though?
12:10tomeu: daniels: yeah, I can only think that we have a race there
12:11tomeu: daniels: pathfinder/canvas_moire.trace also gets misrendered tiles
12:11daniels: but why only -0 and not -1 ...
12:16HdkR: Broken memory? Not terribly uncommon :)
12:21daniels: HdkR: it's _way_ too deterministic for broken memory
12:21daniels: (if you ask me)
12:22daniels: I mean, it runs all the way through 6-way parallel dEQP tests, but only ever fails on one very specific trace ... ?
12:30MrCooper: tomeu: disabling traces on 760 for now sounds good, otherwise we might have to revert the new traces for now, as it's preventing other MRs from merging
12:31tomeu: ok, it's in Marge's hands now
12:36haasn: why does mesa vendor vulkan headers/xml instead of using /usr/include/vulkan?
12:36haasn: this is causing me issues on latest master, because the mesa vulkan headers are out of date relative to the loader
12:38imirkin: haasn: what if the system headers are out of date? mesa won't compile...
12:38imirkin: also how could system headers being newer cause segfaults?
12:39haasn: imirkin: they added a new enum member in the middle of the enum
12:39imirkin: haasn: they're not supposed to do that
12:39haasn: I know
12:46haasn: https://github.com/KhronosGroup/Vulkan-Headers/pull/135 I guess
12:46gitbot: KhronosGroup issue (Pull request) 135 in Vulkan-Headers "Fix enum order for backwards compatibility" [Open]
12:50imirkin: haasn: this has nothing to do with mesa's vendoring, right? if you had a mesa built with old headers and an application/loader compiled with new headers, you'd get the same issue, no?
12:51SolarAquarion: dcbaker: yes
12:51SolarAquarion: i didn't activate lto
12:51haasn: imirkin: yeah, I namedropped mesa because it's an example of something nontrivial affected by this where the work-around involves "manually patching vulkan-headers"
12:52imirkin: seems like it would affect blob drivers even harder
12:52imirkin: since they're not as easy to patch
13:34haasn: https://0x1.st/0.txt also seems to be necessary
13:34haasn: what a mess
13:38imirkin: or just dump it into the enum so you don't have to forget next time?
13:38imirkin: oh right - this is in mesa, nevermind
13:39imirkin: does it matter? presumably it just has to be higher than the max platform that mesa supports
13:39haasn: yes, which is exactly the problem
13:39haasn: it isn't
13:39imirkin: mesa supports METAL?
13:39haasn: no, but _HEADLESS (which comes after _DISPLAY)
13:40imirkin: hehehe ok
13:40haasn: (_METAL is the highest)
13:40haasn: *sigh* it still segfaults, even with the enum order fixed, mesa's _max patched, and everything rebuilt thrice
13:40alyssa: robclark: I'm assuming the answer is "heck no", but I'm wondering if EXT_multisampled_render_to_texture could be inferred from GL3 MSAA in some simple cases via reordering opts (specifcally interested in WebGL)
13:41haasn: what an annoying regression. all I want to do is run my stupid test framework that worked fine for the past year and a half, not spend 2 hours debugging vulkan ecosystem
13:41alyssa: robclark: (Failing that, drirc options for firefox/chromium to force it...)
13:41imirkin: alyssa: you'd have to know that the underlying samples are never access directly in the future
13:41imirkin: alyssa: i don't think there's a way to guarantee that
13:41alyssa: imirkin: right..
13:42imirkin: maybe you can do it with the winsys framebuffer
13:42imirkin: i don't think you can ever peer into its samples when it's multisampled
13:42alyssa: it's FBOs I'm worried about
13:43alyssa: GL(ES)3 multisampling on mobile is *slow*
13:43alyssa: and that's exactly what webgl does in both FF and chrome
13:43imirkin: ideally you'd do the resolve on your way out of the tile buffer
13:43imirkin: but you can't with standard MSAA, which is why that ext exists ;)
13:43alyssa: right, which I have working via that extension with GLES chromium
13:43alyssa: but that doesn't do anything for desktop GL chromium which is what our users actually use, or ff which doesn't use the ext
13:43haasn: imirkin: in any case wsi_common_get_surface_support would definitely have to bounds-check `platform->surface` against that PLATFORM_MAX limit
13:43imirkin: alyssa: was it ever plumbed through mesa?
13:44alyssa: yeah, krh did for fd
13:44ajax: gah, icecream95 left
13:44haasn: otherwise it segfaults on reading past wsi_device->wsi
13:44imirkin: alyssa: nice
13:44haasn: (and dereferencing the resulting value)
13:44imirkin: haasn: i'm not really familiar with the vulkan stuff... not sure who the WSI experts are around here
13:44imirkin: when in doubt, jekstrand and bnieuwenhuizen ?
13:44ajax: oh good, they figured it out
13:54ajax: daniels: re the msaa thing (supra), the general answer to "why don't my fbconfigs reflect the thing i just changed" is "you need to restart xserver with those changes actually loaded"
13:54imirkin: oh, i hate that so much
13:55imirkin: so much time spent debugging that
13:55daniels: don't know what you mean, I have literally never spent hours furiously debugging code it turns out I wasn't actually running
13:55imirkin: other fun fact - X hard-codes the location that it loads dri drivers from
13:55imirkin: so the usual tricks don't help
13:55ajax: not if you're using xwayland from master! you're welcome.
13:56ajax: should wire up that egl backend to xfree86 too. i _guess_.
13:58ajax: not much to be done about the restart-the-server bit though, visuals are a static list built at server init time
13:58ajax: i _guess_ you could regenerate the fbconfigs dynamically and just strip off GLX_WINDOW_BIT for anything that doesn't have a visual, but that seems super fragile
13:58ajax: and would push the "where's my msaa" problem to "why do i only get msaa for pixmaps"
14:05MrCooper: imirkin: per the scrollback, the current Xorg glx module does respect LIBGL_DRIVERS_PATH
14:05imirkin: MrCooper: oh nice! that's new.
14:05imirkin: (as of last time i had to deal with this, which was admittedly a fairly long time ago)
14:06imirkin: i'll try to remember that next time i get to play with the glx server side of things
14:06imirkin: (which will hopefully be never, but one can never be so lucky...)
14:09bnieuwenhuizen: haasn: does it work with older mesa? I think we upgraded some of the vulkan headers in mesa to 1.2.148 already
14:12robclark: alyssa: if gl has that discard-framebuffer it could perhaps be inferred by detecting a sequence of draw(s) -> resolve -> discard-framebuffer.. I think that is what krh wants to do but sounds like a pita.. fwiw seems like firefox wayland is using gles (although don't know if it uses the multisample_render_to_texture thing)
14:14MrCooper: daniels: https://gitlab.freedesktop.org/GL/mesa/-/pipelines/180518 failed due to "Connection reset by peer" on Collabora LAVA runners
14:15daniels: yeah, for some reason our primary LAVA server is unhealthy, admins are looking into it atm
14:15daniels: I'm shortly going to be jumping in a car for a while, but if it's still unhealthy in an hour or whatever, please feel to insta-merge a disable with my A-b
14:15MrCooper: k, thanks
14:16imirkin:is picturing a trampoline inside a car...
14:19lynxeye: TBH trampolin inside a car doesn't sound totally atypical for a graphics guy...
14:21MrCooper: maybe it's a double decker bus :)
14:22imirkin: yeah, it was a bit unclear whether daniels was going to be jumping inside of a car, or whether he would be in the car while it was jumping
14:22imirkin: silly english language
14:28haasn: bnieuwenhuizen: I don't know, haven't tried bisecting anything yet
14:28haasn: it used to work in the past but that was also with older vulkan-layers / vulkan-headers
14:41EdB: 'into a car' would have help you :). But he can also have a trampoline next to the car because he enjoy getting into a car that way...
14:55alyssa: imirkin: car shaped bouncy castle?
14:55alyssa: robclark: IIRC invalidate framebuffer stuff is gles only... so that doesn't help for chrome/linux at least
14:56alyssa: maybe the real answer is to get chrome patched upstream to pick gles for [panfrost|freedreno|...]
14:56robclark: I guess you could detect other forms of invalidation (like glClear())..
14:57robclark: the ideal thing in general, I think, would be prefer gles if avail, otherwise fall back to gl
15:00robclark: maybe this is daniels car? https://www.youtube.com/watch?v=CJsbUFtnENs
15:01imirkin: ah yeah, that makes the most sense
15:02alyssa: robclark: oh, I guess why that was at the office..
15:04daniels: how did you know?!
15:05alyssa: daniels: I'm more impressed you can type on your phone with that thing.
15:08imirkin: alyssa: practice makes perfect, presumably?
16:09tomeu: collabora's lava lab is taking jobs again, after a reboot
16:27MrCooper: tomeu: now there's a MinIO related issue: https://gitlab.freedesktop.org/daenzer/mesa/-/jobs/3746435
16:58SolarAquarion: dcbaker: https://pastebin.com/raw/MsC5CbfE
16:59SolarAquarion: there's some strange conversions and stuff going in format_utils.h
17:11SolarAquarion: got the bc for osmesa https://u.teknik.io/qpIU4.bc
17:22anholt: MrCooper: I'm seeing that in my failing freedreno trace jobs, too.
17:23anholt: tried reverting the "prefix artifacts with device name", no luck
17:30danvet: mlankhorst, need to ff drm-misc-next-fixes now I think
17:30danvet: airlied, can you pls apply " [PATCH -next] dma-fence: Make symbol 'dma_fence_lockdep_map' static" right after merging mlankhorst 's latest pull?
17:31danvet: it's not yet in my inbox somehow, and drm-misc-next-fixes is also not yet ready
17:36pinchartl: danvet: is there still time to get https://lore.kernel.org/dri-devel/20200718001755.GA5962@pendragon.ideasonboard.com/ merged for v5.9 ?
17:38danvet: yeah I guess airlied should get around to vacuuming up pending pulls
17:39danvet: oh lolz, maintainer entry says drm-misc, doesn't come in through drm-misc
17:41pinchartl: danvet: there's a base branch shared with dmaengine, I'm a bit worried of messing this particular case up when merging through drm-misc ;-)
17:42danvet: yeah it's all fine
17:42danvet: just couldn't resist
17:42danvet:bad person sometimes
17:44alimon: tomeu: i'm trying to access the gitlab-ci docs and looks that was already moved to docs.mesa.org, can you point me to the link?
17:45alimon: tomeu: i found this one, https://docs.mesa3d.org/ci/index.html, is that all?
17:58jekstrand: I think this MR ought to win some sort of award for "most applicable lables" :)
18:03karolherbst: I noiced :D
18:04karolherbst: jekstrand: add "gallium" for the st/mesa bits :p
18:05karolherbst: and llvmpipe most likely as well?
18:05airlied: I guess I'll hold off on vallium until after that merge :-P
18:06karolherbst: airlied: no need
18:06karolherbst: lp_bld_nir is touched by that MR
18:06karolherbst: that's what you meant
18:07jekstrand: I am hoping to get at least the first half-dozen patches merged ASAP. Those are the ones that are going to be hell to rebase.
18:07karolherbst: the nouveau ones look fine btw
18:07jekstrand: The rest is also going to be a real pain but possible.
18:07jekstrand: karolherbst: Feel free to give tags on specific patches. :)
18:07jekstrand: karolherbst: Also, if you wouldn't mind testing it. Nouveau isn't in CI.
18:07karolherbst: yeah.. wil give it a shot on turing
18:08karolherbst: the actual arch where nir matters for nouveau :p
18:08danvet: oh nouveau is on the nir train now too?
18:08karolherbst: volta+ yes
18:08jekstrand: danvet: Just about everyone is on the NIR train these days.
18:08Sachiel: time to come up with something new then
18:09karolherbst: anyway, starting with volta we only do TGSI for internal shaders like the blitter
18:09karolherbst: everything else is nir only
18:10danvet: nice, I totally missed that volta+ nir for nouveau happened somehow
18:11ajax: hmph, nobody ported i915g yet?
18:11karolherbst: yeah, and the support isn't that bad either
18:11karolherbst: around 5 CTS fails the last time I checked
18:12jekstrand: ajax: No nor i915 classic. There was some chatter about it a long time ago though.
18:14airlied: nir->tgsi should cover i915g fine :-P
18:14karolherbst: probably :D
18:15anarsoul: I doubt anyone uses it anyway
18:15imirkin: danvet: realistically it's turing support... not a lot of volta's running around, but turing is the current "latest" gen for desktop/mobile GPUs (and is post-volta)
18:16anarsoul: imirkin: out of curiosity, what's the status of turing support in nouveau?
18:16imirkin: anarsoul: karolherbst has been doing a lot of work ironing out the issues
18:16imirkin: i believe it's pretty functional at this point - passes almost all of CTS
18:17anarsoul: I've recently got a laptop with gtx 1650 which is apparently turing
18:17imirkin: TU116 or whatever
18:17imirkin: should work.
18:17anarsoul: but I haven't tried nouveau on it :)
18:17karolherbst: anarsoul: use mesa-git, should just work (tm)
18:17imirkin: you'll need mesa from git, and also a recent kernel
18:17anarsoul: karolherbst: how does it coopearate with integrated video?
18:17karolherbst: there are some patches left I need to upstream, but nothing badly broken
18:18karolherbst: anarsoul: DRI_PRIME stuff
18:18karolherbst: the usual way
18:18anarsoul: blob way is to use prime-run
18:18karolherbst: not anymore
18:18karolherbst: they also support prime offloading now
18:18karolherbst: just different env vars
18:19karolherbst: and with turing you even get runtime suspend/resume
18:19karolherbst: just need to enable it or something?
18:19anarsoul: with nouveau?
18:19karolherbst: nvidia as well
18:19anarsoul: what about reclocking?
18:19karolherbst: all those helper scripts are not needed anymore with the nvidia driver
18:19karolherbst: no reclocking
18:19imirkin: what you don't get are clock speeds that allow the nvidia gpu to beat out the integrated one :)
18:19karolherbst: on some benchmarks nouveau is still faster though :p
18:20anarsoul: I see
18:20karolherbst: if you do some testing and find bugs, that would be really helpful!
18:20karolherbst: just did limited testing myself and mainly focused on the CTS and some benchmarks
18:20anarsoul: I was more interested in poking mesa driver :)
18:20imirkin: there are some turing-only features which could be exposed
18:20jekstrand: Like ray-tracing. :-P
18:21imirkin: not so much on the 1650
18:21karolherbst: and the VR stuff :p
18:21anarsoul: what's the tag for nouveau issues on gitlab?
18:21jekstrand: Yeah, no ray-tracing on 1650, even with the blob.
18:21anarsoul: jekstrand: 1650 doesn't have ray tracing
18:21jekstrand: Which is super-annoying. Because they support it on all the other 1600-series cards. Just not 1650.
18:22jekstrand: It's not fast if it's not an RTX card, but it works.
18:22karolherbst: anarsoul: anyway, feel free to toy around and file bugs
18:22imirkin: but like e.g. NV_compute_shader_derivatives is turing+
18:22karolherbst: I will probably fix them or you :p
18:22karolherbst: I have a bunch of fixes already though
18:22jekstrand: imirkin: It's also IVB+ :-P
18:22jekstrand: (NV_compute_shader_derivatives, that is)
18:22imirkin: jekstrand: yes, that's why it's called NV_foo
18:22karolherbst: yeah.. not caring about exposing new extensions at this point except the core stuff is already wired up :D maybe later once I am done with the CTS stuff
18:22imirkin: core is wired up for that ext
18:22imirkin: i was going to add support for it
18:23karolherbst: ahh, cool
18:23anarsoul: karolherbst: are there any docs on isa?
18:23imirkin: but then noticed it was turing+
18:23karolherbst: jekstrand: ahh right, need to talk with skeggsb about it :D
18:23karolherbst: anarsoul: nothing public
18:23imirkin: anarsoul: feel free to ask in #nouveau about any specifics
18:23imirkin: we generally have a reasonable handle on it
18:24imirkin: [and i try not to bore #dri-devel with the details... usually.]
18:24anarsoul: do I understand correctly that nvidia has to open something (firmware?) in order to enable reclocking?
18:24imirkin: they have to provide signed firmware which exposes a stable ABI for the kernel-side driver to initiate reclocking
18:25anarsoul: I see
18:27anholt: ajax: ntt is my plan for how i915g (and virgl and svga and...) keep going. currently +6% instruction count, more loop unrolling (doesn't count towards that 6%), reduces uniforms count, reduces immediates. temps are a big issue currently, though.
18:28anholt: (tgsi only has a few bits for register indices, and if you don't do reusing of indices then you lose)
18:31karolherbst: anholt: emit immediate loads on use instead of when nir tells you
18:31karolherbst: that reduces temps a lot
18:32karolherbst: like 40% or so
18:32anholt: karolherbst: already done
18:32karolherbst: then probably the input stuff is next :p
18:32karolherbst: nir tends to load them at the start of a block
18:32anholt: also already done.
18:32anholt: or, I guess not.
18:33anholt: but that's not the temps issue, the issue is I'm not register allocating ssa defs or regs or my temps at all
18:33karolherbst: there is a pass even
18:33karolherbst: I see
18:33anholt: nir only has a block-level liveness for ssa defs so far
18:33karolherbst: I need to start caring about optimizing the nir path more :D
18:34anholt: oh, and load_input is already handled (you get alu opcodes with input/constant/sysval/immediate file references packed in)
18:35ajax: losing 6 of your 96 instructions on i915 is... well, screw it, your fault for still being on gen3
18:35karolherbst: I also meant ubos and wahtever though
18:35jekstrand: anholt: Do you need more than block-level?
18:35jekstrand: I guess it depends on how you do RA
18:35anholt: jekstrand: for a straight line shader, I need to be able to free temps as I go, not at the end of the block
18:35jekstrand: anholt: Sure, but you can track liveness easily as you walk the shader.
18:35karolherbst: in case you are looking for ideas for a real RA, skip codegen, it's fundamentally flawed :p
18:36karolherbst: anholt: is your IR structured or unstructured?
18:36anholt: tgsi is structured
18:36karolherbst: I meant whatever you have post TGSI
18:36jekstrand: anholt: Have an array indexed by SSA def index and, set it to list_length(def->uses) when you see the def and decrement when you see a use.
18:36jekstrand: Crossing blocks gets a bit more tricky.
18:36airlied: karolherbst: for i915 and softpipe there is nothing post TGSI
18:36karolherbst: same as nv30 :/
18:36jekstrand: But, yeah, we could do some IP-based thing too if that'd be helpful.
18:37karolherbst: fun projects
18:38anholt: jekstrand: the ip based thing for ssa defs looked easy given having the control flow liveness sorted out already
18:38anholt: (then I just need to walk ssa defs and uses per instr to expand on those ranges)
18:39anholt: the ugly part is regs, but I'm hoping nir ends up being such a win that I don't care.
18:39jekstrand: anholt: Should be easy enough. Just walk each block backwards.
18:39jekstrand: Forwards requires reference-counting. Backwards doesn't.
18:39anholt: for ssa defs?
18:40jekstrand: because you only have one def so, when walking backwards, the moment you see it, it's free.
18:40anholt: with the separate pass, i don't even need that -- ssa def uses are just interval->end = MAX2(interval->end, instr ip), right?
18:40anholt: (ureg doesn't have any notion of cursors, so walking backwards sounds hard)
18:40anholt: walking backwards in codegen, that is
18:40jekstrand: Yeah, you don't want to walk backwards in codegen. That'd be a pain
18:41jekstrand: So you either do a more complicated thing to walk forwards and reference count
18:41jekstrand: Or you do a pre-pass that walks backwards.
18:41jekstrand: THe pre-pass sounds easier
18:41jekstrand: And it shouldn't affect compile time significantly.
18:41anholt: yeah, I'm going for real dumb and simple in the liveness pre pass.
18:42jekstrand: Or you can index the instructions and then compute the end by max(all uses)
18:42anholt: I'm curious to see if instr count goes to improvement once I stop doing extra movs for texturing.
18:42anholt: jekstrand: that was my plan
18:42jekstrand: The problem is that you still need a second pass
18:43jekstrand: Because the real question you're asking in codegen is "will this be used again?" so you know whether or not to free it.
18:44airlied: "90/90 sessions passed, conformance test PASSED
18:44anholt: with the prepass, I was figuring, after an instruction I do foreach_ssa_use(free temp if my instr's ip matches the end interval), and at the end of the block I free all temps whose end interval matches the block end.
18:44bnieuwenhuizen: airlied: which one?
18:44airlied: now to get it into master and CTS fixed
18:44airlied: bnieuwenhuizen: llvmpipe
18:44airlied: GL 4.5
18:44anholt: airlied: nice work
18:44bnieuwenhuizen: cool :)
18:45airlied: and if anyone knos anything about compliant line rendering https://gitlab.freedesktop.org/mesa/mesa/-/issues/3292
18:45jekstrand: anholt: Yeah, that should work.
18:46jekstrand: anholt: I'm not sure about blocks. I don't think you'll ever have the end of the live interval match block_end.
18:47jekstrand: It should always end at an instruction
18:47jekstrand: Well, unless you have phis
18:47jekstrand: Phi sources occur at block boundaries
18:48anholt: jekstrand: if my loop uses my outside-defined ssa def on each iteration, and has a conditional break after the use at the top of the loop, it should be in livein/liveout of the block containing the use, right?
18:49anholt: otherwise iteration 0 gets to overwrite it in the following blocks inside the loop, and iteration 1 gets junk
19:05EdB: jekstrand: I'm not sure the change on clover worth a label :)
19:23jekstrand: EdB: It's still a change to clover. :-P
19:31daniels: anholt: btw, let me know if you want a JWT to play around with MinIO stuff locally and see what's going on
19:34anholt: daniels: kinda confused, because pipelines are passing, but MrCooper had that same fail on not-freedreno.
19:36ajax: why is it so difficult to get vim to honor .editorconfig
19:36anholt: ajax: if it's any consolation, emacs is awful too.
19:36daniels: anholt: schrödinger's pipelines are passing and also not passing ... ?
19:36imirkin: we have .emacs files in mesa
19:37imirkin: or .dir-whatever, i forget the name
19:38tomeu: alimon: there's still some docs that haven't been moved to pages, but are about to
19:39anholt: daniels: hmm, is the DurationSeconds=900 in ci_fairy.py meaning the minio credentials will only be good for 15 minutes?
19:39anholt:would expect lots of intermittent loss in that case
19:41daniels: I don't know; I've never touched ci-fairy
19:42alimon: tomeu: so, in which part of the repo can i find that docs?
19:43tomeu: MrCooper: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6029
19:43tomeu: alimon: for example:
19:45jenatali: karolherbst (or maybe daniels?): Would love if someone would add appropriate labels for https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6030. Probably nir, spir-v, opencl
19:45alimon: tomeu: an specific question, where is the definition about which jobs send to which lava server?
19:45daniels: jenatali: sure, done
19:45alimon: tomeu: i'm not familiar with gitlab ci yaml files, i will need to review it
19:46tomeu: alimon: there's a gitlab runner instance per each lava lab
19:47tomeu: and that gitlab runner has bind-mounted a file with the lava token for the lab it's able to submit to
19:47tomeu: each gitlab ci job that submits to lava has a runner tag, so the job goes to the right runner
19:48tomeu: eg. the jobs to that go to baylibre's lab have this tag: mesa-ci-aarch64-lava-baylibre and to collabora's: mesa-ci-aarch64-lava-collabora
19:50tomeu: alimon: https://docs.mesa3d.org/ci/LAVA.html is up to date
19:50alimon: tomeu: ok thanks for the pointers, i will read about gitlab runners and the related code
19:50tomeu: you are welcome!
20:20jenatali: airlied: If I have patches for your libclc series, what's the right way to share those? Mainly using a hand-rolled mangler rather than the LLVM one, to support the async functions with ocl_event in the mangling, plus address spaces
20:41airlied: jenatali: just publish a new series, and say based on my work, dont worry about git authorship too much
20:43jenatali: Cool, that works
21:06alyssa----:down the framebuffer compression rabbit hole
21:07SolarAquarion: dcbaker: the compiler backtrace in 368 lines of llvm bitcode
21:14dcbaker[m]: SolarAquarion: I have no idea honestly, I just saw lld using lto in your last backtrace and lto can cause weird hard to debug issues like this
21:46daniels: danvet, airlied: when is the cutoff for misc pull? would be really nice to get the imx8 KMS driver in
21:47danvet: uh I already pleaded for an extension
21:47danvet: usually it's -rc6
21:47danvet: smash it into drm-misc-next, give up shipping product on upstream kernels
21:48danvet: the extension I pleaded for was for dma-fence and maarten did the pull request for that this morning
21:49daniels: can you make that extension another day or two? :)
21:49daniels: NXP vendor BSP makes me cry
21:49danvet: I kinda don't like that merge window rush thing ...
21:50danvet: fix upstream release cycle instead :-)
21:50danvet: or like just ship drm-tip
21:50daniels: but the kernel development process is perfect
21:50danvet: perfect for making innocent souls cries
21:50danvet: indeed perfect
21:51danvet: also bit late for english over here
21:51daniels: ah, you should get an extension
21:52airlied: danvet, daniels : for a new driver I can be a bit more flexible
21:52airlied: since in theory you can't break anything much
21:52airlied: but it should be a separate pull maybe for the initial merge if it can't make misc
21:52danvet: https://email@example.com/ <- airlied bugfix for right after maarten's pull
21:52danvet: it showed up now
21:53danvet: daniels, bribe mlankhorst to get that done then
21:53danvet: (the topic pull)
21:54daniels: awesome, thanks! I'll make sure that happens then - it can't cause regressions in any case ;)
21:54danvet: it's too pretty for that I guess
21:55SolarAquarion: dcbaker[m]: it may be a lld bug, but ld proper has issues
21:55mareko: what's your opinion on the PIPE_TRANSFER_* -> PIPE_MAP_* renaming?
21:58daniels: danvet: thing on screen is usually much more pretty than nothing on screen, so yeah, I guess ...
22:22jenatali: airlied: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6035 - I'm pretty sure that's all the libclc-related changes we're running with, minus a few for hooking up async copies
22:23jenatali: Though I'm happy to split it if people think it makes sense
22:40mareko: is there a manual how to add a gitlab pipeline to mesa?
23:36karolherbst: can we allow any user to assign labels to bugs?
23:37karolherbst: or a way of allow predefined labels when creating bugs or something
23:39jenatali: I'd also love to add labels to MRs while we're asking for features
23:41airlied: jenatali: you should be able
23:41airlied: at least I though reporter could do that, butmaybe not
23:41jenatali: airlied: Nope, only issues
23:41bnieuwenhuizen: airlied: labels on bugs is "reporter", labels on MR is "developer"
23:41airlied: ah lols
23:42bnieuwenhuizen: of course the short term small scale solution is to give jenatali developer access once he has submitted a few :)
23:43jenatali: There's a few more on my backlog I need to port over, but that still feels like a hurdle for first-time contributors. But I'm also new to GitLab so idk
23:44bnieuwenhuizen: honestly I feel that if there are new contributors who can't set tags it is for us to worry about them and not the new contributors (though maybe that is making new contributors feel too much like they aren't in control?)
23:46jenatali: I'm already a special case since I've been working on a fork for a while, but still talking to you all, so I probably can't really put myself in a typical new contributor's shoes
23:46danvet: 1y ago our first contributor process was like "try one of these bazillion tutorials about how to submit a patch to a mailing list, all of which don't really work"
23:47jenatali: ... I'm glad I waited until gitlab before trying to contribute then :)
23:54zf: (it worked for me)
23:54zf: (except that by that point people had stopped paying attention to the mailing list)