Re: [PATCH v3 2/2] drm/virtio: Implement save and restore for virtio_gpu_objects

2025-07-10 Thread Dmitry Osipenko
On 7/9/25 18:34, Kim, Dongwon wrote: > Hi Dmitry, > > I thought about what you are saying - avoiding GPU reset and it would work > with normal > sleep and restore (s3) but the problem I saw was hibernation scenario (s4). > In this case, QEMU > process will be terminated after guest hibernation a

RE: [PATCH v3 2/2] drm/virtio: Implement save and restore for virtio_gpu_objects

2025-07-09 Thread Kim, Dongwon
anyway. So some sort of recreation seemed to be required from my point of view. > -Original Message- > From: Dmitry Osipenko > Sent: Wednesday, July 9, 2025 6:26 AM > To: Kim, Dongwon ; dri- > de...@lists.freedesktop.org > Cc: Kasireddy, Vivek > Subject: Re: [PAT

Re: [PATCH v3 2/2] drm/virtio: Implement save and restore for virtio_gpu_objects

2025-07-09 Thread Dmitry Osipenko
On 7/3/25 01:24, dongwon@intel.com wrote: > +int virtio_gpu_object_restore_all(struct virtio_gpu_device *vgdev) > +{ > + struct virtio_gpu_object_restore *curr, *tmp; > + struct virtio_gpu_mem_entry *ents; > + unsigned int nents; > + int ret; > + > + list_for_each_entry_safe

Re: [PATCH v3 2/2] drm/virtio: Implement save and restore for virtio_gpu_objects

2025-07-09 Thread Dmitry Osipenko
On 7/3/25 01:24, dongwon@intel.com wrote: > @@ -257,8 +290,11 @@ int virtio_gpu_object_create(struct virtio_gpu_device > *vgdev, > objs, fence); > virtio_gpu_object_attach(vgdev, bo, ents, nents); > } > + /* add submitted obj