[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4m/M+jeF+CBqTyW@nanopsycho>
Date: Fri, 2 Dec 2022 10:02:43 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Shay Drory <shayd@...dia.com>
Cc: netdev@...r.kernel.org, kuba@...nel.org, davem@...emloft.net,
danielj@...dia.com, yishaih@...dia.com, jiri@...dia.com,
saeedm@...dia.com, parav@...dia.com
Subject: Re: [PATCH net-next V2 7/8] devlink: Expose port function commands
to control migratable
Fri, Dec 02, 2022 at 09:26:21AM CET, shayd@...dia.com wrote:
>Expose port function commands to enable / disable migratable
>capability, this is used to set the port function as migratable.
>
>Live migration is the process of transferring a live virtual machine
>from one physical host to another without disrupting its normal
>operation.
>
>In order for a VM to be able to perform LM, all the VM components must
>be able to perform migration. e.g.: to be migratable.
>In order for VF to be migratable, VF must be bound to VFIO driver with
>migration support.
>
>When migratable capability is enable for a function of the port, the
>device is making the necessary preparations for the function to be
>migratable, which might include disabling features which cannot be
>migrated.
>
>Example of LM with migratable function configuration:
>Set migratable of the VF's port function.
>
>$ devlink port show pci/0000:06:00.0/2
>pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0
>vfnum 1
> function:
> hw_addr 00:00:00:00:00:00 migratable disable
>
>$ devlink port function set pci/0000:06:00.0/2 migratable enable
>
>$ devlink port show pci/0000:06:00.0/2
>pci/0000:06:00.0/2: type eth netdev enp6s0pf0vf1 flavour pcivf pfnum 0
>vfnum 1
> function:
> hw_addr 00:00:00:00:00:00 migratable enable
>
>Bind VF to VFIO driver with migration support:
>$ echo <pci_id> > /sys/bus/pci/devices/0000:08:00.0/driver/unbind
>$ echo mlx5_vfio_pci > /sys/bus/pci/devices/0000:08:00.0/driver_override
>$ echo <pci_id> > /sys/bus/pci/devices/0000:08:00.0/driver/bind
>
>Attach VF to the VM.
>Start the VM.
>Perform LM.
>
>Signed-off-by: Shay Drory <shayd@...dia.com>
>Reviewed-by: Jiri Pirko <jiri@...dia.com>
>Reported-by: kernel test robot <lkp@...el.com>
I believe that you put reported by only to patches that fix the reported
issue which exists in-tree. It does not apply to issues found on
a submitted patch.
Powered by blists - more mailing lists