Hi Josh,
>
> > If virgl=true (which means blob=false at the moment), then things work
> > very differently.
> Yes, we're using virglrenderer. The flushed resources are backed by host
Virgl is not my forte. Someone working on virgl should be able to help you.
Thanks,
Vivek
> allocated buffers.
> If virgl=true (which means blob=false at the moment), then things work
> very differently.
Yes, we're using virglrenderer. The flushed resources are backed by host
allocated buffers. We tried posting the flushed resource directly to the
display and replied to the flush immediately (since not f
Hi Josh,
> It looks like the virtio-gpu flush should be fenced, but on the host side the
> received flush cmd doesn't have the fence flag set, and no fence_id. So,
> I have to reply right away instead of waiting for scanout to complete.
> Is that expected? then what's the right way to vsync the
It looks like the virtio-gpu flush should be fenced, but on the host side the
received flush cmd doesn't have the fence flag set, and no fence_id. So, I
have to reply right away instead of waiting for scanout to complete. Is that
expected? then what's the right way to vsync the guest?
At the
