From: Sukrit Bhatnagar <skrtbhtngr@gmail.com>
To: qemu-devel@nongnu.org
Cc: Yuval Shaia <yuval.shaia@oracle.com>
Subject: [Qemu-devel] [RFC v2 0/2] Add live migration support in the PVRDMA device
Date: Sat, 6 Jul 2019 09:39:38 +0530 [thread overview]
Message-ID: <20190706040940.7884-1-skrtbhtngr@gmail.com> (raw)
Changes in v2:
* Modify load_dsr() such that dsr mapping is not performed if dsr value
is non-NULL. Also move free_dsr() out of load_dsr() and call it right
before if needed. These two changes will allow us to call load_dsr()
even when we have already done dsr mapping and would like to go on
with the rest of mappings.
* Use VMStateDescription instead of SaveVMHandlers to describe migration
state. Also add fields for parent PCI object and MSIX.
* Use a temporary structure (struct PVRDMAMigTmp) to hold some fields
during migration. These fields, such as cmd_slot_dma and resp_slot_dma
inside dsr, do not fit into VMSTATE macros as their container
(dsr_info->dsr) will not be ready until it is mapped on the dest.
* Perform mappings to CQ and event notification rings after the state is
loaded. This is an extension to the mappings performed in v1;
following the flow of load_dsr(). All the mappings are succesfully
done on the dest on state load.
Link(s) to v1:
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg04924.html
https://lists.gnu.org/archive/html/qemu-devel/2019-06/msg04923.html
Things working now (were not working at the time of v1):
* vmxnet3 is migrating successfully. The issue was in the migration of
its PCI configuration space, and is solved by the patch Marcel had sent:
https://lists.gnu.org/archive/html/qemu-devel/2019-07/msg01500.html
* There is no problem due to BounceBuffers which were failing the dma mapping
calls in state load logic earlier. Not sure exactly how it went away. I am
guessing that adding the PCI and MSIX state to migration solved the issue.
What is still needed:
* A workaround to get libvirt to support same-host migration. Since
the problems faced in v1 (mentioned above) are out of the way, we
can move further, and in doing so, we will need this.
Sukrit Bhatnagar (2):
hw/pvrdma: make DSR mapping idempotent in load_dsr()
hw/pvrdma: add live migration support
hw/rdma/vmw/pvrdma_main.c | 104 +++++++++++++++++++++++++++++++++++---
1 file changed, 96 insertions(+), 8 deletions(-)
--
2.21.0
next reply other threads:[~2019-07-06 4:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 4:09 Sukrit Bhatnagar [this message]
2019-07-06 4:09 ` [Qemu-devel] [RFC v2 1/2] hw/pvrdma: make DSR mapping idempotent in load_dsr() Sukrit Bhatnagar
2019-07-06 4:09 ` [Qemu-devel] [RFC v2 2/2] hw/pvrdma: add live migration support Sukrit Bhatnagar
2019-07-08 5:13 ` Yuval Shaia
2019-07-10 20:14 ` Sukrit Bhatnagar
2019-07-06 19:04 ` [Qemu-devel] [RFC v2 0/2] Add live migration support in the PVRDMA device Marcel Apfelbaum
2019-07-08 9:38 ` Daniel P. Berrangé
2019-07-08 18:58 ` Marcel Apfelbaum
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=20190706040940.7884-1-skrtbhtngr@gmail.com \
--to=skrtbhtngr@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yuval.shaia@oracle.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).