On 21/4/23 03:12, Gurchetan Singh wrote:
The virtio-gpu GL device has a heavy dependence on virgl.
Acknowledge this by naming functions accurately.

Signed-off-by: Gurchetan Singh <gurchetansi...@chromium.org>
---
  hw/display/virtio-gpu-gl.c     | 27 ++++++++++++++-------------
  hw/display/virtio-gpu-virgl.c  |  2 +-
  include/hw/virtio/virtio-gpu.h |  2 +-
  3 files changed, 16 insertions(+), 15 deletions(-)


diff --git a/include/hw/virtio/virtio-gpu.h b/include/hw/virtio/virtio-gpu.h
index adee17968d..e256e44172 100644
--- a/include/hw/virtio/virtio-gpu.h
+++ b/include/hw/virtio/virtio-gpu.h
@@ -297,7 +297,7 @@ void virtio_gpu_virgl_process_cmd(VirtIOGPU *g,
                                    struct virtio_gpu_ctrl_command *cmd);
  void virtio_gpu_virgl_fence_poll(VirtIOGPU *g);
  void virtio_gpu_virgl_reset_scanout(VirtIOGPU *g);
-void virtio_gpu_virgl_reset(VirtIOGPU *g);
+void virtio_gpu_virglrenderer_reset(VirtIOGPU *g);

Or virtio_gpu_virgl_reset_renderer() similar to scanout?

Regardless,

Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>

  int virtio_gpu_virgl_init(VirtIOGPU *g);
  int virtio_gpu_virgl_get_num_capsets(VirtIOGPU *g);


Reply via email to