On Fri, 21 Apr 2023 at 19:21, Gurchetan Singh
wrote:
>
> On Fri, Apr 21, 2023 at 9:00 AM Stefan Hajnoczi wrote:
> >
> > On Thu, 20 Apr 2023 at 21:13, Gurchetan Singh
> > wrote:
> > >
> > > gfxstream and both cross-domain (and even newer versions
> > > virglrenderer: see VIRGL_RENDERER_ASYNC_FENC
On Fri, Apr 21, 2023 at 9:00 AM Stefan Hajnoczi wrote:
>
> On Thu, 20 Apr 2023 at 21:13, Gurchetan Singh
> wrote:
> >
> > gfxstream and both cross-domain (and even newer versions
> > virglrenderer: see VIRGL_RENDERER_ASYNC_FENCE_CB) like to signal
> > fence completion on threads ("callback thread
On Thu, 20 Apr 2023 at 21:13, Gurchetan Singh
wrote:
>
> gfxstream and both cross-domain (and even newer versions
> virglrenderer: see VIRGL_RENDERER_ASYNC_FENCE_CB) like to signal
> fence completion on threads ("callback threads") that are
> different from the thread that processes the command qu
gfxstream and both cross-domain (and even newer versions
virglrenderer: see VIRGL_RENDERER_ASYNC_FENCE_CB) like to signal
fence completion on threads ("callback threads") that are
different from the thread that processes the command queue
("main thread").
This is generally possible with locking, a
