From: Jason Gunthorpe <jgg@nvidia.com>
To: Yishai Hadas <yishaih@nvidia.com>
Cc: alex.williamson@redhat.com, saeedm@nvidia.com,
kvm@vger.kernel.org, netdev@vger.kernel.org, kuba@kernel.org,
leonro@nvidia.com, maorg@nvidia.com, cohuck@redhat.com
Subject: Re: [PATCH mlx5-next 2/5] net/mlx5: Expose mlx5_sriov_blocking_notifier_register / unregister APIs
Date: Wed, 4 May 2022 10:55:57 -0300 [thread overview]
Message-ID: <20220504135557.GF49344@nvidia.com> (raw)
In-Reply-To: <20220427093120.161402-3-yishaih@nvidia.com>
On Wed, Apr 27, 2022 at 12:31:17PM +0300, Yishai Hadas wrote:
> Expose mlx5_sriov_blocking_notifier_register / unregister APIs to let a
> VF register to be notified for its enablement / disablement by the PF.
>
> Upon VF probe it will call mlx5_sriov_blocking_notifier_register() with
> its notifier block and upon VF remove it will call
> mlx5_sriov_blocking_notifier_unregister() to drop its registration.
>
> This can give a VF the ability to clean some resources upon disable
> before that the command interface goes down and on the other hand sets
> some stuff before that it's enabled.
>
> This may be used by a VF which is migration capable in few cases.(e.g.
> PF load/unload upon an health recovery).
>
> Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
> ---
> .../net/ethernet/mellanox/mlx5/core/sriov.c | 65 ++++++++++++++++++-
> include/linux/mlx5/driver.h | 12 ++++
> 2 files changed, 76 insertions(+), 1 deletion(-)
This patch needs to be first and be on the mlx5 shared branch
Jason
next prev parent reply other threads:[~2022-05-04 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 9:31 [PATCH mlx5-next 0/5] Improve mlx5 live migration driver Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 1/5] vfio/mlx5: Reorganize the VF is migratable code Yishai Hadas
2022-05-04 20:13 ` Alex Williamson
2022-05-08 12:56 ` Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 2/5] net/mlx5: Expose mlx5_sriov_blocking_notifier_register / unregister APIs Yishai Hadas
2022-05-04 13:55 ` Jason Gunthorpe [this message]
2022-04-27 9:31 ` [PATCH mlx5-next 3/5] vfio/mlx5: Manage the VF attach/detach callback from the PF Yishai Hadas
2022-05-04 20:34 ` Alex Williamson
2022-05-08 13:04 ` Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 4/5] vfio/mlx5: Refactor to enable VFs migration in parallel Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 5/5] vfio/mlx5: Run the SAVE state command in an async mode Yishai Hadas
2022-05-04 13:29 ` [PATCH mlx5-next 0/5] Improve mlx5 live migration driver Yishai Hadas
2022-05-04 20:19 ` Alex Williamson
2022-05-04 21:33 ` Jason Gunthorpe
2022-05-04 22:48 ` Alex Williamson
2022-05-05 5:38 ` 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=20220504135557.GF49344@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.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).