17:34imirkin: skeggsb: what do you think about keeping track of the last process to submit a pushbuf for a particular fd? i'm really sick of X being blamed
18:05karolherbst: imirkin: I thought you already wrote a patch like this, but I also got annoyed by that recently
18:07karolherbst: imirkin: btw, I have a more or less ugly attempt in making the nouveau_fence stuff not depend on having a nouveau_screen object: https://github.com/karolherbst/mesa/commit/651557d02408b0461b05ac5bda28766fb8b25903
18:07karolherbst: any suggestions?
18:08karolherbst: I would kind of prefer having nv30 and nv50/nvc0 doing more or less the same, but... I don't know why it is different
18:09karolherbst: and it is a bit silly that we need the screen for updating the driver stats. But I am sure there is no way around that
18:13karolherbst: or maybe I should give up on the one pushbuf per context idea? Would make those changes unnecessary
18:13karolherbst: it seems to work, I just don't like to have different way of doing fencing in the drivers. Would be nice to adjust nv30 to whatever nv50/nvc0 is doing
18:18imirkin: karolherbst: i started to write a patch. but it was a lot of work.
18:19karolherbst: ohh, because of those copies of the process name everywhere? Right
18:23karolherbst: worst case we could use char**..... is there at least some way to notice that the fd gets handed over to another process?
18:23imirkin: not really
18:23karolherbst: I would imagine that both processes could still use the fd anyway
18:23imirkin: with dup'd fds, yes
18:25karolherbst: worst case we add a nouveau ioctl .... or abuse setparam or something :/
18:25karolherbst: mhh maybe setparam isn't such a bad idea
18:37Lyude: karolherbst: btw, didn't get a chance to setup the dogfood yesterday so I will probably do it this afternoon
18:37Lyude: got distracted with getting this khadas vim2 working 😅
18:38karolherbst: Lyude: no worries. I am already working on a different solution, but the patch I gave to you should work potentially. But it might help to track down various issues we have, like chromium 69 was pretty much broken with it, allthough it didn't crash.
18:46karolherbst: nv30 and nv50 are broken though
18:46karolherbst: want to have the other solution first where we share one channel and see how well that works out