Hi Dmitry, Sorry, I have been busy in handling some other high priority tasks so couldn't follow up with this. Yeah, so to confirm, you are saying this object save/restore mechanism should only be used for S4 case (in the PM notifier for virtio-gpu driver) and handle S3 case by not resetting virtio-gpu from QEMU?
I will take a look at that option. Thanks! > -----Original Message----- > From: Dmitry Osipenko <dmitry.osipe...@collabora.com> > Sent: Thursday, July 10, 2025 2:43 PM > To: Kim, Dongwon <dongwon....@intel.com>; dri-devel@lists.freedesktop.org > Cc: Kasireddy, Vivek <vivek.kasire...@intel.com> > Subject: Re: [PATCH v3 2/2] drm/virtio: Implement save and restore for > virtio_gpu_objects > > 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 and this actually destroys all the > > resources > anyway. So some sort of recreation seemed to be required from my point of > view. > > Can we add proper hibernation support/handling to the virtio-gpu driver? > I.e. restoring shmem buffers based on S4 PM_POST_HIBERNATION event and > not resetting GPU on S3. Entering S4 then should be prohibited if 3d contexts > feature enabled. > > -- > Best regards, > Dmitry
