From: Jiri Pirko <jiri@resnulli.us>
To: Shay Drory <shayd@nvidia.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
danielj@nvidia.com, yishaih@nvidia.com, jiri@nvidia.com,
saeedm@nvidia.com, parav@nvidia.com
Subject: Re: [PATCH net-next V2 7/8] devlink: Expose port function commands to control migratable
Date: Fri, 2 Dec 2022 10:02:43 +0100 [thread overview]
Message-ID: <Y4m/M+jeF+CBqTyW@nanopsycho> (raw)
In-Reply-To: <20221202082622.57765-8-shayd@nvidia.com>
Fri, Dec 02, 2022 at 09:26:21AM CET, shayd@nvidia.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@nvidia.com>
>Reviewed-by: Jiri Pirko <jiri@nvidia.com>
>Reported-by: kernel test robot <lkp@intel.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.
next prev parent reply other threads:[~2022-12-02 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 8:26 [PATCH net-next V2 0/8] devlink: Add port function attribute to enable/disable Roce and migratable Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 1/8] net/mlx5: Introduce IFC bits for migratable Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 2/8] devlink: Validate port function request Shay Drory
2022-12-02 18:42 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 3/8] devlink: Move devlink port function hw_addr attr documentation Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 4/8] devlink: Expose port function commands to control RoCE Shay Drory
2022-12-02 18:56 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 5/8] net/mlx5: Add generic getters for other functions caps Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 6/8] net/mlx5: E-Switch, Implement devlink port function cmds to control RoCE Shay Drory
2022-12-02 8:26 ` [PATCH net-next V2 7/8] devlink: Expose port function commands to control migratable Shay Drory
2022-12-02 9:02 ` Jiri Pirko [this message]
2022-12-02 18:39 ` Jakub Kicinski
2022-12-04 9:31 ` Shay Drory
2022-12-02 17:26 ` kernel test robot
2022-12-02 18:58 ` Jakub Kicinski
2022-12-02 8:26 ` [PATCH net-next V2 8/8] net/mlx5: E-Switch, Implement devlink port function cmds " Shay Drory
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=Y4m/M+jeF+CBqTyW@nanopsycho \
--to=jiri@resnulli.us \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@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).