virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Virtualization List <virtualization@lists.linux-foundation.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>,
	levinsasha928@gmail.com, Amit Shah <amit.shah@redhat.com>
Subject: [PATCH v5 00/11]  virtio: s4 support
Date: Thu, 15 Dec 2011 18:15:46 +0530	[thread overview]
Message-ID: <cover.1323952933.git.amit.shah@redhat.com> (raw)

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 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 if=/dev/zero of=/tmp/bigfile bs=1024 count=200000'
  across S4 gives same sha1sum for the file in the guest as well as
  one that's created without invoking S4.

* 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.

* virtio-balloon: Works fine before and after.  Forgets the ballooned
  value across S4 (see details in commit log). Maintains ballooned
  value on failed freeze.

All of these tests are run in parallel.

v5:
 - Enable virtio device after the driver-specific restore/thaw
   callbacks are completed.
 - Balloon: Don't exit kthread on freeze.  It's already frozen by the
   PM API before invoking the freeze callback, so exiting is pointless.

v4:
 - Disable / enable napi across S4 (Michael S. Tsirkin)
 - Balloon: lots of improvements (I had neglected this driver thinking
   it was a simple one, but this one needed the most thought!  Check
   the commit log for patch 12 for details.)
 - Net, Blk: Reset device as the first operation on freeze

v3:
 - Reset vqs before deleting them (Sasha Levin)
 - Flush block queue before freeze (Rusty)
 - Detach netdev before freeze (Michael S. Tsirkin)

v2:
 - fix checkpatch errors/warnings

Amit Shah (11):
  virtio: pci: switch to new PM API
  virtio: pci: add PM notification handlers for restore, freeze, thaw,
    poweroff
  virtio: console: Move vq and vq buf removal into separate functions
  virtio: console: Add freeze and restore handlers to support S4
  virtio: blk: Move vq initialization to separate function
  virtio: blk: Add freeze, restore handlers to support S4
  virtio: net: Move vq initialization into separate function
  virtio: net: Move vq and vq buf removal into separate function
  virtio: net: Add freeze, restore handlers to support S4
  virtio: balloon: Move vq initialization into separate function
  virtio: balloon: Add freeze, restore handlers to support S4

 drivers/block/virtio_blk.c      |   57 ++++++++++++++++--
 drivers/char/virtio_console.c   |  126 ++++++++++++++++++++++++++++++---------
 drivers/net/virtio_net.c        |  102 +++++++++++++++++++++++--------
 drivers/virtio/virtio_balloon.c |   95 ++++++++++++++++++++++++------
 drivers/virtio/virtio_pci.c     |  106 +++++++++++++++++++++++++++++++-
 include/linux/virtio.h          |    5 ++
 6 files changed, 410 insertions(+), 81 deletions(-)

-- 
1.7.7.3

             reply	other threads:[~2011-12-15 12:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15 12:45 Amit Shah [this message]
2011-12-15 12:45 ` [PATCH v5 01/11] virtio: pci: switch to new PM API Amit Shah
2011-12-15 12:45 ` [PATCH v5 02/11] virtio: pci: add PM notification handlers for restore, freeze, thaw, poweroff Amit Shah
2011-12-15 12:45 ` [PATCH v5 03/11] virtio: console: Move vq and vq buf removal into separate functions Amit Shah
2011-12-15 12:45 ` [PATCH v5 04/11] virtio: console: Add freeze and restore handlers to support S4 Amit Shah
2011-12-15 12:45 ` [PATCH v5 05/11] virtio: blk: Move vq initialization to separate function Amit Shah
2011-12-15 12:45 ` [PATCH v5 06/11] virtio: blk: Add freeze, restore handlers to support S4 Amit Shah
2011-12-15 12:45 ` [PATCH v5 07/11] virtio: net: Move vq initialization into separate function Amit Shah
2011-12-15 12:45 ` [PATCH v5 08/11] virtio: net: Move vq and vq buf removal " Amit Shah
2011-12-15 12:45 ` [PATCH v5 09/11] virtio: net: Add freeze, restore handlers to support S4 Amit Shah
2011-12-15 12:45 ` [PATCH v5 10/11] virtio: balloon: Move vq initialization into separate function Amit Shah
2011-12-15 12:45 ` [PATCH v5 11/11] virtio: balloon: Add freeze, restore handlers to support S4 Amit Shah
2011-12-15 13:13 ` [PATCH v5 00/11] virtio: s4 support Michael S. Tsirkin
2011-12-15 14:55   ` Amit Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1323952933.git.amit.shah@redhat.com \
    --to=amit.shah@redhat.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).