09:18MrCooper: macc24: I read somewhere that even Nvidia will stop supporting generic SLI (with the generation after Ampere?); multi-GPU support will be all up to the applications, which should work with Mesa
09:19MrCooper: bnieuwenhuizen: please don't do such ugly workarounds in WSI; non-vsync swapchains are useful with Wayland as well (e.g. for lower input→output latency)
09:38mripard: airlied: danvet_: we have a few leftovers in drm-misc-next-fixes, should I just merge drm-misc-next-fixes into drm-misc-fixes and send you that PR later during the week, or would you prefer a final drm-misc-next-fixes PR today?
09:48danvet_: mripard, I think just merging it into the weekly -fixes is fine
09:48danvet_: that also makes dim push -next to linux-next again
09:53danvet_: mripard, [PATCH] drm/v3d: Fix double free in v3d_submit_cl_ioctl()
09:53danvet_: from Dan
09:53danvet_: fell through the cracks apparantly
09:53danvet_: while you're working -fixes :-)
09:53DPA: danvet_: Judgeing from your reply to a reply of v1 of my patch, are you not getting the mails I send to the list?
09:55danvet_: DPA, I need more context
09:55danvet_: like maybe archive link
09:56DPA: danvet_: https://lore.kernel.org/dri-devel/CAKMK7uEX38yzJGy6PWBs-L375kUGAPQK7SMPjT8Ze+3oKk38Mg@mail.gmail.com/T/#t
09:58danvet_: DPA, I only commented on this because vsyrjala found out that we have a general mess around modifier support in display drivers
09:59danvet_: DPA, did you expect something else?
10:00danvet_: DPA, you're patch hasn't shown up yet, but might just be stuck somewhere still, dunno
10:00danvet_: shown up here I mean
10:03DPA: danvet_: I see. I don't think it will. I'll have to ask the firstname.lastname@example.org to enable dmarc from header mungeing, I think that's the problem.
10:03emersion: what do you mean by "enable dmarc from header mungeing"?
10:04danvet_: yeah if you're dkim/dmarc is set up correctly, it should allow mailing list
10:04danvet_: if not, and you can't change that, then you need a different mail provider like gmail
10:05danvet_: sravn, just realized that it's better to update the kerneldoc example in the core constify patch
10:05danvet_: so I'll do that there, ok?
10:08emersion: > if you're dkim/dmarc is set up correctly, it should allow mailing list
10:08emersion: not quite
10:08DPA: danvet_: How is that supposed to work? The mailing list changes the message body, and since DMARC requires SPF Alignment, I can't make that match either. So the DMARC check is bound to fail.
10:08DPA: Or will the list allow me to set the From: header to the list and put my mail into the reply to to header myself?
10:08emersion: because lists.freedesktop.org mutates the emails
10:08emersion: adding a footer for instance
10:08emersion: DPA: DMARC doesn't require SPF alignment
10:08emersion: it requires either SPF or DKIM
10:09emersion: and with the current lists.fdo behaviour neither can work
10:09danvet_: yeah there's a magic way to set this up and get through mailing list
10:09danvet_: and a lot of other recommended ways which don't work
10:10danvet_: I forgot the details, but ffwll.ch works
10:10emersion: my recommendation is to stop mutating emails like lists.sr.ht, but there were concerns about unsubscribing, even though the standard List-Unsubscribe header is there
10:10emersion: danvet_: Authentication-Results: mailin006.protonmail.ch; dmarc=none (p=none dis=none)
10:11emersion: danvet_: anybody can send an email from ffwll.ch with this DMARC policy
10:12DPA: emersion: With enableing dmarc from header mungeing, I mean what is described here, see munge_from: https://mailman.readthedocs.io/en/release-3.1/src/mailman/handlers/docs/dmarc-mitigations.html
10:12emersion: oh please don't mungle From ;_;
10:13danvet_: emersion, well I set up something and gmail is happy now
10:13danvet_: email is broken anyway
10:13emersion: danvet_: and i can'
10:13emersion: t trust your emails
10:13emersion: > email is broken anyway
10:13danvet_: you shouldn't
10:13emersion: just because you break it doesn't mean it's broken
10:14emersion: anyways, if you really want to keep the silly footer, the "official" fix is https://tools.ietf.org/html/rfc8617
10:15emersion: * requires the receiving server to trust lists.fdo
10:15DPA: emersion: It's only for dmarc users. And I won't disable DMARC, I have DMARC reports showing that spoofing my mail address has been attempted at least once already.
10:15danvet_: yeah at that point you're down to mailer reputation
10:16emersion: DPA: yes i agree disabling DMARC like danvet_ does is not a good idea
10:16emersion: i don't have DMARC disabled either
10:16emersion: but mungling From is really bad UX
10:16emersion: google groups does it and it's terrible
10:18DPA: I've already got used to it.
10:18emersion: you mean, "my email client doesn't show the correct sender anymore and i'm fine with that"?
10:19emersion: also, "regular email operations like Reply vs. Reply-All don't work anymore"
10:21DPA: My mail client can "Reply to list -> all". And yes, I'm fine with that.
10:22emersion: this breaks email semantics badly
10:22danvet_: ok I read this crap again
10:22emersion: this is just a workaround, and there's a real proper solution available
10:24danvet_: I have dkim, that helps with getting mails accepted
10:24danvet_: and everything else maximally relaxed, so it gets in
10:24danvet_: because I need my mails to arrive
10:26emersion: well. maybe you don't care about email spoofing, but other people may care
10:26emersion: and recommend them to not care to post to the ML isn't great
10:27danvet_: have one domain for patch bombing
10:27danvet_: another one for stuff where you maximally lock down your mailer because business
10:27DPA: At least this the mailing list doesn't seam to reencode everything in base64.
10:27DPA: Maybe I can get away with revisiting my effort of specifying the count of to be verified bytes of the message in DKIM for certain emails again this time around.
10:28emersion: DPA: some receiving servers have a policy to reject DKIM signatures with a bh= param
10:28emersion: because it's inherently insecure
10:29emersion: danvet_: so the ML is broken, and each ML user needs to fix their setup to work around it?
10:30emersion: DPA: https://tools.ietf.org/html/rfc6376#section-8.2
10:31danvet_: emersion, I guess you can volunteer to admin a massive mail amplifier, dunno
10:31pq: bnieuwenhuizen, https://gitlab.freedesktop.org/xorg/app/xisxwayland/
10:32danvet_: real fix is going to be gitlab for patches and most discussions
10:33DPA: emersion: Is google or MS doing the reject l= thing? If it's only some small unimportant mail server operators, I may just ignore them.
10:33danvet_: it's fairly regular that we mass-unsubscribe domains because some mailers have a fight over what they're ok with again
10:34emersion: DPA: i haven't tested google/ms
10:34emersion: in my software, i just reject l=
10:34emersion: daniels: is there a way i could help getting ARC setup for the ML? https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/docs/arc_sign.html
10:35emersion: err, we're still on mailman 2…
10:35danvet_: emersion, yeah you'd volunteer to run this show
10:36emersion: yak shaving involves https://docs.mailman3.org/en/latest/migration.html
10:37DPA: emersion: Why? Isn't the l= covered by the dmarc signature? I mean, it boils down to a disable dmarc/dkim for this mail feature. Are you blocking non-dmarc signed mails too?
10:37daniels: yeah, especially the archives having to be split was pretty awesome
10:39daniels: if someone else who loves email more than I do wants to take over, I'd be all for it
10:40emersion: DPA: https://noxxi.de/research/breaking-dkim-on-purpose-and-by-chance.html#hdr2.2
10:40mripard: danvet_: done (for the v3d fix)
10:41emersion: DPA: i consider DKIM with l= to be as good as no DKIM signature
10:45emersion: daniels: actually we can do ARC without upgrading mailman
10:46emersion: just needs to be done in the MTA instead of mailman itself
10:46DPA: emersion: It shouldn't be as much of a problem for non-multipart messages, with the l= covering all of the pre-existing message including the headers though, right?
10:48emersion: DPA: again, it depends. if Content-Type is not signed or signed only once, can overwrite it with a multipart one and overwrite the whole body
10:48emersion: also, if it's HTML, then there are all sort of things you could do
10:49emersion: so in the special case of "Content-Type signed properly and text/plain body", you can only append untrusted text
10:49emersion: but you can still append bad stuff
10:50emersion: there are so many special cases and footguns that rejecting l= outright is less dangerous
10:53mripard: danvet_: there's a scary (to me) merge conflict in drivers/gpu/drm/i915/gem/i915_gem_pages.c, who should I ping?
10:55danvet_: mripard, due to the backmerge?
10:56danvet_: there shouldn't really be anything new, the dma-api rework conflict I think airlied should already have solved
10:56danvet_: so imo look at the current drm-tip and try to match your resolution
10:56danvet_: it probably just moved around a bit between merge points and context
10:56ickle: vmalloc interfaces have been changed
10:56danvet_: otherwise ping ickle here
10:56danvet_: oh I bet on dma-api without looking :-)
10:56mripard: there's some stuff that went through torvalds' tree directly apparently
10:57danvet_: yeah hch is busy
10:57danvet_: and banned on fd.o :-)
11:00DPA: I guess I'll just order a new domain, specifically for sending mails to such MLs, for now.
11:03emersion: you can also use a sub-domain
11:04emersion: name it email-is-broken.<existing domain> :P
11:08DPA: emersion: My DMARC is strict and thus applies to all my subdomains. I don't think it's possible to set a different policy for a specific subdomain.
11:10emersion: DPA: you can use the sp= tag to change a subdomain policy
11:10emersion: eh, maybe not
11:11emersion: DPA: ok, yeah, you can override the DMARC policy per subdomain
11:11MrCooper: danvet_: FWIW, hch is only banned on the dri-devel list (and maybe others), he can still post e.g. to the amd-gfx list; TBH I suspect the dri-devel ban is an overall loss at this point
11:12bnieuwenhuizen: MrCooper: I got the impression from https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7033#note_652386 that Wayland (and hence by extension XWayland) doesn't really support IMMEDIATE semantics, only FIFO and MAILBOX?
11:12DPA: Oh, cool, I didn't know that. This makes everything much easier.
11:12bnieuwenhuizen: I thought it would be worth either stop claiming support for IMMEDIATE or switching the implementation to MAILBOX if we find wayland in the mix?
11:13emersion: bnieuwenhuizen: yeah, that sounds correct…
11:15danvet_: MrCooper, hm I thought it was just fd.o
11:15danvet_: daniels, ^^
11:15danvet_: MrCooper, I mostly get them because I get cc'ed
11:15MrCooper: bnieuwenhuizen: IMMEDIATE with Xwayland ends up more or less as what MAILBOX should be. IIRC MAILBOX itself currently works differently though; if that was changed to always submit frames to Xwayland instead of doing the mailbox behaviour on the client side, then dropping IMMEDIATE might make sense
11:16bnieuwenhuizen: MrCooper: client side = app?
11:16MrCooper: Mesa WSI
11:16bnieuwenhuizen: that never dropped frames IIRC
11:17bnieuwenhuizen: So reason why going for the MAILBOX impl might make sense: we wait for rendering to finish in the app (async thread) as otherwise that gets less than ideal results in the X11 server
11:17bnieuwenhuizen: like with all the queueing for flip even before we know for sure that frame is going to be ready etc.
11:17bnieuwenhuizen: with implicit sync
11:17bnieuwenhuizen: and you get the 5 images in the WSI :P
11:21MrCooper: how does MAILBOX set the target MSC?
11:22bnieuwenhuizen: but without XCB_PRESENT_OPTION_ASYNC (compared to IMMEDIATE)
11:24MrCooper: right, that's a problem
11:25MrCooper: it means Xwayland picks the first available buffer, then waits for the Wayland frame callback
11:25MrCooper: not really mailbox
11:25bnieuwenhuizen: yeah ...
11:26bnieuwenhuizen: at least by waiting on the WSI side we got the first available buffer correct wrt implicit sync
11:26bnieuwenhuizen: but you still get 1 frame of latency due to queueing in KMS at least
11:26MrCooper: right, though I'd argue that's really the Wayland compositor's job :)
11:27bnieuwenhuizen: I honestly think we should just move to explicit sync and make that separation clear :)
11:27MrCooper: wait, actually since MSC has always passed already, Xwayland might be doing the right thing
11:28MrCooper: MSC 0
11:28bnieuwenhuizen: well, it is still eager and you can't override a flip that is already queued in KMS
11:28bnieuwenhuizen: so you are still losing that frame of latency
11:28MrCooper: that's definitely the Wayland compositor's job
11:29MrCooper: should be possible to get much lower
11:30bnieuwenhuizen: well for Xwayland to be doing the right thing it should also send over a next frame before the frame callback for the previous one is received no?
11:31bnieuwenhuizen: otherwise the wayland compositor never gets the chance to schedule a newer image to the flip
11:32MrCooper: I just confirmed MSC 0 without XCB_PRESENT_OPTION_ASYNC doesn't work as intended for MAILBOX (with Xwayland; it's probably the best you can do with Xorg, without tearing)
11:32MrCooper: right, exactly
11:33ickle: mripard: should be resolved
11:34mripard: ickle: awesome, thanks!
11:34MrCooper: bnieuwenhuizen: bottom line, dropping IMMEDIATE for Xwayland might make sense if MAILBOX sets XCB_PRESENT_OPTION_ASYNC instead
11:35bnieuwenhuizen: why ASYNC?
11:35MrCooper: that's what allows frames to be sent independently from frame callbacks
11:35bnieuwenhuizen: I thought that results in tearing for non Xwayland which is not what we want
11:36MrCooper: right, only for Xwayland
11:36bnieuwenhuizen: or I guess we just have differences in mailbox between xwayland and normal X
12:08tzimmermann: danvet_, your comment on leaking the fb address was not meant to be fixed in the patchset (?)
12:12danvet_: tzimmermann, which patch set?
12:14tzimmermann: danvet_, i mean the discussion at https://patchwork.freedesktop.org/patch/395923/?series=80038&rev=6
12:16danvet_: tzimmermann, I think if you don't you can blow up
12:16danvet_: and it's a tiny change, just add && map.is_iomem to the condition
12:16tzimmermann: well, ok then
12:17danvet_: one annoyance is also that fb core uses that for it's own mmap
12:17danvet_: but I think for generic fbdev emulation we always go through the gem mmap function
12:21danvet_: tzimmermann, I guess strictly speaking it's fallout from using fbdev helpers for iomem in general
12:21danvet_: but since your patch set is fixing that fallout, imo should be included
12:21danvet_: if you want split it out into a separate patch, but imo not needed
12:22tzimmermann: i see when i find time
12:22tzimmermann: it's no big deal
12:49haasn: How surprised should I be that eglExportDMABUFImageQueryMESA is returning DRMDRM_FORMAT_MOD_INVALID as the modifiers?
12:49haasn: I'd have expected DRM_FORMAT_MOD_NONE or something like that
12:50haasn: (this being on amdgpu)
12:52bnieuwenhuizen: haasn: not surprised at all
12:52haasn: So should I treat that function returning _INVALID and _NONE as equivalent (i.e. no modifiers needed)?
12:53bnieuwenhuizen: well, ONE has this issue that it is aliased with _LINEAR
12:53bnieuwenhuizen: so better treat _NONE as a mistake that nobody will use, and treat its value as _LINEAR
12:55haasn: good point
12:55haasn: I somehow missed that
12:55bnieuwenhuizen: we should probably add some documentation about that in drm_fourcc.h ...
13:14pq: I didn't even realize DRM_FORMAT_MOD_NONE was actually defined.
13:14emersion: it's even in the list of vendors ><
13:17pq: there are three uses of it in the kernel, too
13:17pq: all in vc4 driver
13:17emersion: haasn: https://lists.freedesktop.org/archives/dri-devel/2020-October/284158.html
14:18zmike: anyone have any tips for forcing a DEVICE_LOST error during a shader?
14:18zmike: nir is too good at optimizing out all my infinite loops
14:22bnieuwenhuizen: zmike: something stupid like finding the second even prime?
14:25bnieuwenhuizen: probably just even taking the sum from 1 to INT_MAX-1 is enough to not be optimized
14:25bnieuwenhuizen: just make sure you output the result somewhere?
14:26zmike: ah, that's a good one
14:26zmike: thanks bnieuwenhuizen
14:41jekstrand: zmike: "for (uint i = 0; i < 10; i += u_zero)" where u_zero is a uniform that conatins zero.
14:42jekstrand: And do something in the loop you use
14:44zmike: hm will try this, a 32bit int summation wasn't succeeding at failing
14:45zmike: are int64 types explicitly prohibited as loop iterators? I've been trying to find that in a glsl spec, but it just says they're "fully supported"
14:45jekstrand: zmike: Why are you trying to force DEVICE_LOST?
14:45zmike: to test the callback for resetting the device
14:45jekstrand: zmike: They should be supported.
14:45zmike: jekstrand: they crash atm
14:45zmike: in loop_analysis.cpp
14:46zmike: the first check is for 32bit ints and then assumes that if that fails it must be a float/double
14:46jekstrand: zmike: That's not good. Also, not surprising.
14:46karolherbst: jekstrand: btw, I found a bug inside lower_cl_images_to_tex: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7241/diffs?commit_id=c388a9f744b94330208e4ad26367924a507c93b0
14:46zmike: then later int64/uint64 is just missing from the switch
14:46jekstrand: zmike: Crashing in GLSL IR or NIR?
14:46zmike: I can add this
14:46karolherbst: and I think array coordinates are still broken
14:46zmike: I just wasn't able to find the spec saying one way or the other
14:47jekstrand: karolherbst: rb
14:47karolherbst: array indices have to be integers, right?
14:48jekstrand: karolherbst: Yes
14:48karolherbst: right.. that might give a hint why float coords are broken with array images
14:48jekstrand: karolherbst: I wouldn't be surprised if sample() on an array with integer coordinates is broken. :)
14:48jekstrand: Because we have to convert all but the last one to float and add 0.5.
14:48karolherbst: ahh, right
14:48karolherbst: I remember this part
14:48karolherbst: will take a look later
14:50karolherbst: jekstrand: anyway, testing with the CTS I am now confident enough to say that the broken luxmark rendering isn't caused by broken image support :)
14:50karolherbst: I just suspect we still have a bunch of random issues
14:50karolherbst: or just CL precision problems
14:50jekstrand: karolherbst: Yeah. Did you see my two memcpy fixes over the weekend? :-)
14:51jekstrand: karolherbst: I wouldn't at all be surprised if you're hitting one of those.
14:51karolherbst: yeah, didn't try them out
14:51karolherbst: but yeah
14:51karolherbst: they could help
14:51karolherbst: I also added that struct size thing, but that didn't change a thing
14:51zmike: jekstrand: that loop also manages to not lose the device :/
14:51zmike: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/7316 for 64bit iterator fix
14:52karolherbst: all images tests are passing now, except a few ones crashing because I don't properly support 8 bit in nouveau
14:52karolherbst: but yeah, overall it's working now
14:54jekstrand: karolherbst: Woo!
14:54karolherbst: mh, though, samplerless reads are a bit broken, and I am not sure why yet
14:55karolherbst: but I think the CTS just complains that stuff is a bit different
14:55karolherbst: comparing to samplerful reads
14:55karolherbst: oh well.. 1.2 features anyway
15:09karolherbst: ehh.. okay, seems like my kernel traps with the samplerless reads tests.. uff
15:14karolherbst: ahh nice, apitrace broke for big endian between 7.1 and 8.0
15:27danvet_: tzimmermann, so what's the verdict, should I split the constification patch up per-driver?
15:39daniels: danvet_: hmm I thought it was all of fd.o too - I remember editing Postfix rules - but I can't see it atm
15:42sravn: danvet_: add const to the example in another patch is fine
15:44sravn: danvet_, tzimmermann - personally I prefer that the patch just goes in drm-misc-next ad mripard (and I) already acked it. Then it is done and we can move forward from there. It is not like the patch breaks the workd, it only makes it harder to mis-use the drm infrastructure
15:44karolherbst: snappy broke be :/
15:47daniels: emersion: cool that we can do ARC in the MTA. :) tbh our Postfix setup hasn't been meaningfully changed or brought up to date since ... about 2007? I think the only things since then have been setting up TLS and splitting @x.org out as a very separate namespace
15:47emersion: yeah, i can understand that
15:50kubast2: Is there some kind of enivormental variable
15:50kubast2: to set a custom llvmpipe vendor id
15:51kubast2: I have an application which wants to know the vendor id of llvmpipe and read out 0000 and shutsdown shortly after
15:56pepp: kubast2: maybe try force_gl_vendor ?
16:08tzimmermann: danvet_, i do backports of drm patches and some like this give me nightmares. but OTOH, maybe just commit what you have
16:11danvet_: tzimmermann, I dont think you should backport this one
16:12danvet_: I've looked carefully, but with stuff like amdgpu mangling drm_driver I might have missed something
16:12zmike: jekstrand: any other ideas for triggering a DEVICE_LOST from a shader test?
16:13danvet_: tzimmermann, or do you stuff like only backport a specific driver, not anything else?
16:16tzimmermann: danvet_, it depends
16:16tzimmermann: but go ahead and merge it
16:24AI6K: Is there a channel specific to playing around w/ Vulkan on the Raspberry Pi? Or is the best way to take a look at the demo code in the Git repo?
16:30nroberts: AI6K: you could try #videocore. the vulkan pi driver devs are in there
16:30pepp: daniels: hi! do you think you could take a look at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5096 (EGL_EXT_protected_surface) this week?
16:35AI6K: Maybe I need to take a step back and ask a more pertinent question. I want to start learning about creating simple demos, maybe like you used to see from the Demoscene a few decades ago, like Second Reality, but on the Raspberry Pi. My apologies for spamming this channel.
16:42jekstrand: zmike: Is infinite looping not working for you?
16:45AndrewR: karolherbst, so, you nearly fixed it all (OpenCL images on nvc0) :} Thanks a lot
16:47zmike: jekstrand: doesn't seem to be, no
16:51anholt: AI6K: there shouldn't really be anything raspberry pi specific for that, assuming you're on a pi4 and can build Mesa yourself (I don't know that raspbian ships the driver yet)
16:58seanpaul: emersion: did you manage to get vrr working on amd?
17:04emersion: seanpaul: yes!
17:04emersion: seanpaul: i used https://github.com/emersion/drm_monitor to make sure the timings change appropriately
17:05seanpaul: emersion: ah cool, thanks for confirming! had a couple questions internally here about vrr support and saw some emails from you about it :)
17:05emersion: it's also implemented in sway (and released in sway 1.5)
17:06emersion: yeah, VRR can be tricky, especially how to handle flickering screens
17:07seanpaul: awesome, sounds like there's fun ahead then
17:15emersion: the current status is that we (user-space) expect kernel drivers to handle this
17:15emersion: by implementing a slew rate for refresh rate changes
17:15emersion: but we still get flickering screens, at least on amdgpu
17:15emersion: (note, just with *some* screens, not all)
17:15emersion: (mine works fine for instance)
18:02kreyren: I found this IRC on https://docs.mesa3d.org/lists.html is this a good place to get more relevant informations to https://gitlab.freedesktop.org/mesa/mesa/-/issues/3694 because i am impatient and trying to fix it myself?~
18:04kreyren: currently trying to figure out if it's mesa bug or game bug assuming https://youtu.be/L9QritXkozY?t=114
18:42zmike: jekstrand: somehow it's not actually looping infinitely even though the shader nir definitely looks like it should be
18:42zmike: it breaks out after ~10s on iris and ~1-2 on zink
18:44jekstrand: zmike: That really should ge giving you a DEVICE_LOST
18:45jekstrand: zmike: Are you seeing any reset messages on dmesg?
18:56airlied: jekstrand: i think kernel hang detect is broken
18:56airlied: or wierd
18:57airlied: danvet_: may knownmore
18:57danvet_: which gen/platform?
18:57danvet_: and yes as long as you can still preempt, current i915 doesn't kill you and declare you dead
18:58airlied: gen11 i think zmike has
18:58danvet_: but it varies what can preempt, and whether mid-thread/shaders or just between 3dprim from the batch
18:58danvet_: I think that can preempt mid-shader
18:58danvet_: iirc for gen12 or so they lost that for $reasons
18:59danvet_: also kernel version
18:59danvet_: but not sure you can go back far enough and still have working gen11
19:00danvet_: but if the shader does eventually stop it's not that
19:00danvet_: or what does "break out" mean
19:01danvet_: I think you also don't get the loud message (by default) in dmesg when we just do an engine reset
19:02ickle: you do
19:02danvet_:should probably go back to dinner and let people with working knowledge of the code speak :-)
19:03ickle: you've got to the root of it; what does break out mean
19:11airlied: also not sure if a device lost is approoriste if the shader is exited but the device lives
19:11airlied: but i cant remeber the api semantics
19:11airlied: jekstrand: does loop umroll also boow.up your shader?
19:14jekstrand: airlied: ?
19:20airlied: jekstrand: just wondering if we unroll a loop that calls a fn that geta inlined
19:21bnieuwenhuizen: depends on the size of the body including inlined function
19:21jekstrand: airlied: context?
19:21jekstrand: airlied: Generally, loop unrolling happens after inlining
19:21airlied: jekstrand: cl shader that gets big
19:21airlied: and ooms
19:21jekstrand: airlied: No, it OOMS in the initial function inline
19:22airlied: ah cool
19:22airlied: jekstrand: any idea how useful the spirv inline hints are?
19:22airlied: ive started hookinf them up
19:22airlied: for llvmpipe
19:23jekstrand: airlied: Today, we inline everything
19:23jekstrand: airlied: If we wanted to stop doing that... I don't know. I imagine they're about as useful as they are to C compilers.
19:24airlied: yeah my branch is not inlining
19:24jekstrand: Have fun with that!
19:24airlied: but i need to write a function cleanuo pass to discard dead fns
19:24jekstrand: I'm sure lots of optimizations are busted if there are calls
19:25airlied: it makes it through to llvmpipe at least
19:25airlied: but cleaning up dead fns is necessay
20:32danvet_: emersion, just noticed you're comment on newsy fighting the good fight
20:32danvet_: it's kinda impressive how like 80% in the comments is just bonkers
20:33emersion: yeah, i should just stop trying ;_;
20:36zmike: jekstrand: sorry, I've been in and out this afternoon
20:36zmike: no reset messages or anything
20:38zmike: I used to get a DEVICE_LOST from spec@arb_shader_storage_buffer_object@execution@ssbo-atomiccompswap-int in zink, but somehow after either mesa or kernel updates I'm no longer getting them
20:38zmike: and I can't seem to trigger them no matter what I try :/
20:38zmike: makes testing a gallium device reset callback challenging
20:38airlied: danvet_: all the comments in most sites are bonkers
20:43danvet_: zmike, tried isolating which upgrade changed this?
20:43danvet_: could be either kernel or maybe also mesa
20:44danvet_: airlied, popular topics like this seem to be worth
20:44danvet_: still only a handful of people with some clue, but more clueless to drown them out
20:46airlied: danvet_: you should have said it on a monetised blog :-P
20:48danvet_: airlied, well phoronix would still have copypasted and stolen all the adclicks
20:48danvet_: as probably like 5$ in total
20:51ccr: uhh .. 245 comments.
20:54karolherbst: wondering if I should throw some more comments into it or not :D
20:54airlied: you should always throw more tyures onto a tyre fire
20:55zmike: danvet_: not particularly since I haven't paid attention to it for a couple months now, so it could've been just about anything :/
20:55airlied: I was consiering going full blog post to amp it up
20:55karolherbst: airlied: ehh, the replies I got are quite stupid
20:55danvet_: airlied, do it
20:55danvet_: just .... DO IT
20:55karolherbst: somebody tells me, that preventing applications from grabbing input/recording screen is bad, because it treats people as children
20:56karolherbst: or rather "is just to protect them from themselves"
20:56karolherbst: I'd be glad if such people never decide anything security sensitive :D
20:56karolherbst: sadly, those do
20:58airlied: danvet_: just register isxorgabandoned.com
20:58karolherbst: Xorg countdown
20:58danvet_: also need whenwillX12ship.com and just redirect to mutter or whatever
20:58karolherbst: like https://pythonclock.org/
20:58karolherbst: and just put 0s
20:58danvet_: karolherbst, I don't think that'll happen
20:59karolherbst: I know you want to do it
20:59danvet_: I guess in 1-2 years someone's going to be fed up, filter xwayland out of the xserver repo
20:59karolherbst: just do it
20:59danvet_: and we'll ship that thing for another few decades or so
20:59airlied: danvet_: MrCooper is already workong on that
20:59karolherbst: that's already decided :p
20:59danvet_: I thought the plan is to trick emersion into doing it
21:00airlied: < MrCooper> xwayland release branches with other DDXen dropped
21:00airlied: I'm assuming we'd just filter to do that
21:00airlied: inside the xserver repo
21:00karolherbst: I think we can keep things like Xvfb? dunno
21:00danvet_: make it the official xorg-xserver 1.21 release
21:00karolherbst: dropping everything sounds a bit drastic
21:00danvet_: just to rub it it
21:00karolherbst: if somebody does it and nobody disagrees, I'd be fine with that
21:01karolherbst: danvet_: +1
21:01danvet_: karolherbst, there's no wnest or similar yet?
21:01karolherbst: no clue
21:01danvet_: or fire up weston on vkms.ko with xwayland
21:01karolherbst: sounds more painful than just running Xvfb
21:01danvet_: maybe we get an outreachy this winter to add configfs support to vkms
21:02danvet_: so you can have all the fake compositor instances you need
21:02airlied: karolherbst: no reason to ship and updated Xvfb
21:02airlied: it would still be in the Xorg package
21:02karolherbst: well, we need a simple way of being able to do headless GL
21:02emersion: karolherbst: is this what you want? https://github.com/Hjdskes/cage
21:02airlied: the idea behind xwayland release is you would just get xwayland
21:02karolherbst: airlied: ahh, so X is 1.20 for eternity, and only xwayland gets releases?
21:02airlied: karolherbst: yes
21:03airlied: until someone volunteers to RM X.org
21:03karolherbst: emersion: more painful than just running Xvfb
21:03emersion: karolherbst: how so?
21:03karolherbst: need to build it
21:03karolherbst: getting Xvfb running is literally two commands
21:03karolherbst: one if it's already installed
21:04emersion: cage is in some repos
21:04emersion: oh, and i forget that weston has a kiosk mode now too
21:04danvet_: yeah I'd expect every semi-competent compositor will have something like that for testing
21:05danvet_: quick search says kwaylandtest is, didn't look further for the others
21:05emersion: just running in nested mode is supported by almost all wayland compositors i know of
21:05karolherbst: emersion: but then you already need something
21:05danvet_: well you need to put your turtles all the way down on something
21:05karolherbst: I meant to run it on a server
21:05karolherbst: worst case, no GPU
21:05danvet_: aka s390
21:06danvet_: if rh engineers come up with something funny, it's always s390
21:06karolherbst: hey.. still planning to CI llvmpipe on that, but god that will be painful
21:06danvet_: especially post ibm :-P
21:43karolherbst: airlied: interested? https://github.com/llvm/llvm-project/commit/89808ce7343b22586bfd0d3fafddcdbba94fbcbb :p
21:45airlied: karolherbst: lols, won't be as fast as llvmpipe :-P
21:45karolherbst: of course not
23:43airlied: ah yes execution mask and function calling interactions are fun