ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
warpme has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
warpme has quit [Ping timeout: 480 seconds]
simon-perretta-img has quit [Read error: Connection reset by peer]
warpme has joined #dri-devel
pcercuei has quit [Quit: dodo]
simon-perretta-img has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
epoch101 has quit [Ping timeout: 480 seconds]
LeviYun has joined #dri-devel
warpme has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
flynnjiang has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
yuq825 has joined #dri-devel
mattst88 has quit [Quit: Lost terminal]
warpme has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
mattst88 has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
Dark-Show has quit [Quit: Leaving]
alane_ has quit []
LeviYun has joined #dri-devel
alane has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
LeviYun has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
Company has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
LeviYun has joined #dri-devel
epoch101 has joined #dri-devel
warpme has joined #dri-devel
nerdopolis has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
warpme has quit [Ping timeout: 480 seconds]
bmodem has joined #dri-devel
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #dri-devel
phire has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
LeviYun has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
glennk has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
Duke`` has joined #dri-devel
fab has joined #dri-devel
fab has quit []
fab has joined #dri-devel
phire has joined #dri-devel
heat has joined #dri-devel
warpme has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
LeviYun has joined #dri-devel
warpme has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
warpme has quit [Ping timeout: 480 seconds]
bmodem has quit [Ping timeout: 480 seconds]
kzd has quit [Ping timeout: 480 seconds]
Duke`` has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
flynnjiang1 has joined #dri-devel
flynnjiang has quit [Remote host closed the connection]
warpme has quit [Ping timeout: 480 seconds]
phire_ has joined #dri-devel
phire is now known as Guest550
phire_ is now known as phire
LeviYun has joined #dri-devel
Guest550 has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
dakr has quit [Quit: ZNC 1.9.0 - https://znc.in]
dakr has joined #dri-devel
simon-perretta-img has quit [Read error: Connection reset by peer]
warpme has joined #dri-devel
simon-perretta-img has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
tzimmermann has joined #dri-devel
pjakobsson has quit [Remote host closed the connection]
warpme has quit [Ping timeout: 480 seconds]
fab has quit [Quit: fab]
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
sima has joined #dri-devel
mupuf has quit [Remote host closed the connection]
hakzsam has quit [Remote host closed the connection]
mupuf has joined #dri-devel
<dj-death> mareko: hey there, do you think you could give a look at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30038 ?
<dj-death> mareko: looks good to me but I'm not really a huge expert on the mesa/state-tracker code :)
hakzsam has joined #dri-devel
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
warpme has joined #dri-devel
simon-perretta-img has quit [Read error: Connection reset by peer]
simon-perretta-img has joined #dri-devel
fab has joined #dri-devel
dviola has left #dri-devel [WeeChat 4.3.3]
dviola has joined #dri-devel
bmodem has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #dri-devel
jkrzyszt_ has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
simon-perretta-img has quit [Read error: Connection reset by peer]
simon-perretta-img has joined #dri-devel
phire has quit [Remote host closed the connection]
flynnjiang1 has quit []
LeviYun has joined #dri-devel
warpme has quit []
warpme has joined #dri-devel
simon-perretta-img has quit [Ping timeout: 480 seconds]
simon-perretta-img has joined #dri-devel
lynxeye has joined #dri-devel
Company has quit [Quit: Leaving]
phire has joined #dri-devel
yuq825 has quit [Read error: Connection reset by peer]
yuq825 has joined #dri-devel
pcercuei has joined #dri-devel
epoch101 has quit []
flynnjiang has joined #dri-devel
<sima> mripard, I wonder whether we could even try to push the -next trees first, as a test, to catch people misplacing patches
<mripard> it's weird still, because drm-misc-next-fixes was still at drm-misc-next-fixes-2024-06-07
<sima> since the linux-next branch really should always be fast-forwards
<sima> mripard, I haven't looked why it happened tbh
<sima> maybe dim broke instead
<mripard> so it hasn't moved in a month, and it was definitely working around that time
* sima kinda busy processing pr
u-amarsh04 has joined #dri-devel
apinheiro has joined #dri-devel
smpl has joined #dri-devel
<sima> rodrigovivi, thellstrom, demarchi xe had a wrong rerere solution in drm-tip that resulted in https://paste.debian.net/hidden/df834b8a/
<sima> spotted it while backmerging -rc6 into drm-next and fixed it there
<thellstrom> Weird, I thought I fixed that yesterday?
<thellstrom> sima: ^
warpme has quit []
<sima> thellstrom, hm maybe git lost it again, sometimes it's confused like that
<sima> or the section right after
bmodem has quit [Ping timeout: 480 seconds]
<thellstrom> Yup. I reverted Imres manual fixup which was after the merge of xe-for-CI and instead placed it after the merge of drm-next...
flynnjiang has quit [Remote host closed the connection]
<thellstrom> So the drm-rerere commit supposed to fix this is 3c92d77045fa9e736cb72bc88b9acdcf1cdc507d
flynnjiang has joined #dri-devel
flynnjiang has quit [Remote host closed the connection]
<sima> thellstrom, hm yeah I have that, maybe git just got confused because the context changed
warpme has joined #dri-devel
<sima> I had to redo a different xe conflict in drm-tip too after I merged the latest drm-xe-next from rodrigovivi
<sima> git rerere isn't super smart, and sometimes even incompatible between different git versions
flynnjiang has joined #dri-devel
<sima> but it's been a while I've seen one of those
daemondragon has joined #dri-devel
<thellstrom> Hm. Yes, I thought even weirder was how that line got added anyway. It's neither in the merge source nor destination and the result of of an automatic merge..
phire has quit [Read error: Connection reset by peer]
glennk has quit [Ping timeout: 480 seconds]
<sima> thellstrom, we have rerere enabled, so you need to nuke the wrong stored conflict resolution
<sima> deleting the fixup alone won't be enough if the issue is in the rerere side
<sima> so the issue might predate imre's rerere commit, and imre just tried to patch it up with a fixup
<sima> instead of deleting the root cause
<sima> and you deleting the fixup means it pops back up
<thellstrom> Well the fixup wasn't actually deleted but rather moved to where it surfaces. But IIRC I at some point added a conflict resolution to add such a line in an unrelated place so I may have to dig a bit deeper.
<sima> thellstrom, well I deleted the fixup since it's baked in now
daemondragon has quit [Remote host closed the connection]
daemondragon has joined #dri-devel
phire has joined #dri-devel
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #dri-devel
flynnjiang has quit [Remote host closed the connection]
bmodem has joined #dri-devel
phire has quit [Remote host closed the connection]
phire has joined #dri-devel
mriesch has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
mriesch has joined #dri-devel
Fijxu has quit [Quit: XD!!]
Fijxu has joined #dri-devel
davispuh has joined #dri-devel
glennk has joined #dri-devel
<sima> robclark, bbd9d05618a6d608c72640b1d3d651a75913456a stumbled over this one and it's kinda ... ugh how that went in
<sima> robclark, if cros/android really wants to push that I think we need to have some uapi docs for it to make it a proper stable tracepoint, like what pepp is doing
<sima> and maybe more than one driver supporting it 4 years later :-/
guludo has joined #dri-devel
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
rasterman has joined #dri-devel
<mripard> lumag: yeah, ideally someone maintaining amdgpu
<mripard> I thought I acked that patch though?
rasterman has quit [Quit: Gettin' stinky!]
<sima> I think this is simple enough that one review/ack is enough
<sima> once it's been 2-3 weeks on the list
<sima> agd5f, found all your pulls, was blind
<lumag> mripard, going through the ML history, no
<lumag> you didn't
<lumag> sima, ack.
hakzsam has quit []
mupuf has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
hakzsam has joined #dri-devel
mupuf has joined #dri-devel
fab has quit [Quit: fab]
<daniels> spoiler: it’s literally llvmpipe https://youtu.be/LNva9WrwZ2A
<cwabbott> wow, what a way to advertise... nothing
<zmike> feels kinda bad to punch down on a channel with 8 subscribers
<daniels> cwabbott: you just don’t understand their amazing innovation https://www.x-silicon.com/news/
kts has joined #dri-devel
fab has joined #dri-devel
<imre> thellstrom, sima, ftr: the wrong merge result came about already before my 'dim push', see the earlier https://lore.kernel.org/all/20240628085457.21929-1-nirmoy.das@intel.com . After the push and noticing the build failure in drm-tip I also checked drm-rerere/rr-cache, but haven't found any resolution for the given line -> added the fixup (even though not after the correct merge point).
<sima> imre, yeah it happens, rerere is sometimes a mess
warpme has quit []
<robclark> sima: it isn't cros/android, it is perfetto
<sima> robclark, well the original patch that landed the tracepoint in 2020 claimed it's for android
<sima> msm is the first upstream driver using it
<robclark> it is because android uses perfetto ;-)
<robclark> anyways, it is a thing userspace tracing tools need.. and was already there.. so I used it ;-)
<sima> yeah I just want to avoid a world where we have like android tracepoints (mostly downstream) and other tracepoints used by non-android
<sima> kinda why I'm pestering pepp so much too
<robclark> I didn't want to hack on perfetto to add a new thing.. so I used the existing thing
<sima> robclark, yeah definitely don't want a 3rd thing just to make it even more messy
<sima> but would be good to at least integrated that tracepoint into the same docs that pepp is working on
<robclark> anyways, what is there seemed good enough.. anything else would just be more or less the same thing with a different coat of paint
<sima> yup
<robclark> fair
<sima> I don't care about the pain brand, just that we're at least trying to document it and roll it out consistently
<robclark> I hadn't been following the docs he is working on, but would make sense to have more than just the implicit "how perfetto uses it" docs
<sima> kinda like the drm fdinfo situation, there's already much better consistency just by starting with some docs and forcing people to jointly bikeshed those
<sima> robclark, yup
<sima> also, some docs that we're trying really hard to keep those tracepoints stable across releases
<sima> and consistent across drivers
<sima> so that other traces can also use those
<sima> *tracers
<robclark> we don't have a choice but to keep that tracepoint as abi.. there is already userspace using it.. the time to bikeshed it has already passed
<sima> eh, msm is the first one in upstream actually using it
<sima> so you're the one baking it in
<robclark> no, I mean perfetto is already using it
<sima> yeah, but for the upstream no-regressions rule
<sima> if we do a different one, we'll never break perfetto
<sima> using the one perfetto uses means we must also pretty much keep it working as-is forever
<robclark> right, but that is just creating more work for ourselves (ie. having to teach perfetto about a new thing)
<sima> oh sure
<robclark> I'm inherently lazy that way :-P
<sima> bit of docs + some acks would still be good that nothing, because the og patch didn't even go to dri-devel iirc
<sima> *better than nothing
* sima not much english today
warpme has joined #dri-devel
<sima> robclark, https://lore.kernel.org/dri-devel/?q=gpu%2Ftrace%3A+add+a+gpu+total+memory+usage+tracepoint <- this is a bit too little consensus finding for my taste :-P
<sima> don't need much more, but should be a tad bit more than zero
<sima> essentially drm uapi doc patch plus commit message that says "perfetto uses it, seems good enough" to dri-devel and I'll ack
<sima> and maybe poke a few tracing people to make sure there's no violent disagreement
<robclark> if you've got a pointer to what pepp is working on I'll take a look later and try to add something for gpu memory traces.. (it is holiday atm)
<sima> it's stable uapi after all
<sima> robclark, pepp is still very much wip, the uapi is kinda just a filler for now
<robclark> thx
<sima> I think just a starting point is already much better, it really seemed to work pretty well to get drm-fdinfo into pretty good shape
<sima> plus a lot of tursulin staying on top of things
<sima> robclark, there's also stuff like maybe trying to make sure the ctx for the mem tracepoints has some relation to the ctx of the scheduler events
<sima> that's probably the area where we're most likely to just make a mess for the dustbin
<sima> and also whether userspace has any expectation of connecting that kernel ctx id with vk/gl context or not
<sima> or with fdinfo stuff (but not sure we have those details there already)
<robclark> sima: the tracepoint is global memory usage, fwiw
<robclark> so no ctx
<robclark> well, there is gpu_id
<sima> yeah, but what do you put in there
<robclark> but I guess that just maps to "create a different counter line"
<sima> just want to avoid that one driver puts the drm minor in there, the next the hw engine and the third the logical ctx id
<sima> fourth probably just goes with 0
<sima> or that you can't align things with fdinfo output
<robclark> minor is defn the wrong thing
<sima> there's lots of ways to screw this up
<robclark> maybe we should have a unique counter id for each drm device
Mangix has quit [Read error: Connection reset by peer]
<sima> robclark, minor of the render node doesn't sound wrong to me for something that's gpu_id
Mangix has joined #dri-devel
<sima> or the primary
<sima> except accel messes that up ofc
<robclark> each drm_device should have a unique id
<sima> maybe?
<sima> really my aim here is just to get people to ponder these details, and make sure the right folks are connected and we don't end up with fdinfo, sched tp and memory tp doing completely different things
<sima> I fully expect that there will be at least some messy situations at first
coldfeet has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
epoch101 has joined #dri-devel
tuliom has joined #dri-devel
yuq825 has left #dri-devel [#dri-devel]
daemondragon has quit [Remote host closed the connection]
sima has quit [Remote host closed the connection]
bmodem has quit [Ping timeout: 480 seconds]
lanodan has quit [Ping timeout: 480 seconds]
kzd has joined #dri-devel
Tashtari has joined #dri-devel
mripard has quit [Quit: mripard]
kts has quit [Ping timeout: 480 seconds]
<Tashtari> Hi all. I upgraded mesa-24.0.7_1 to mesa-24.1.1_2 and Firefox started segfaulting when loading certain websites (Google Maps for one) and PDFs. Downgrading the package resolves the issue, and upgrading to the latest package (24.1.2_1) does not resolve it. I've collected a backtrace here: http://paste.debian.net/1322416/
dliviu has quit [Ping timeout: 480 seconds]
<Tashtari> Happy to collect any more data that might be needed to help resolve the issue. Can anyone take a look?
<Tashtari> (I use Void Linux, btw)
tuliom has left #dri-devel [WeeChat 4.3.3]
<pepp> Tashtari: which GPU are you using?
<Tashtari> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO / Venus LE / Tropo PRO-L [Radeon HD 8830M / R7 250 / R7 M465X] (rev 87)
kts has joined #dri-devel
<pepp> Tashtari: looks like https://gitlab.freedesktop.org/mesa/mesa/-/issues/11352 - the fix isn't merged yet
<Tashtari> Ahh, cool. Glad it's something already known.
<Tashtari> Thanks for looking into it.
<pepp> Tashtari: using the amdgpu kernel module instead of radeon is another possiblity to fix
<Tashtari> It's cool, I can stay on the old version of mesa until the fix is rolled out.
<pepp> sure
Mangix has quit [Ping timeout: 480 seconds]
sima has joined #dri-devel
dliviu has joined #dri-devel
nopjmp_ has quit []
warpme has quit []
nopjmp has joined #dri-devel
epoch101 has quit []
sarnex has quit [Read error: Connection reset by peer]
Mangix has joined #dri-devel
sarnex has joined #dri-devel
epoch101 has joined #dri-devel
TMM has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM has joined #dri-devel
melonai has quit []
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
coldfeet has quit [Remote host closed the connection]
melonai has joined #dri-devel
LeviYun has joined #dri-devel
odrling has quit [Remote host closed the connection]
odrling has joined #dri-devel
simon-perretta-img has quit [Read error: No route to host]
simon-perretta-img has joined #dri-devel
odrling has quit [Remote host closed the connection]
odrling has joined #dri-devel
ungeskriptet is now known as Guest602
ungeskriptet has joined #dri-devel
kts has quit [Quit: Konversation terminated!]
Guest602 has quit [Ping timeout: 480 seconds]
Duke`` has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
enzuru has quit [Quit: ZNC 1.8.2 - https://znc.in]
enzuru has joined #dri-devel
tzimmermann has quit [Quit: Leaving]
smpl has quit [Ping timeout: 480 seconds]
phire has quit [Read error: Connection reset by peer]
nerdopolis has joined #dri-devel
LeviYun has joined #dri-devel
epoch101_ has joined #dri-devel
epoch101 has quit [Ping timeout: 480 seconds]
ungeskriptet is now known as Guest607
LeviYun has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
Guest607 has quit [Ping timeout: 480 seconds]
coldfeet has joined #dri-devel
Haaninjo has joined #dri-devel
ungeskriptet has joined #dri-devel
simon-perretta-img has quit [Read error: No route to host]
LeviYun has joined #dri-devel
simon-perretta-img has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
lanodan has joined #dri-devel
nerdopolis has joined #dri-devel
epoch101_ has quit [Ping timeout: 480 seconds]
eukara has joined #dri-devel
fab has quit [Quit: fab]
LeviYun has joined #dri-devel
epoch101 has joined #dri-devel
Dark-Show has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
epoch101 has quit []
davispuh has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
guludo has quit [Ping timeout: 480 seconds]
Company has joined #dri-devel
guludo has joined #dri-devel
davispuh has joined #dri-devel
jkrzyszt_ has quit [Ping timeout: 480 seconds]
lynxeye has quit [Quit: Leaving.]
Dark-Show has quit [Ping timeout: 480 seconds]
Dark-Show has joined #dri-devel
Dark-Show has quit [Ping timeout: 480 seconds]
Dark-Show has joined #dri-devel
LeviYun has joined #dri-devel
coldfeet has quit [Remote host closed the connection]
LeviYun has quit [Ping timeout: 480 seconds]
crabbedhaloablut has quit []
crabbedhaloablut has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
Duke`` has joined #dri-devel
Simonx22 has quit []
nerdopolis has quit [Ping timeout: 480 seconds]
Simonx22 has joined #dri-devel
Simonx22 has quit []
Simonx22 has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
benjaminl has quit [Ping timeout: 480 seconds]
benjaminl has joined #dri-devel
nerdopolis has joined #dri-devel
frankbinns has quit [Remote host closed the connection]
frankbinns has joined #dri-devel
LeviYun has joined #dri-devel
feaneron has joined #dri-devel
nerdopolis has quit [Ping timeout: 480 seconds]
epoch101 has joined #dri-devel
glennk has quit [Ping timeout: 480 seconds]
lanodan has quit [Quit: WeeChat 4.2.1]
lanodan has joined #dri-devel
<alyssa> does glcts have any coverage for indirect draws with tessellation? why would it have that? (-:
<alyssa> ah, there's KHR-GL46.pipeline_statistics_query_tests_ARB.functional_tess_queries ... so you need full gl4.6 to get coverage for a gles3.2 feature, classic
crabbedhaloablut has quit [Read error: Connection reset by peer]
crabbedhaloablut has joined #dri-devel
LeviYun has quit [Ping timeout: 480 seconds]
guludo has quit [Quit: WeeChat 4.3.3]
pcercuei has quit [Quit: dodo]
LeviYun has joined #dri-devel
sima has quit [Ping timeout: 480 seconds]
LeviYun has quit [Ping timeout: 480 seconds]
nerdopolis has joined #dri-devel