Re: [PATCH 00/11] virtio: Support for hibernation (S4)
From: Michael S. Tsirkin
Date: Sun Oct 02 2011 - 05:48:21 EST
On Thu, Sep 29, 2011 at 08:55:56PM +0530, Amit Shah wrote:
> These patches add support for S4 to virtio (pci) and all drivers. The
> patches are based on the virtio-console patch series in Rusty's queue.
> For each driver, all vqs are removed before hibernation, and then
> re-created after restore.
> All the drivers in testing work fine:
> * virtio-blk is used for the only disk in the VM, IO works fine before
> and after.
> * virtio-console: port IO keeps working fine before and after.
> * If a port is waiting for data from the host (blocking read(2)
> call), this works fine in both the cases: host-side connection is
> available or unavailable after resume. In case the host-side
> connection isn't available, the blocking call is terminated. If
> it is available, the call continues to remain in blocked state
> till further data arrives.
> * virtio-net: ping remains active across S4. One packet is lost.
> (Current qemu.git has a regression in slirp code causing qemu
> segfault, commit 1ab74cea060 is the offender).
> * virtio-balloon: Works fine before and after. Forgets the ballooned
> value across S4. If it's desirable to maintain the ballooned value,
> a new config option can be created to do this.
> All in all, this looks pretty good.
> Please review and apply.
So a general comment is that we need to make sure
VQs are not used by guest or host while
they are deleted.
For example remove path in exiting virtio net does:
/* Free unused buffers in both send and recv, if any. */
unregister_netdev is done before del_vqs
which makes sure guest leaves the device alone, including
napi and tx. PM will need something like this too if it
removes the VQs, otherwise any use of 'vq->' might cause a crash.
As a side note: above code is not 100% robust in theory as guest could
try using VQs after reset, and we never documented that it's ok to
access such VQs, but in practice it's safe with existing hosts, accesses
are simnply discarded. Maybe we should just document this assumption in
Another theoretical concern with existing code is that interrupt
handler for the device might be in progress while we do
unregister_netdev, since these are not ordered wrt
io write that does the reset.
Probably reset in virtio pci should also flush all interrupt handlers?
> Amit Shah (11):
> virtio: pci: switch to new PM API
> virtio-pci: add PM notification handlers for restore, freeze, thaw,
> virtio: console: Move out vq and vq buf removal into separate
> virtio: console: Add freeze and restore handlers to support S4
> virtio: blk: Move out vq initialization to separate function
> virtio: blk: Add freeze, restore handlers to support S4
> virtio: net: Move out vq initialization into separate function
> virtio: net: Move out vq and vq buf removal into separate function
> virtio: net: Add freeze, restore handlers to support S4
> virtio: balloon: Move out vq initialization into separate function
> virtio: balloon: Add freeze, restore handlers to support S4
> drivers/block/virtio_blk.c | 36 ++++++++++--
> drivers/char/virtio_console.c | 124 ++++++++++++++++++++++++++++++---------
> drivers/net/virtio_net.c | 98 ++++++++++++++++++++++---------
> drivers/virtio/virtio_balloon.c | 65 +++++++++++++++------
> drivers/virtio/virtio_pci.c | 57 +++++++++++++++++-
> include/linux/virtio.h | 4 +
> 6 files changed, 301 insertions(+), 83 deletions(-)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/