<div dir="ltr">Dear mesa/experts,<div><br></div><div>Need your support to help us better understand how we can go about this behavior.</div><div><br></div><div>Here is what we have:</div><div>     1.    We are running QEMU based Debian guest with <span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">-device virtio-gpu-rutabaga,gfxstream-vulkan=on,cross-domain=on.   </span>Expect to run vulkan application eg.vkcube-wayland from guest via wayland proxy over gfxstream and wayland protocol.   Please check this link (<a href="https://www.qemu.org/docs/master/system/devices/virtio-gpu.html" target="_blank">https://www.qemu.org/docs/master/system/devices/virtio-gpu.html</a>) for what is rutabaga/gfxstream GPU mode.     In theory,  it should be sufficient to render vkcube graphics over vulkan/gfxstream/virtio-gpu via host wayland compositor with a physical GPU driver.</div><div>  2.  On guest side mesa,  we compile with these options</div><div>      <span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size:9pt;font-family:"Roboto Mono",monospace;color:rgb(24,128,56);vertical-align:baseline">-Dgallium-drivers=radeonsi,virgl,zink</span><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size:9pt;font-family:"Roboto Mono",monospace;color:rgb(0,0,0);vertical-align:baseline"> </span><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size:9pt;font-family:"Roboto Mono",monospace;color:rgb(24,128,56);vertical-align:baseline">-Dvulkan-drivers=virtio,amd.</span></div><div><span style="background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size:9pt;font-family:"Roboto Mono",monospace;color:rgb(24,128,56);vertical-align:baseline">  </span>3.  When running $vkcube-wayland with wayland proxy,  gbm_create_device(...) will be invoked to acquire drm device resource, which will invoke driCreateNewScreen2 -> dri2_init_screen() etc.</div><div><br></div><div>    <b><i>within mesa/src/gallium/frontends/dri/dri2.c,  what was the intention to indicate that "no zink" will be used?</i></b></div><div>===========================================</div><div>#ifdef HAVE_LIBDRM<br>if (pipe_loader_drm_probe_fd(&screen->dev, screen->fd, <b>false</b>)) <<=== <b>ZINK usage</b><br>      pscreen = pipe_loader_create_screen(screen->dev, driver_name_is_inferred);<br>#endif<br></div><div>=============================================</div><p style="margin:0px;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(159,160,28)"><span style="font-variant-ligatures:no-common-ligatures"></span></p><p style="margin:0px;font-stretch:normal;line-height:normal"><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small">4.  In current behavior, </span><span style="color:rgb(0,0,0);font-family:Menlo;font-size:11px;font-variant-ligatures:no-common-ligatures">virtio_gpu_driver_descriptor </span><span style="color:rgb(34,34,34);font-family:Arial,Helvetica,sans-serif;font-size:small">will be discovered and used.  Which will depend on "</span>-device virtio-gpu-gl-pci" the capsets of virgl and virgl2, which is not what we are using.<br></p><p style="margin:0px;font-stretch:normal;line-height:normal"><br></p><p style="margin:0px;font-stretch:normal;line-height:normal">Any clarification will be highly appreciated!</p><p style="margin:0px;font-stretch:normal;line-height:normal">Lei Zhou</p>

















<div><span style="background-color:transparent;color:rgb(24,128,56);font-family:"Roboto Mono",monospace;font-size:9pt"> </span></div><div><span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px"><br></span></div>





</div>