[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211013180651.GM2744544@nvidia.com>
Date: Wed, 13 Oct 2021 15:06:51 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Yishai Hadas <yishaih@...dia.com>
Cc: alex.williamson@...hat.com, bhelgaas@...gle.com, saeedm@...dia.com,
linux-pci@...r.kernel.org, kvm@...r.kernel.org,
netdev@...r.kernel.org, kuba@...nel.org, leonro@...dia.com,
kwankhede@...dia.com, mgurtovoy@...dia.com, maorg@...dia.com
Subject: Re: [PATCH V1 mlx5-next 13/13] vfio/mlx5: Trap device RESET and
update state accordingly
On Wed, Oct 13, 2021 at 12:47:07PM +0300, Yishai Hadas wrote:
> Trap device RESET and update state accordingly, it's done by registering
> the matching callbacks.
>
> Signed-off-by: Yishai Hadas <yishaih@...dia.com>
> Signed-off-by: Leon Romanovsky <leonro@...dia.com>
> drivers/vfio/pci/mlx5/main.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/pci/mlx5/main.c b/drivers/vfio/pci/mlx5/main.c
> index e36302b444a6..8fe44ed13552 100644
> +++ b/drivers/vfio/pci/mlx5/main.c
> @@ -613,6 +613,19 @@ static const struct vfio_device_ops mlx5vf_pci_ops = {
> .match = vfio_pci_core_match,
> };
>
> +static void mlx5vf_reset_done(struct vfio_pci_core_device *core_vdev)
> +{
> + struct mlx5vf_pci_core_device *mvdev = container_of(
> + core_vdev, struct mlx5vf_pci_core_device,
> + core_device);
> +
> + mvdev->vmig.vfio_dev_state = VFIO_DEVICE_STATE_RUNNING;
This should hold the state mutex too
Jason
Powered by blists - more mailing lists