From: Dragos Tatulea <dtatulea@nvidia.com>
To: "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Eugenio Perez Martin <eperezma@redhat.com>,
Si-Wei Liu <si-wei.liu@oracle.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
<virtualization@lists.linux-foundation.org>
Cc: Dragos Tatulea <dtatulea@nvidia.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Gal Pressman <galp@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: [PATCH vhost 0/7] vdpa/mlx5: Add support for resumable vqs
Date: Fri, 1 Dec 2023 12:48:50 +0200 [thread overview]
Message-ID: <20231201104857.665737-1-dtatulea@nvidia.com> (raw)
Add support for resumable vqs in the driver. This is a firmware feature
that can be used for the following benefits:
- Full device .suspend/.resume.
- .set_map doesn't need to destroy and create new vqs anymore just to
update the map. When resumable vqs are supported it is enough to
suspend the vqs, set the new maps, and then resume the vqs.
The first patch exposes the relevant bits in mlx5_ifc.h. That means it
needs to be applied to the mlx5-vhost tree [0] first. Once applied
there, the change has to be pulled from mlx5-vhost into the vhost tree
and only then the remaining patches can be applied. Same flow as the vq
descriptor mappings patchset [1].
To be able to use resumable vqs properly, support for selectively modifying
vq parameters was needed. This is what the middle part of the series
consists of.
[0] https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/log/?h=mlx5-vhost
[1] https://lore.kernel.org/virtualization/20231018171456.1624030-2-dtatulea@nvidia.com/
Dragos Tatulea (7):
vdpa/mlx5: Expose resumable vq capability
vdpa/mlx5: Split function into locked and unlocked variants
vdpa/mlx5: Allow modifying multiple vq fields in one modify command
vdpa/mlx5: Introduce per vq and device resume
vdpa/mlx5: Mark vq addrs for modification in hw vq
vdpa/mlx5: Mark vq state for modification in hw vq
vdpa/mlx5: Use vq suspend/resume during .set_map
drivers/vdpa/mlx5/core/mr.c | 31 +++---
drivers/vdpa/mlx5/net/mlx5_vnet.c | 172 +++++++++++++++++++++++++----
include/linux/mlx5/mlx5_ifc.h | 3 +-
include/linux/mlx5/mlx5_ifc_vdpa.h | 4 +
4 files changed, 174 insertions(+), 36 deletions(-)
--
2.42.0
next reply other threads:[~2023-12-01 10:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:48 Dragos Tatulea [this message]
2023-12-01 10:48 ` [PATCH mlx5-vhost 1/7] vdpa/mlx5: Expose resumable vq capability Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 2/7] vdpa/mlx5: Split function into locked and unlocked variants Dragos Tatulea
2023-12-01 11:46 ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 3/7] vdpa/mlx5: Allow modifying multiple vq fields in one modify command Dragos Tatulea
2023-12-01 14:47 ` Eugenio Perez Martin
2023-12-01 15:26 ` Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 4/7] vdpa/mlx5: Introduce per vq and device resume Dragos Tatulea
2023-12-01 14:51 ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 5/7] vdpa/mlx5: Mark vq addrs for modification in hw vq Dragos Tatulea
2023-12-01 10:48 ` [PATCH vhost 6/7] vdpa/mlx5: Mark vq state " Dragos Tatulea
2023-12-01 15:18 ` Eugenio Perez Martin
2023-12-01 10:48 ` [PATCH vhost 7/7] vdpa/mlx5: Use vq suspend/resume during .set_map Dragos Tatulea
2023-12-02 20:26 ` [PATCH vhost 0/7] vdpa/mlx5: Add support for resumable vqs Michael S. Tsirkin
2023-12-03 15:21 ` Dragos Tatulea
2023-12-03 16:23 ` Michael S. Tsirkin
2023-12-04 8:53 ` Dragos Tatulea
2023-12-04 8:55 ` Michael S. Tsirkin
2023-12-04 9:16 ` Dragos Tatulea
2023-12-04 11:04 ` Michael S. Tsirkin
2023-12-04 11:18 ` Dragos Tatulea
2023-12-04 13:10 ` (subset) " Leon Romanovsky
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=20231201104857.665737-1-dtatulea@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=eperezma@redhat.com \
--cc=galp@nvidia.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=si-wei.liu@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xuanzhuo@linux.alibaba.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
all inboxes | Powered by JetHome®