Claude review: drm/virtio: Freeze and restore hooks to support suspend and resume

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

**Overall:** Clean extraction of `virtio_gpu_find_vqs()` helper and a well-structured `virtio_gpu_wait_queue()`. The freeze/restore flow is correct.

**Issue 1 — Missing error recovery in freeze (medium severity):**

If `virtio_gpu_wait_queue` times out after `drm_mode_config_helper_suspend()` has already succeeded, the function returns an error but leaves the DRM subsystem in a suspended state:

```c
error = drm_mode_config_helper_suspend(dev);
if (error) {
    DRM_ERROR("suspend error %d\n", error);
    return error;
}

flush_work(&vgdev->obj_free_work);
// ...

error = virtio_gpu_wait_queue(&vgdev->ctrlq, vgdev->ctrlq.vq->num_max);

if (error) {
    DRM_ERROR("suspend error %d\n", error);
    return error;  // DRM still suspended — no recovery
}
```

The error paths after the successful suspend should call `drm_mode_config_helper_resume(dev)` before returning.

**Issue 2 — Redundant min() in wait_queue call site:**

The caller passes `vgdev->ctrlq.vq->num_max` and `virtio_gpu_wait_queue` caps at `vgvq->vq->num_max`. This is harmless (the helper is designed for general use), just noting it.

**Nit — Extra blank lines in freeze between call and error check:**

```c
error = virtio_gpu_wait_queue(&vgdev->ctrlq, vgdev->ctrlq.vq->num_max);

if (error) {
```

Typical kernel style omits the blank line between a function call and its error check. Minor.

---

---
Generated by Claude Code Patch Reviewer