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 3/3] vdpa/mlx5: Disable VLAN support to support live migration
Date: Mon, 20 Jun 2022 16:06:14 +0300 [thread overview]
Message-ID: <20220620130614.19679-4-elic@nvidia.com> (raw)
In-Reply-To: <20220620130614.19679-1-elic@nvidia.com>
Current qemu code does not support live migration for devices supporting
VLAN. Disable it.
Note: this patch is provided just to enable testing with current qemu.
Signed-off-by: Eli Cohen <elic@nvidia.com>
---
drivers/vdpa/mlx5/net/mlx5_vnet.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/vdpa/mlx5/net/mlx5_vnet.c b/drivers/vdpa/mlx5/net/mlx5_vnet.c
index cb637dee2ea8..a468e02fd869 100644
--- a/drivers/vdpa/mlx5/net/mlx5_vnet.c
+++ b/drivers/vdpa/mlx5/net/mlx5_vnet.c
@@ -2172,7 +2172,6 @@ static u64 get_supported_features(struct mlx5_core_dev *mdev)
mlx_vdpa_features |= BIT_ULL(VIRTIO_NET_F_MQ);
mlx_vdpa_features |= BIT_ULL(VIRTIO_NET_F_STATUS);
mlx_vdpa_features |= BIT_ULL(VIRTIO_NET_F_MTU);
- mlx_vdpa_features |= BIT_ULL(VIRTIO_NET_F_CTRL_VLAN);
return mlx_vdpa_features;
}
--
2.35.1
prev parent reply other threads:[~2022-06-20 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 13:06 [PATCH RFC v1 0/3] Support live migration with mlx5_vdpa Eli Cohen
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 ` Eli Cohen [this message]
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-4-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