On Mon, Sep 8, 2025 at 11:12 PM Ryosuke Yasuoka <ryasuoka@redhat.com> wrote:
>
> Add drm_panic support for stdu in vmwgfx. This patch was tested in
> a VM with VMSVGA on Virtual Box.
>
> I got 2 type of suggestions from reviewers:
> 1. Write the panic screen to guest_memory_bo and send dirty/flush
> command
> 2. Write it to VRAM directly and then switch back to legacy mode
>
> Since option 2 is simpler than another one and ldu might be able
> to re-use some codes if ldu supports drm_panic, I re-write this
> v2 patch with option 2.
>
> Ryosuke Yasuoka (1):
> drm/vmwgfx: add drm_panic support for stdu
>
> drivers/gpu/drm/vmwgfx/vmwgfx_cmd.c | 73 ++++++++++++++++++++++++++++
> drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 18 +++++++
> drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 9 ++++
> drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 1 +
> drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 43 ++++++++++++++++
> drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 34 +++++++++++++
> 6 files changed, 178 insertions(+)
>
>
> base-commit: 306c8959b5fdfdc3900aebe4e56257a349f5765f
> --
> 2.51.0
>
This is the history of this patch.
v1:
https://lore.kernel.org/all/20250901083701.32365-1-ryasuoka@redhat.com/
v2:
- Map a scanout_buffer to VRAM in .get_scanout_buffer
- And then write to VRAM directly using fifo in legacy mode to avoid
allocations or command submissions.
Regards,
Ryosuke