Re: [PATCH 1/3] drm/virtio: skip set_scanout if framebuffer didn't change

From: Chia-I Wu
Date: Wed Dec 11 2019 - 13:27:53 EST


On Wed, Dec 11, 2019 at 12:42 AM Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:
>
> Signed-off-by: Gerd Hoffmann <kraxel@xxxxxxxxxx>
> ---
> drivers/gpu/drm/virtio/virtgpu_plane.c | 31 ++++++++++++++------------
> 1 file changed, 17 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/gpu/drm/virtio/virtgpu_plane.c b/drivers/gpu/drm/virtio/virtgpu_plane.c
> index bc4bc4475a8c..a0f91658c2bc 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_plane.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_plane.c
> @@ -151,20 +151,23 @@ static void virtio_gpu_primary_plane_update(struct drm_plane *plane,
> if (bo->dumb)
> virtio_gpu_update_dumb_bo(vgdev, bo, plane->state);
>
> - DRM_DEBUG("handle 0x%x, crtc %dx%d+%d+%d, src %dx%d+%d+%d\n",
> - bo->hw_res_handle,
> - plane->state->crtc_w, plane->state->crtc_h,
> - plane->state->crtc_x, plane->state->crtc_y,
> - plane->state->src_w >> 16,
> - plane->state->src_h >> 16,
> - plane->state->src_x >> 16,
> - plane->state->src_y >> 16);
> - virtio_gpu_cmd_set_scanout(vgdev, output->index,
> - bo->hw_res_handle,
> - plane->state->src_w >> 16,
> - plane->state->src_h >> 16,
> - plane->state->src_x >> 16,
> - plane->state->src_y >> 16);
> + if (plane->state->fb != old_state->fb) {
Should we check src_{w,h,x,y} as well?
> + DRM_DEBUG("handle 0x%x, crtc %dx%d+%d+%d, src %dx%d+%d+%d\n",
> + bo->hw_res_handle,
> + plane->state->crtc_w, plane->state->crtc_h,
> + plane->state->crtc_x, plane->state->crtc_y,
> + plane->state->src_w >> 16,
> + plane->state->src_h >> 16,
> + plane->state->src_x >> 16,
> + plane->state->src_y >> 16);
> + virtio_gpu_cmd_set_scanout(vgdev, output->index,
> + bo->hw_res_handle,
> + plane->state->src_w >> 16,
> + plane->state->src_h >> 16,
> + plane->state->src_x >> 16,
> + plane->state->src_y >> 16);
> + }
> +
> virtio_gpu_cmd_resource_flush(vgdev, bo->hw_res_handle,
> plane->state->src_x >> 16,
> plane->state->src_y >> 16,
> --
> 2.18.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.freedesktop.org/mailman/listinfo/dri-devel