Hi, > -----Original Message----- > From: Bing Zhao <[email protected]> > Sent: Friday, June 30, 2023 3:42 PM > To: Matan Azrad <[email protected]>; Slava Ovsiienko > <[email protected]>; Ori Kam <[email protected]>; Suanming Mou > <[email protected]>; Raslan Darawsheh <[email protected]> > Cc: [email protected]; Rongwei Liu <[email protected]>; [email protected] > Subject: [PATCH] common/mlx5: fix obtaining IB device in LAG mode > > In hardware LAG mode, both PFs are in the same E-Switch domain but the VFs > are in the other domains. Moreover, VF has its own dedicated IB device. > > When probing a VF created on the 1st PF, usually its PCIe address is the same > as the PF's except the function part. Then there would be some wrong VF BDF > match on the IB "bond" device due to incomplete comparison (we do not > compare the function part of BDF for bonding devices to match all bonded > PFs). > > Adding one extra condition to check whether the current PCIe address device > is a VF will solve the incorrect IB device recognition. Thus the full address > comparison will be done. > > Fixes: f956d3d4c33c ("net/mlx5: fix probing with secondary bonding > member") > Cc: [email protected] > Cc: [email protected] > > Signed-off-by: Bing Zhao <[email protected]> > Acked-by: Viacheslav Ovsiienko <[email protected]>
Patch applied to next-net-mlx, Kindest regards, Raslan Darawsheh
