Hi, > In theory Mesa could help here, but GL isn't thread friendly at all, > so it probably won't help in the virgl > case even if it did. Since most GL apps compile a shader and block on > using it straight away doing it > in a thread won't help unblock things. > > So I think it would be best to have all the virgl vq processing happen > in it's own thread with some API > to the UI to do UI resizes (the most difficult) and dirty regions etc.
We can move only virgl into its own thread, but then we'll have two threads (virgl and main which runs ui) which use opengl. So I was thinking maybe it is better to have a single thread which runs both virgl and ui (and thats why I've started this thread ...). cheers, Gerd
