Add kernel config for NVIDIA DPU/ConnectX adapter

[l8huang]

With Nvidia DPU or ConnectX network adapter, VF can do VFIO passthrough to guest VM in guest-kernel mode. In the guest kernel, the adapter's driver is required to claim the VFIO device and create network interface.

[l8huang]

FYI: in the guest VM:

root@localhost:/proc# lspci  -tv
-[0000:00]-+-00.0  Device 8086:29c0
           +-01.0  Device 1af4:1003
           +-02.0-[01]--
           +-03.0  Device 1af4:1004
           +-04.0  Device 1af4:1005
           +-05.0-[02]----00.0  Device 15b3:101e
           +-06.0-[03]--
           +-07.0  Device 1af4:1053
           +-08.0  Device 1af4:1009
           +-1f.0  Device 8086:2918
           +-1f.2  Device 8086:2922
           \-1f.3  Device 8086:2930

root@localhost:/proc# lspci -nn -k -s 0000:02:00.0
02:00.0 Class [0200]: Device [15b3:101e] (rev 01)
	Subsystem: Device [15b3:0063]
	Kernel driver in use: mlx5_core

root@localhost:/proc# ethtool -i eth0 
driver: mlx5_core
version: 6.1.62-nvidia-gpu
firmware-version: 24.35.3502 (MT_0000000542)
expansion-rom-version: 
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

[l8huang]

@zvonkok PR updated, PTAL, thanks

[zvonkok]

@l8huang You need to bump tools/packaging/kernel/kata_config_version

[l8huang]

@l8huang You need to bump tools/packaging/kernel/kata_config_version

Thanks for the heads up, version updated.

[zvonkok]

LGTM, thanks!

[l8huang]

@lifupan @fidencio @GabyCT need another LGTM, could you please take a look? thanks

[amshinde]

@l8huang I see that this PR is for adding kernel configs for NVIDIA Mellanox ConnectX network adaptor. While the PR looks good overall, the usage of NVIDIA here and in tools/packaging/kernel/configs/fragments/dpu/nvidia.conf file name you added is slightly confusing, also due to the fact we have fragments present for NVIDIA gpu as well.

Since the configs added in the fragment here have Mellonox/MLX in the name, can we rename this to Mellanox instead to reduce confusion.

I am suggesting to replace
-D : DPU/SmartNIC vendor, only NVIDIA. => -D : DPU/SmartNIC vendor, only Mellanox.

cc @zvonkok @fidencio

[l8huang]

-D : DPU/SmartNIC vendor, only NVIDIA. => -D : DPU/SmartNIC vendor, only Mellanox.

@amshinde Mellanox was acquired by NVIDIA, the products are named under NVIDIA now.

[amshinde]

-D : DPU/SmartNIC vendor, only NVIDIA. => -D : DPU/SmartNIC vendor, only Mellanox.

@amshinde Mellanox was acquired by NVIDIA, the products are named under NVIDIA now.

@l8huang I understand that, I suggested the rename to Mellanox to avoid confusion with Nvidia GPU, and since the kernel configs refer to Mellanox rather than Nvidia.

[l8huang]

According to https://en.wikipedia.org/wiki/Mellanox_Technologies:

The company was integrated into Nvidia's networking division in 2020 and Nvidia stopped using the brand name "Mellanox" for its new networking products.

If one googles Mellanox Technologies, the top results point to NVIDIA.

TBH: I don't see too much confusion, the option says the DPU/SmartNIC vendor. We should move beyond historical legacies, looking forward NVIDIA is the de facto vendor.

@zvonkok what do you think?

[l8huang]

@amshinde Would you mind merging this PR as it is? If any confusion arises later, I will address and amend it accordingly.

[amshinde]

@l8huang There is a merge conflict now, can you rebase this PR?

[l8huang]

@amshinde thanks for heads up, just rebased.