On 11/19/24 13:21, Jocelyn Falempe wrote:
...
>> In the virtio_panic_flush() below,
>> virtio_gpu_panic_cmd_transfer_to_host_2d() is invoked only for dumb BOs.
>> Thus, only dumb BO supports panic output and should be accepted by
>> get_scanout_buffer(), other should be rejected with ENODEV here, A
On 18/11/2024 17:16, Dmitry Osipenko wrote:
On 11/13/24 11:44, Ryosuke Yasuoka wrote:
From: Jocelyn Falempe
Virtio gpu supports the drm_panic module, which displays a message to
the screen when a kernel panic occurs.
Signed-off-by: Ryosuke Yasuoka
Signed-off-by: Jocelyn Falempe
---
On a s
On 11/13/24 11:44, Ryosuke Yasuoka wrote:
> From: Jocelyn Falempe
>
> Virtio gpu supports the drm_panic module, which displays a message to
> the screen when a kernel panic occurs.
>
> Signed-off-by: Ryosuke Yasuoka
> Signed-off-by: Jocelyn Falempe
> ---
On a second look, I spotted few proble
On 11/13/24 11:44, Ryosuke Yasuoka wrote:
> From: Jocelyn Falempe
>
> Virtio gpu supports the drm_panic module, which displays a message to
> the screen when a kernel panic occurs.
>
> Signed-off-by: Ryosuke Yasuoka
> Signed-off-by: Jocelyn Falempe
> ---
I'll apply this patch tomorrow with a
From: Jocelyn Falempe
Virtio gpu supports the drm_panic module, which displays a message to
the screen when a kernel panic occurs.
Signed-off-by: Ryosuke Yasuoka
Signed-off-by: Jocelyn Falempe
---
v4:
- As per Dmitry's comment, make virtio_panic_buffer private to
virtio_gpu_device.
v3:
http
