similar to: [PULL] virtio: S3 support, use PM API macro for init

Hello, Turns out S3 is not different from S4 for virtio devices: the device is assumed to be reset, so the host and guest state are to be assumed to be out of sync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A

Hello, Turns out S3 is not different from S4 for virtio devices: the device is assumed to be reset, so the host and guest state are to be assumed to be out of sync upon resume. We handle the S4 case with exactly the same scenario, so just point the suspend/resume routines to the freeze/restore ones. Once that is done, we also use the PM API's macro to initialise the sleep functions. A

commit e562966dbaf49e7804097cd991e5d3a8934fc148 added support for S4 to the balloon driver. The freeze function did nothing to free the pages, since reclaiming the pages from the host to immediately give them back (if S4 was successful) seemed wasteful. Also, if S4 wasn't successful, the guest would have to re-fill the balloon. On restore, the pages were supposed to be marked freed and the

commit e562966dbaf49e7804097cd991e5d3a8934fc148 added support for S4 to the balloon driver. The freeze function did nothing to free the pages, since reclaiming the pages from the host to immediately give them back (if S4 was successful) seemed wasteful. Also, if S4 wasn't successful, the guest would have to re-fill the balloon. On restore, the pages were supposed to be marked freed and the

Hello, The main fix is to update the host with the current balloon value on module removal after deflating the balloon. Without the fix, the host has the wrong idea of the ballooned memory in the guest. This is patch 2. Patches 1 and 3 are cleanups with no effective code change. Please apply, Amit Shah (3): virtio: balloon: drop restore_common() virtio: balloon: let host know of updated

Hello, The main fix is to update the host with the current balloon value on module removal after deflating the balloon. Without the fix, the host has the wrong idea of the ballooned memory in the guest. This is patch 2. Patches 1 and 3 are cleanups with no effective code change. Please apply, Amit Shah (3): virtio: balloon: drop restore_common() virtio: balloon: let host know of updated

Hi, These patches add support for S4 to virtio (pci) and all drivers. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit and init work is also done in the freeze and restore functions. All the drivers in testing work fine: * virtio-blk is used for the only disk in the VM, IO works fine before and after. 'dd

Hi, These patches add support for S4 to virtio (pci) and all drivers. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit and init work is also done in the freeze and restore functions. All the drivers in testing work fine: * virtio-blk is used for the only disk in the VM, IO works fine before and after. 'dd

Hi, These patches add support for S4 to virtio (pci) and all drivers. Michael saw some race in virtio-net module removal which will need a similar fix for the freeze code as well. I'll update the virtio-net patch with that fix once the fix is settled upon and applied. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit

Hi, These patches add support for S4 to virtio (pci) and all drivers. Michael saw some race in virtio-net module removal which will need a similar fix for the freeze code as well. I'll update the virtio-net patch with that fix once the fix is settled upon and applied. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit

(I called the tag to-linus. I think it worked). To git at github.com:rustyrussell/linux.git + 3ed0016...b6c96c0 master -> master (forced update) + 815645d...f8e8df5 to-linus -> to-linus (forced update) + git request-pull remotes/origin/master git://github.com/rustyrussell/linux.git The following changes since commit e343a895a9f342f239c5e3c5ffc6c0b1707e6244: Merge tag

(I called the tag to-linus. I think it worked). To git at github.com:rustyrussell/linux.git + 3ed0016...b6c96c0 master -> master (forced update) + 815645d...f8e8df5 to-linus -> to-linus (forced update) + git request-pull remotes/origin/master git://github.com/rustyrussell/linux.git The following changes since commit e343a895a9f342f239c5e3c5ffc6c0b1707e6244: Merge tag

Hi, These patches add support for S4 to virtio (pci) and all drivers. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit and init work is also done in the freeze and restore functions. All the drivers in testing work fine: * virtio-blk is used for the only disk in the VM, IO works fine before and after. 'dd

Hi, These patches add support for S4 to virtio (pci) and all drivers. For each driver, all vqs are removed before hibernation, and then re-created after restore. Some driver-specific uninit and init work is also done in the freeze and restore functions. All the drivers in testing work fine: * virtio-blk is used for the only disk in the VM, IO works fine before and after. 'dd

On 21.10.2014 02:23, poma wrote: > On 20.10.2014 21:30, poma wrote: >> On 20.10.2014 08:13, poma wrote: >>> >>> 02:00.0 VGA compatible controller: >>> NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1) >>> Chipset: G98 (NV98) >>> Family : NV50 >>> >>> The same for all four kernel: >>> -

On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: > On 13.09.2014 07:02, poma wrote: >> On 13.09.2014 06:57, poma wrote: >>> >>> Actually I have nothing to show cause logs are all OK. >>> Haha, it seems to me that the bugs become intelligent. >>> >>> 3.15.10-201.fc20.x86_64 >>> 3.16.2-200.fc20.x86_64

On Sat, Sep 13, 2014 at 5:25 PM, poma <pomidorabelisima at gmail.com> wrote: > On 13.09.2014 22:58, Ilia Mirkin wrote: >> On Sat, Sep 13, 2014 at 4:52 PM, poma <pomidorabelisima at gmail.com> wrote: >>> On 13.09.2014 07:02, poma wrote: >>>> On 13.09.2014 06:57, poma wrote: >>>>> >>>>> Actually I have nothing to show cause logs

Dear Poma, Don't get anyone wrong, your input is greatly valued. The reason why "we" (nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down (thanks for that!), we don't know how big the difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and

The following changes since commit f7da9cdf45cbbad5029d4858dcbc0134e06084ed: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2012-07-28 06:00:39 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git tags/virtio-for-linus for you to fetch changes up to 6a743897144500fb4c4566ced3a498d5180fbb5b:

The following changes since commit f7da9cdf45cbbad5029d4858dcbc0134e06084ed: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2012-07-28 06:00:39 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git tags/virtio-for-linus for you to fetch changes up to 6a743897144500fb4c4566ced3a498d5180fbb5b: