From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: quintela@redhat.com, Alexey Kardashevskiy <aik@ozlabs.ru>,
agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 7/8] pseries: savevm support for PAPR virtual SCSI
Date: Fri, 31 May 2013 20:07:55 +1000 [thread overview]
Message-ID: <1369994875.3928.137.camel@pasglop> (raw)
In-Reply-To: <51A83C18.2030102@ozlabs.ru>
On Fri, 2013-05-31 at 15:58 +1000, Alexey Kardashevskiy wrote:
>
> And another question (sorry I am not very familiar with terminology but
> cc:Ben is :) ) - what happens with indirect requests if migration happened
> in the middle of handling such a request? virtio-scsi does not seem to
> handle this situation anyhow, it just reconstructs the whole request and
> that's it.
So Paolo, the crux of the question here is really whether we have any
guarantee about the state of the request when this happens (by this I
mean a save happening with requests still "in flight") ?
IE. Can the request can be at any stage of processing, with the data
transfer phase being half way through, or do we somewhat know for sure
that the request will *not* have started transferring any data ?
This is key, because in the latter case, all we really need to do is
save the request itself, and re-parse it on restore as if it was
new really (at least from a DMA descriptor perspective).
However, if the data transfer is already half way through, we need to
somewhat save the state of the data transfer machinery, ie. the position
of the "cursor" that follows the guest-provided DMA descriptor list,
etc... (which isn't *that* trivial since we have a concept of indirect
descriptors and we use pointers to follow them, so we'd probably have
to re-walk the whole user descriptors list until we reach the same position).
Cheers,
Ben.
next prev parent reply other threads:[~2013-05-31 10:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 1:38 [Qemu-devel] [0/8] pseries: savevm / migration support David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 1/8] savevm: Implement VMS_DIVIDE flag David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 2/8] target-ppc: Convert ppc cpu savevm to VMStateDescription David Gibson
2013-05-03 11:29 ` Andreas Färber
2013-05-03 14:26 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 3/8] pseries: savevm support for XICS interrupt controller David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 4/8] pseries: savevm support for VIO devices David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 5/8] pseries: savevm support for PAPR VIO logical lan David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 6/8] pseries: savevm support for PAPR TCE tables David Gibson
2013-05-03 1:38 ` [Qemu-devel] [PATCH 7/8] pseries: savevm support for PAPR virtual SCSI David Gibson
2013-05-06 7:37 ` Paolo Bonzini
2013-05-07 3:07 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2013-05-27 6:48 ` [Qemu-devel] " Alexey Kardashevskiy
2013-05-27 7:03 ` Paolo Bonzini
2013-05-31 5:58 ` Alexey Kardashevskiy
2013-05-31 8:18 ` Paolo Bonzini
2013-05-31 10:12 ` Alexey Kardashevskiy
2013-05-31 10:26 ` Paolo Bonzini
2013-05-31 10:33 ` Alexey Kardashevskiy
2013-05-31 10:34 ` Paolo Bonzini
2013-05-31 10:07 ` Benjamin Herrenschmidt [this message]
2013-05-31 10:25 ` Alexey Kardashevskiy
2013-05-31 10:41 ` Paolo Bonzini
2013-06-01 0:01 ` Benjamin Herrenschmidt
2013-06-03 6:21 ` Paolo Bonzini
2013-06-03 5:46 ` Alexey Kardashevskiy
2013-06-03 6:23 ` Paolo Bonzini
2013-06-03 8:07 ` Benjamin Herrenschmidt
2013-06-03 9:37 ` Alexey Kardashevskiy
2013-06-03 9:41 ` Paolo Bonzini
2013-05-03 1:38 ` [Qemu-devel] [PATCH 8/8] pseries: savevm support for pseries machine David Gibson
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=1369994875.3928.137.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=quintela@redhat.com \
/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).