alyssa changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard & Bifrost - https://gitlab.freedesktop.org/panfrost - Logs https://freenode.irclog.whitequark.org/panfrost - <daniels> avoiding X is a huge feature
stikonas has joined #panfrost
stikonas has quit [Remote host closed the connection]
<anarsoul> glmark2-es2-drm: ../src/gallium/drivers/lima/ir/gp/scheduler.c:395: gpir_sched_node: Assertion `result' failed.
<anarsoul> *sigh*
<anarsoul> I guess I need yuq's or cwabbott's help here. I don't understand how gp scheduler works.
vstehle has quit [Ping timeout: 246 seconds]
<alyssa> Mmblep
<urjaman> MIDGARD_MESA_DEBUG actually
<alyssa> Thanks
<anarsoul> I had higher expectations of lima gp compiler :(
<anarsoul> it can't handle nested bcsel nor 9th degree polynomial
<alyssa> Ook ook.
<anarsoul> anyway, 9th degree isn't enough. It needs 13th degree to get rid of bcsel
vstehle has joined #panfrost
<cwabbott> anarsoul: uhhh, yeah, the gp scheduler is a complicated beast
<cwabbott> it *should* work, so you probably hit some pathological case
<cwabbott> I probably couldn't figure it out myself without putting it in gdb
<cwabbott> so, the assert that you hit means that we couldn't schedule a node that needed to be scheduled, so we created a move instead, and scheduling that failed too
<cwabbott> I *think* I remember an issue with the scheduler that could cause it, but to understand it you'd have to understand the whole design of the scheduler first
<cwabbott> it has to do with those pesky double-wide ops that take 3-4 inputs, like bcsel
yann has quit [Ping timeout: 246 seconds]
raster has joined #panfrost
_whitelogger has joined #panfrost
afaerber has joined #panfrost
afaerber has quit [Remote host closed the connection]
afaerber has joined #panfrost
stikonas has joined #panfrost
stikonas has quit [Ping timeout: 252 seconds]
raster has quit [Remote host closed the connection]
yann has joined #panfrost
raster has joined #panfrost
raster has quit [Ping timeout: 252 seconds]
raster has joined #panfrost
<alyssa> Wacky
raster has quit [Remote host closed the connection]
raster has joined #panfrost
afaerber has quit [Quit: Leaving]
fysa has quit [Read error: Connection reset by peer]
fysa has joined #panfrost
raster has quit [Remote host closed the connection]
yann has quit [Ping timeout: 250 seconds]
pH5 has joined #panfrost
<anarsoul> cwabbott: probably a silly question, but is there a design doc for gp compiler?
<cwabbott> anarsoul: unfortunately not, although there were some emails between me and yuq where I explained stuff
<anarsoul> if there's nothing private, could you forward them to me?
<cwabbott> I'm trying to finish a rework of the scheduler I almost finished a while ago, including writing up a more informative comment
<cwabbott> sure
<cwabbott> anarsoul: what's your email?
<anarsoul> cwabbott: anarsoul at gmail
afaerber has joined #panfrost
* TheCycoONE notes that format is nearly as trivial to harvest as just writing the address
BenG83 has joined #panfrost
stikonas has joined #panfrost
<anarsoul> cwabbott: mixed top/bottom posting is evil. It's extremely hard to follow this email
narmstrong has quit [Read error: Connection reset by peer]
narmstrong has joined #panfrost
jernej has quit [Ping timeout: 258 seconds]
adjtm has joined #panfrost
jernej has joined #panfrost
adjtm_ has quit [Ping timeout: 250 seconds]
stikonas has quit [Quit: Konversation terminated!]
stikonas has joined #panfrost
hl has quit [Read error: Connection reset by peer]
yann has joined #panfrost
hl has joined #panfrost
stikonas_ has joined #panfrost
stikonas has quit [Ping timeout: 246 seconds]
stikonas has joined #panfrost
stikonas_ has quit [Ping timeout: 250 seconds]
pH5 has quit [Quit: -_-]
kszaq has joined #panfrost
NeuroScr has joined #panfrost
<kszaq> Good day everyone. I am trying to run Panfrost in mixed arch environment, that is aarch64 kernel with arm userspace, on T820. I fixed passing array pointer in https://gitlab.freedesktop.org/kszaq/mesa/commit/e0a07be but still getting only DATA_INVALID_FAULT. I stumbled upon https://gitlab.freedesktop.org/mesa/mesa/commit/97aa054 that suggest an assumption if userspace is 32-bit -> use 32-bit GPU descriptors but even with the assumptio
<kszaq> the same only-errors situation happens. I would be greatful if someone can tell me whether this assumption is correct or should I look somewhere else?
<HdkR> I don't think anyone is testing a mixed bitness environment atm
kszaq_ has joined #panfrost
kszaq has left #panfrost [#panfrost]
<kszaq_> I would assume so as there are few use cases.
<kszaq_> I am very new to panfrost, mesa and gpus in general so I will be asking questions about easy things: is there a way to dump the data passed to GPU that was reported as invalid in my case?
<HdkR> I don't think panwrap supports wrapping the panfrost drm. probably need to trace back which buffer is actually causing the GPU fault
<alyssa> PANTRACE_BASE=/dev/shm
<alyssa> ^^ set that
<alyssa> And then `pandecode /dev/shm`
<HdkR> There we go, alyssa has the hookup