Bug 1678276

Summary: [Broadcom CCX 8.1 FEAT]libbnxt_re: Add support for Broadcom 57500 adapters in user library
Product: Red Hat Enterprise Linux 8 Reporter: Selvin Xavier (Broadcom) <sxavier>
Component: rdma-coreAssignee: Jarod Wilson <jarod>
Status: CLOSED ERRATA QA Contact: Afom T. Michael <tmichael>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: anantha.subramanyam, brcm-roce-dev.pdl, hwkernel-mgr, infiniband-qe, jarod, jfeeney, jshortt, laurie.barry, rdma-dev-team, selvin.xavier, wchadwic
Target Milestone: rcKeywords: OtherQA
Target Release: 8.1Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rdma-core-22.3-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:22:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Selvin Xavier (Broadcom) 2019-02-18 12:10:08 UTC
Following patch is under review on the rdma community:

https://marc.info/?l=linux-rdma&m=155003698431927&w=2
https://github.com/linux-rdma/rdma-core/pull/453

Will update the git-tag number once the patch is pulled in.

Comment 1 Jarod Wilson 2019-06-24 17:23:11 UTC
(In reply to Selvin Xavier from comment #0)
> Following patch is under review on the rdma community:
> 
> https://marc.info/?l=linux-rdma&m=155003698431927&w=2
> https://github.com/linux-rdma/rdma-core/pull/453
> 
> Will update the git-tag number once the patch is pulled in.

This bug was overlooked for 8.1 until now, partially because it was waiting on that update. I'm pretty sure we did that enablement for RHEL-7.7 already though, so I'd like to get it done for 8.1 as well.

Comment 3 Selvin Xavier (Broadcom) 2019-06-25 06:16:42 UTC
Thanks Jarod. Actually i missed updating the 8.1 BZ when i updated the same info on 7.7 BZ.
As you mentioned, its already enabled in 7.7 and we have validated the same. 

Thanks,
Selvin

Comment 9 Afom T. Michael 2019-08-30 18:37:42 UTC
Moving to verified as our libibverbs-utils test has passed.

[root@rdma-dev-16 ~]$ cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.1 Beta (Ootpa)
[root@rdma-dev-16 ~]$ uname -r
4.18.0-135.el8.x86_64
[root@rdma-dev-16 ~]$ rpm -qa | grep -E 'rdma|verbs'
rdma-core-devel-22.3-1.el8.x86_64
librdmacm-22.3-1.el8.x86_64
librdmacm-utils-22.3-1.el8.x86_64
rdma-core-22.3-1.el8.x86_64
libibverbs-22.3-1.el8.x86_64
libibverbs-utils-22.3-1.el8.x86_64
[root@rdma-dev-16 ~]$ rpm -ql libibverbs-22.3-1.el8.x86_64 | grep bnxt
/etc/libibverbs.d/bnxt_re.driver
/usr/lib64/libibverbs/libbnxt_re-rdmav22.so
[root@rdma-dev-16 ~]$ echo $HCA_ABRV 
BCM57500
[root@rdma-dev-16 ~]$ ibv_devinfo 
hca_id:	bnxt_re0
	transport:			InfiniBand (0)
	fw_ver:				215.0.170.0
	node_guid:			b226:28ff:fe4b:cd80
	sys_image_guid:			b226:28ff:fe4b:cd80
	vendor_id:			0x14e4
	vendor_part_id:			5968
	hw_ver:				0x2100
	phys_port_cnt:			1
		port:	1
			state:			PORT_ACTIVE (4)
			max_mtu:		4096 (5)
			active_mtu:		4096 (5)
			sm_lid:			0
			port_lid:		0
			port_lmc:		0x00
			link_layer:		Ethernet

hca_id:	bnxt_re1
	transport:			InfiniBand (0)
	fw_ver:				215.0.170.0
	node_guid:			b226:28ff:fe4b:cd81
	sys_image_guid:			b226:28ff:fe4b:cd81
	vendor_id:			0x14e4
	vendor_part_id:			5968
	hw_ver:				0x2100
	phys_port_cnt:			1
		port:	1
			state:			PORT_DOWN (1)
			max_mtu:		4096 (5)
			active_mtu:		1024 (3)
			sm_lid:			0
			port_lid:		0
			port_lmc:		0x00
			link_layer:		Ethernet

[root@rdma-dev-16 ~]$

Test results for libibverbs-utils on rdma-dev-16:
4.18.0-135.el8.x86_64, bnxt, roce, & bnxt_re0
    Result | Status | Test
  ---------+--------+------------------------------------
      PASS |      0 | ibv_devices
      PASS |      0 | ibv_devinfo
      PASS |      0 | ibv_rc_pingpong
      PASS |      0 | ibv_srq_pingpong
      PASS |      0 | ibv_ud_pingpong

Comment 11 errata-xmlrpc 2019-11-05 22:22:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3585