From: Amit Shah <amit.shah@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Virtualization List <virtualization@lists.linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 00/11] virtio: Support for hibernation (S4)
Date: Tue, 15 Nov 2011 18:22:46 +0530 [thread overview]
Message-ID: <20111115125246.GB26378@amit-x200.redhat.com> (raw)
In-Reply-To: <8739f9ipsi.fsf@rustcorp.com.au>
On (Tue) 04 Oct 2011 [10:36:05], Rusty Russell wrote:
> On Sun, 2 Oct 2011 11:49:21 +0200, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> > On Thu, Sep 29, 2011 at 08:55:56PM +0530, Amit Shah wrote:
> > > Hello,
> > >
> > > 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.
>
> I'm not familiar with the suspend code, but:
>
> 1) Does it already ensure there are no outstanding I/O requests? If
> not, we want to restore them when we unfreeze.
For the blk code, I added blk_drain_queue() and related calls to the
freeze handler, that was missed earlier.
> 2) Does it stop more I/O from reaching do_virtblk_request during freeze?
> If not, we need to.
Added blk_stop_queue() and blk_start_queue() calls to ensure this.
> If we need to save and restore requests, I don't think we should do this
> on a per-driver basis, but try to do it in the core.
Agreed, however currently we don't save and restore any pending vq
items. If it is necessary, we should do it in common code (earlier
version of this patchset did that). I think we can get better results
by flushing the vq instead of trying to save/restore elements.
Amit
parent reply other threads:[~2011-11-15 12:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8739f9ipsi.fsf@rustcorp.com.au>]
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=20111115125246.GB26378@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--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