From: Eli Cohen <elic@nvidia.com>
To: <eperezma@redhat.com>, <jasowang@redhat.com>, <mst@redhat.com>,
<virtualization@lists.linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <si-wei.liu@oracle.com>,
<parav@nvidia.com>, Eli Cohen <elic@nvidia.com>
Subject: [PATCH RFC v1 0/3] Support live migration with mlx5_vdpa
Date: Mon, 20 Jun 2022 16:06:11 +0300 [thread overview]
Message-ID: <20220620130614.19679-1-elic@nvidia.com> (raw)
Hi all,
I am sending this patch set with adressing some of the comments.
Please note that I will be on vacation for the next three weeks so any
comments will be addressed after I return.
Eugenio and myself were able to actually see live migation working over
mlx5_vdpa so that's a good sign too :-)
Following patchset supports the suspend callback to suspend VQs to allow
sshdow VQs to kick in. It also adds address space support also required
for live migration. We use two groups, one for the control virtqueue and
one for the data virtqueues.
Finally there is a patch that disables VLAN support since it is not
supported currently.
The aim of this patchset is to enable development/testing of live
migration over a real hardware device.
The below two patches are also required to be applied but I did not
include them in the series since they were sent separately.
https://lore.kernel.org/all/20220613075958.511064-1-elic@nvidia.com/T/
https://lore.kernel.org/all/20220613075958.511064-2-elic@nvidia.com/T/
v0 -> v1:
1. Fix a few typos
2. handle memory map updates for all groups with a given asid.
Eli Cohen (3):
vdpa/mlx5: Implement susupend virtqueue callback
vdpa/mlx5: Support different address spaces for control and data
vdpa/mlx5: Disable VLAN support to support live migration
drivers/vdpa/mlx5/core/mlx5_vdpa.h | 11 ++
drivers/vdpa/mlx5/net/mlx5_vnet.c | 157 ++++++++++++++++++++++++++---
include/linux/mlx5/mlx5_ifc_vdpa.h | 8 ++
3 files changed, 163 insertions(+), 13 deletions(-)
--
2.35.1
next reply other threads:[~2022-06-20 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:06 Eli Cohen [this message]
2022-06-20 13:06 ` [PATCH RFC v1 1/3] vdpa/mlx5: Implement susupend virtqueue callback Eli Cohen
2022-06-20 13:06 ` [PATCH RFC v1 2/3] vdpa/mlx5: Support different address spaces for control and data Eli Cohen
2022-06-20 13:06 ` [PATCH RFC v1 3/3] vdpa/mlx5: Disable VLAN support to support live migration Eli Cohen
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=20220620130614.19679-1-elic@nvidia.com \
--to=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=si-wei.liu@oracle.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