00:22imirkin_: cmarcelo: does intel not support variable workgroup sizes? seems like https://cgit.freedesktop.org/mesa/mesa/commit/?id=ff5b74ef32ea0ccff265064017f8168a4b328a5a would be problematic in that case.
00:24imirkin_: indeed, looks like ARB_compute_variable_group_size is unsupported on intel. nevermind.
00:27cmarcelo: imirkin_: yep, it still doesn't. there's an open MR to implement it but got a bit stale...
00:28imirkin_: yeah, that's fine. it'll have to consider that, i guess.
00:28imirkin_: could probably do like if == 0, then return 1024 or whatever
00:30cmarcelo: I added a note to the ARB_compute_variable_group_size MR to make sure we don't forget it :)
00:51ngcortes: heads up, the public mesa ci results site will be down momentarily for an upgrade
00:54Kayden: it's kind of crazy that the MR for that was posted 7 months ago
00:54Kayden: and no activity in 4-5 months
01:00anarsoul: out of curiosity, does anyone have a theory why Mali4x0 specifies a register to take gl_FragColor from 4 times in render state?
01:00anarsoul: that's not 4 components
01:52mareko: okias[m]: I'm not aware of any ARM users of radeonsi
02:06MaxLeiter: I'm working on packaging mesa for a unix-like OS with swrast, and when others install mesa (I used DESTDIR to package) with the LFS glxgears patch, glxgears/glxinfo report: Error: couldn't get an RGB, Double-buffered visual
02:06imirkin: try it with LIBGL_DEBUG=verbose
03:07anholt_: anarsoul: it supports 4 render targets, and that lets you do gl_FragColor vs gl_FragData?
03:34anarsoul: anholt_: I need to change all them at once in order for shaders to work
03:34anarsoul: if I leave out one of them then result is weird
03:36anarsoul: also it supports only up to 3 render targets
06:44tomeu: mareko: okias[m]: I heard of people using radeonsi on ampere workstations
08:08danvet: j4ni, I think if you can coerce seanpaul into acking drm_WARN we're hopefully good enough
08:08danvet: otherwise not seeing anyone with opinions about how drm driver debug output should happen
08:32MrCooper: Venemo: please use Marge for merging MRs
08:32Venemo: MrCooper: care to elaborate?
08:33MrCooper: what's unclear?
08:35Venemo: why do I need Marge?
08:37Venemo: what's wrong with the "Merge when pipeline succeeds" button?
08:41MrCooper: see e.g. https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3402#note_389654
08:41gitbot: Mesa issue (Merge request) 3402 in mesa "panfrost: Fix naming conflict between bifrost & midgard compiler backends" [Android, Panfrost, Merged]
08:41MrCooper: there were also mesa-dev list posts about it
08:42Venemo: I assigned the next one to the marge bot
08:42MrCooper: also, if you merge manually and it interferes with Marge, she gets upset ;)
08:54mlankhorst_: danvet: hmm, time to open drm-misc-next-fixes I suppose?
08:56airlied: mlankhorst_: yup I think it should be
09:00mlankhorst_: pushing :)
09:00mlankhorst_: drm-misc-next-fixes is now open!
09:21j4ni: seanpaul: may I have your ack on http://firstname.lastname@example.org please?
09:23j4ni: mlankhorst_: mripard: your acks would be appreciated as well on ^, can I merge via a topic branch so that I can start applying changes in i915 immediately?
09:29mripard: j4ni: you can add mine
09:39j4ni: mripard: thanks!
10:38mlankhorst_: j4ni: irc ack enough?
10:42dj-death: oh noes, gitlab times out
10:50j4ni: mlankhorst_: sure, thanks a lot!
12:01GreyXor: Hi, someone can help me to build mesa ?
12:01GreyXor: i need to try an branch to debug my hardware
12:09daniels: Venemo: whenever you rebase a tree, a CI job will be run. Marge takes each approved MR into a queue, rebasing them one-by-one and then pushing when their CI has succeeded. without Marge, you get a thundering herd: people rebase (CI runs), then can't merge because someone else's MR landed first, so they rebase again (another CI run), etc etc.
12:09daniels: the resulting contention on CI means that everyone's pipelines take longer, meaning that they rebase more often, making the contention worse ...
12:09Venemo: daniels: understood. yes, that makes good sense :)
12:10daniels: a good counterpoint is 'so why do we have a big button at the top saying "merge"?'
12:10daniels: to which my preferred answer is 'only allow Marge and no-one else to merge'
12:11Venemo: can the button be changed to do the right thing?
12:24daniels: possibly at some point in the future but not soon
18:15imirkin_: is there an easy way to do the equivalent of "dmesg -w" when you have a version of dmesg that's too old?
18:15imirkin_: like tailing /dev/kmsg or something?
18:16ickle: cat /dev/kmsg
18:17imirkin_: cat: /dev/kmsg: Invalid argument
18:21ickle: my reading of devkmsg_read() says that is output buffer too small for message packet
18:21ickle: assuming it got that far
18:22imirkin_: sounds like "no", then, for easy ways
18:23turol: cat /dev/kmsg works for me
18:23turol: you might need to sysctl kernel.dmesg_restrict = 0
18:23kisak:waves to pipeline 100000 as it goes by
18:23imirkin_: turol: already 0
18:23ickle: restrict should be EPERM
18:23Kayden: but did pipeline 99999 do critical damage to the CI? :)
18:23imirkin_: this is probably not _the_ most recent kernel
18:24imirkin_: let's just say it matches the version of dmesg which doesn't have "-w" support :)
18:25linkmauve: Speaking of kmsg, how could I increase its buffer size to see what was printed out at early boot?
18:25imirkin_: there's a kernel cmdline thing
18:25imirkin_: or osmething like that
18:25linkmauve: Thanks. :)
18:26imirkin_: i was close.
18:26imirkin_: thanks to the NLP built into the kernel, it should be able to work things like that out :)
18:27imirkin_: boo - only K/M/G suffixes supported. so if you want 1TB of your ram to go to the kernel log buffer, you'll have to type it out in G
18:27dcbaker: PSA: Mesa 20.0 branchpoint is schedules for 2020/01/29, the release milestone is https://gitlab.freedesktop.org/mesa/mesa/-/milestones/9
18:28Kayden: thanks for the heads up!
18:28imirkin_: and more relevantly, apparently n has to be a power of 2, so 100M -> 128M
18:28imirkin_: or whatever
19:22mattst88: MR from someone that doesn't have commit access
19:23mattst88: I review, add my tag, force push to his/her branch and assign to Marge-Bot
19:23mattst88: what stops that person from pushing a bunch of crap to their branch after I've assigned to Marge and getting that committed without review?
19:24airlied: nothing, but at that point they've already owned all your CI infrastructure :-P
19:24mattst88: does Marge automatically unassign itself when the author pushes more stuff to that branch?
19:25mattst88: (I'm looking at https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3231 as a concrete example)
19:25gitbot: Mesa issue (Merge request) 3231 in mesa "Do not require libdrm for DRI2 on hurd" [Meson, Opened]
19:27anholt_: mattst88: a re-push unassigns from marge
19:27mattst88: okay, cool
19:28mattst88: it looks like that didn't happen in this case -- perhaps because only the commit message changed
19:30anholt_: mattst88: my bet would be that marge is off testing other stuff and hasn't swept the MR list again
19:30kisak: marge's attention might be elsewhere, could something like that be delayed until it's the current task in the queue?
19:30anholt_: (it's very single threaded)
19:30mattst88: ah, I see
19:53Kayden: is there a way to see what marge is doing?
19:54Kayden: because sometimes you assign it and nothing happens for 30+ minutes
19:54Kayden: and so you're kind of left wondering ... is marge around and online? has she just not gotten to that request yet? or is it never going to happen?
19:55anholt_: Kayden: nope, it doesn't put up any web interface or anything, just the kube logs
19:55Kayden: the other day I assumed marge was still broken due to the gitlab updates, and unassigned marge, rebased, and merge when pipeline succeeds...then marge came back and cancelled it all, and then said "somebody did something, nooo" and bailed
19:56Kayden: so reassign to marge, and finally happened - would've happened faster if I just left it, but... :)
19:56anholt_: well, I guess you could watch https://gitlab.freedesktop.org/marge-bot
19:56Kayden: ah! true
19:56Kayden: yeah, that at least answers the "has marge been around today" question :)
19:59kisak: !eightball are we going to see an overloaded CI workload next wednesday
20:02kisak: mattst88: I wonder if some of the merge requests you queued up would have landed by now if you had cancelled the CI jobs on the pull requests that were going to get fast forwarded by marge and tested then. there's a throwaway iteration in there from adjusting the commit messages
20:03mattst88: kisak: your guess is probably better than mine
20:04mattst88: kisak: maybe I should just make sure that the MRs I'm assigning to Marge rebase cleanly and /don't/ rebase/push myself?
20:04mattst88: or does CI still trigger if just the commit message is updated? that would be... stupid.
20:05kisak: it looked like CI was doing a fresh batch on commit message change
20:05mattst88: sigh :(
20:06kisak: in the simple case, Marge picks up the assignment, rebases, and the throwaway step gets auto-cancelled
20:06Kayden: yeah, it would be nice if it didn't re-trigger when the only change is the commit message
20:06kisak: but when 2 are assigned to marge at the same time, the second queued pull request pulls CI time until marge gets to it and rebases
20:07Kayden: (queue the mention that not adding R-b type tags in the commit messages would also fix that)
20:07mattst88: yeah, I suspect I totally clogged up the pipes by reviewing/rebasing/pushing a bunch of outstanding MRs and assigning to marge
20:09Kayden: glad to see that happen regardless :)
20:09mattst88: alternatively... people could spread the load a bit more (both in review/merging others commits and CI) :)
20:09mattst88: poor Samuel with his four Hurd patches, all clogging CI
20:10mattst88: really should have just been one MR I suppose
20:27capOM: Hi, is there an equivalent to https://mesamatrix.net/ but for EGL ? I would like to know how mature is EGL in Mesa, thx
20:29kisak: maybe it would make sense to call for everything that's going into mesa 20.0 to land 48 hours early, so that the CI work gets spread out and just-in-time projects can land without hassle
20:30kisak: (as a friendly reminder)
20:31imirkin_: capOM: EGL is pretty much identical across (non-ancient) drivers
20:31imirkin_: hrmph, i965 is missing EGL 1.5. surprising.
20:41capOM: imirkin_: Thx, would be great to reflect that in a matrix
20:43imirkin_: well, mesamatrix.net is just a prettifier for features.txt
20:44imirkin_: i tried my own attempt at this based on actual data, but getting people to submit data is harder than pulling their teeth over the internet.
20:45degasus: imirkin_: I'm really sad that this page got outdated that hard. It was the best source for this kind of information
20:46imirkin_: i gave up maintaining it
20:46imirkin_: anyone (in the mesa group) can push to it though
20:46anarsoul: ivb is at 4.5
20:46anarsoul: for quite a while
20:46degasus: understandable. I just wanted to say "thank you"
20:47anarsoul: looks like I'm wrong
20:47imirkin_: yw :)
20:47anarsoul: it's indeed at 4.2
20:47imirkin_: anarsoul: as you can see at the top, this is for mesa 17.2
20:47imirkin_: i have data as recently as 18.0
20:47imirkin_: but only for nouveau
20:47imirkin_: (coincidence, i'm sure)
20:47anarsoul: imirkin_: ivb is ~8yo
20:48anarsoul: if not older
20:48imirkin_: ok, but mesa didn't always have pre-release hw support for everything
20:48imirkin_: in fact, there was a time when GL 4 wasn't fully supported at the mesa level, believe it or not
20:49imirkin_: for example.
20:49imirkin_:started hacking on mesa just before GL 3.2 support was added
20:50imirkin_: i should probably do a "final" round of data collection
20:50imirkin_: for 20.0 or something
20:52anarsoul: ha, looks like my first commit in mesa was in 2011, but it was pretty minor and I had 8 years break afterwards
21:05robclark: imirkin_: I suppose w/ CI running stuff on real hw.. it would be nearly possible to update glxinfo automagically.. supposedly there is a way to setup scheduled CI runs (like, run glxinfo every thing)..
21:06imirkin_: happy to assist in explaining how my thing works to the next person :)
21:07anholt_: robclark: with drm-shim, you don't even need hw
21:07imirkin_: it's a lot of fixed, data-driven js ... just need to massage some of the inputs
21:10robclark: oh, good point on drm-shim.. I guess that would need some periodic maintenance (ie. like when there is a feature that is only exposed depending on kernel version)
21:11anholt_: yeah, but it's usually of the form "case DRIVER_GETPARAM_HAS_NEW_THING: return 1"
21:24Kayden: i965 doesn't have EGL 1.5 because of OpenCL interop, IIRC.
21:24MaxLeiter: LIBGL_DEBUG didnt work, do I need to compile with a flag imirkin?
21:24MaxLeiter: Nothing new printed
21:24imirkin_: MaxLeiter: no, that should just work
21:24imirkin_: if you're using libGL, that is
21:43MaxLeiter: imirkin_ I am
21:44imirkin_: MaxLeiter: LIBGL_DEBUG=verbose glxinfo > /dev/null
21:44imirkin_: what does that print?
22:29MaxLeiter: iPhone:~ root# DISPLAY=:1 LIBGL_DEBUG=verbose glxinfo > /dev/null
22:29MaxLeiter: Error: couldn't find RGB GLX visual or fbconfig
22:31imirkin_: that's it?
22:31MaxLeiter: oh hm imirkin_
22:31MaxLeiter: it seems DESTDIR didnt install swrast.so
22:32MaxLeiter: any clue if theres something special I neeed to do for packaging?
22:32imirkin_: probably. look at how others do it? no idea how this stuff all works with meson.
22:33imirkin_: iirc the point of DESTDIR is that you're the one that has to move it there.
22:33imirkin_: but i'm no authority on this stuff.
22:34MaxLeiter: nah DESTDIR is just where to install the files, and now I need to figure out how to see how others did it
22:34MaxLeiter: oh huh, seems it didnt build swrast last time
22:35imirkin_: anyways, sounds like glxinfo isn't the issue ;)
23:15endrift: Are integer textures just slow in i965?
23:16endrift: I'm seeing a lot of performance issues when I use them on Intel
23:16endrift: (RGBA8I specifically)
23:17imirkin_: any particular flavor of i965?
23:18imirkin_: like ivb with texture borders?
23:18imirkin_: (or does i965 even do those fallbacks?)
23:18endrift: gen9.5, no borders
23:18endrift: I'm on coffeelake
23:18endrift: I think that's 9.5
23:20endrift: also getting a few warnings for Integer fast clear not enabled for (MESA_FORMAT_RGBA_SINT8)
23:20endrift: Which I assume is a driver limitation
23:21imirkin_: hardware, i'd assume
23:22endrift: Is there an intel-specific channel that would know better?
23:23endrift: (also I guess by driver limitation I meant "either unimplemented or can't be implemented due to hardware")
23:24imirkin_: although tons of overlap between the people
23:26endrift: I figured
23:27endrift: hm, gles3 doesn't seem to have any 16-bit integer textures
23:27imirkin_: EXT_texture_rg probably
23:28endrift: oh, rg
23:28endrift: those are listed here but I don't know if they're core in gles3
23:28imirkin_: they're not core
23:28imirkin_: hm. they MIGTH be core.
23:28imirkin_: ugh, sorry. i used to remember this stuff. but i clearly don't anymore
23:29imirkin_: GLES3 includes rg.
23:29HdkR: RG8 is core yes
23:29imirkin_: there's also GL_EXT_texture_norm16 for R16 & co
23:29imirkin_: but i thought integer textures should be there in GLES3 directly.
23:30endrift: I'll see if rg8 is any faster
23:30endrift: I'm only using a few bits of each channel
23:30endrift: 2, 3, 2, 1 respectively I think
23:30imirkin_: just do R8 :)
23:31endrift: oh wait I'm wrong
23:32endrift: 2, 4, 5, 1
23:33imirkin_: there really should be a R16UI on GLES3
23:33imirkin_: are you *sure* it's not?
23:33imirkin_: i see it in the gles3 spec
23:34imirkin_: (numbered) page 129
23:34endrift: by 16-bit I meant 16bpp not 16bpc
23:34imirkin_: RGBA4 :p
23:34endrift: not integer
23:34endrift: honestly I'd love 565
23:34imirkin_: well, R16UI and RG8UI are also both supported.
23:35endrift: I'll try those
23:35endrift: hopefully they'll be faster
23:35endrift: I just don't want to hit slow paths even if I am processing less data
23:35imirkin_: yeah =/
23:36endrift: I suspect R16UI is like 4 slow paths in one--16bpc, integer, unsigned, one channel
23:36endrift: *one color channel
23:36endrift: this also needs to work on TX1 with Nouveau :x
23:38imirkin_: nouveau is fairly standards compliant ... passes the GL45 CTS
23:38imirkin_: (just not with all the tests run in one go... sigh...)
23:39imirkin_: if you find bugs, please report them
23:40endrift: of course