From: Leon Romanovsky <leon@kernel.org>
To: alex.williamson@redhat.com
Cc: jgg@nvidia.com, saeedm@nvidia.com,
Yishai Hadas <yishaih@nvidia.com>,
kvm@vger.kernel.org, netdev@vger.kernel.org, kuba@kernel.org,
maorg@nvidia.com, cohuck@redhat.com,
Leon Romanovsky <leonro@nvidia.com>
Subject: [GIT PULL] Please pull mlx5 vfio changes
Date: Tue, 10 May 2022 16:12:36 +0300 [thread overview]
Message-ID: <20220510131236.1039430-1-leon@kernel.org> (raw)
The following changes since commit 2984287c4c19949d7eb451dcad0bd5c54a2a376f:
net/mlx5: Remove not-implemented IPsec capabilities (2022-04-09 08:25:07 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/ tags/mlx5-lm-parallel
for you to fetch changes up to 4d67783344e8380ec3c0810e4f67c003646ccd7e:
vfio/mlx5: Run the SAVE state command in an async mode (2022-05-10 15:46:42 +0300)
----------------------------------------------------------------
Improve mlx5 live migration driver
From Yishai:
This series improves mlx5 live migration driver in few aspects as of
below.
Refactor to enable running migration commands in parallel over the PF
command interface.
To achieve that we exposed from mlx5_core an API to let the VF be
notified before that the PF command interface goes down/up. (e.g. PF
reload upon health recovery).
Once having the above functionality in place mlx5 vfio doesn't need any
more to obtain the global PF lock upon using the command interface but
can rely on the above mechanism to be in sync with the PF.
This can enable parallel VFs migration over the PF command interface
from kernel driver point of view.
In addition,
Moved to use the PF async command mode for the SAVE state command.
This enables returning earlier to user space upon issuing successfully
the command and improve latency by let things run in parallel.
Alex, as this series touches mlx5_core we may need to send this in a
pull request format to VFIO to avoid conflicts before acceptance.
Link: https://lore.kernel.org/all/20220510090206.90374-1-yishaih@nvidia.com
Signed-of-by: Leon Romanovsky <leonro@nvidia.com>
----------------------------------------------------------------
Yishai Hadas (4):
net/mlx5: Expose mlx5_sriov_blocking_notifier_register / unregister APIs
vfio/mlx5: Manage the VF attach/detach callback from the PF
vfio/mlx5: Refactor to enable VFs migration in parallel
vfio/mlx5: Run the SAVE state command in an async mode
drivers/net/ethernet/mellanox/mlx5/core/sriov.c | 65 ++++++-
drivers/vfio/pci/mlx5/cmd.c | 236 ++++++++++++++++++------
drivers/vfio/pci/mlx5/cmd.h | 52 +++++-
drivers/vfio/pci/mlx5/main.c | 122 +++++-------
include/linux/mlx5/driver.h | 12 ++
5 files changed, 351 insertions(+), 136 deletions(-)
next reply other threads:[~2022-05-10 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 13:12 Leon Romanovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-09-07 9:43 [GIT PULL] Please pull mlx5 vfio changes Leon Romanovsky
2022-09-07 19:21 ` Alex Williamson
2022-09-08 6:31 ` Leon Romanovsky
2022-09-08 16:53 ` Alex Williamson
2022-09-08 17:31 ` Yishai Hadas
2022-09-08 18:00 ` Alex Williamson
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=20220510131236.1039430-1-leon@kernel.org \
--to=leon@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=yishaih@nvidia.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).