1. 22 2月, 2019 1 次提交
  2. 21 2月, 2019 1 次提交
  3. 20 2月, 2019 4 次提交
    • W
      iw_cxgb4: Make function read_tcb() static · 3b8f8b95
      Wei Yongjun 提交于
      Fixes the following sparse warning:
      
      drivers/infiniband/hw/cxgb4/cm.c:658:6: warning:
       symbol 'read_tcb' was not declared. Should it be static?
      
      Fixes: 11a27e21 ("iw_cxgb4: complete the cached SRQ buffers")
      Signed-off-by: NWei Yongjun <weiyongjun1@huawei.com>
      Acked-by: NRaju Rangoju <rajur@chelsio.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      3b8f8b95
    • Y
      RDMA/hns: Bugfix for set hem of SCC · 6ac16e40
      Yangyang Li 提交于
      The method of set hem for scc context is different from other contexts. It
      should notify the hardware with the detailed idx in bt0 for scc, while for
      other contexts, it only need to notify the bt step and the hardware will
      calculate the idx.
      
      Here fixes the following error when unloading the hip08 driver:
      
      [  123.570768] {1}[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 0
      [  123.579023] {1}[Hardware Error]: event severity: recoverable
      [  123.584670] {1}[Hardware Error]:  Error 0, type: recoverable
      [  123.590317] {1}[Hardware Error]:   section_type: PCIe error
      [  123.595877] {1}[Hardware Error]:   version: 4.0
      [  123.600395] {1}[Hardware Error]:   command: 0x0006, status: 0x0010
      [  123.606562] {1}[Hardware Error]:   device_id: 0000:7d:00.0
      [  123.612034] {1}[Hardware Error]:   slot: 0
      [  123.616120] {1}[Hardware Error]:   secondary_bus: 0x00
      [  123.621245] {1}[Hardware Error]:   vendor_id: 0x19e5, device_id: 0xa222
      [  123.627847] {1}[Hardware Error]:   class_code: 000002
      [  123.632977] hns3 0000:7d:00.0: aer_status: 0x00000000, aer_mask: 0x00000000
      [  123.639928] hns3 0000:7d:00.0: aer_layer=Transaction Layer, aer_agent=Receiver ID
      [  123.647400] hns3 0000:7d:00.0: aer_uncor_severity: 0x00000000
      [  123.653136] hns3 0000:7d:00.0: PCI error detected, state(=1)!!
      [  123.658959] hns3 0000:7d:00.0: ROCEE uncorrected RAS error identified
      [  123.665395] hns3 0000:7d:00.0: ROCEE RAS AXI rresp error
      [  123.670713] hns3 0000:7d:00.0: requesting reset due to PCI error
      [  123.676715] hns3 0000:7d:00.0: received reset event , reset type is 5
      [  123.683147] hns3 0000:7d:00.0: AER: Device recovery successful
      [  123.688978] hns3 0000:7d:00.0: PF Reset requested
      [  123.693684] hns3 0000:7d:00.0: PF failed(=-5) to send mailbox message to VF
      [  123.700633] hns3 0000:7d:00.0: inform reset to vf(1) failded -5!
      
      Fixes: 6a157f7d ("RDMA/hns: Add SCC context allocation support for hip08")
      Signed-off-by: NYangyang Li <liyangyang20@huawei.com>
      Reviewed-by: NYixian Liu <liuyixian@huawei.com>
      Reviewed-by: NLijun Ou <oulijun@huawei.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      6ac16e40
    • L
      RDMA/hns: Modify qp&cq&pd specification according to UM · 3e394f94
      Lijun Ou 提交于
      Accroding to hip08's limitation, qp&cq specification is 1M, mtpt
      specification 1M in kernel space.
      Signed-off-by: NYangyang Li <liyangyang20@huawei.com>
      Signed-off-by: NLijun Ou <oulijun@huawei.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      3e394f94
    • P
      IB/usnic: Fix deadlock · 5bb3c1e9
      Parvi Kaustubhi 提交于
      There is a dead lock in usnic ib_register and netdev_notify path.
      
      	usnic_ib_discover_pf()
      	| mutex_lock(&usnic_ib_ibdev_list_lock);
      	 | usnic_ib_device_add();
      	  | ib_register_device()
      	   | usnic_ib_query_port()
      	    | mutex_lock(&us_ibdev->usdev_lock);
      	     | ib_get_eth_speed()
      	      | rtnl_lock()
      
      order of lock: &usnic_ib_ibdev_list_lock -> usdev_lock -> rtnl_lock
      
      	rtnl_lock()
      	 | usnic_ib_netdevice_event()
      	  | mutex_lock(&usnic_ib_ibdev_list_lock);
      
      order of lock: rtnl_lock -> &usnic_ib_ibdev_list_lock
      
      Solution is to use the core's lock-free ib_device_get_by_netdev() scheme
      to lookup ib_dev while handling netdev & inet events.
      Signed-off-by: NParvi Kaustubhi <pkaustub@cisco.com>
      Reviewed-by: NGovindarajulu Varadarajan <gvaradar@cisco.com>
      Reviewed-by: NTanmay Inamdar <tinamdar@cisco.com>
      Signed-off-by: NJason Gunthorpe <jgg@mellanox.com>
      5bb3c1e9
  4. 16 2月, 2019 4 次提交
  5. 15 2月, 2019 10 次提交
  6. 14 2月, 2019 2 次提交
  7. 12 2月, 2019 12 次提交
  8. 09 2月, 2019 6 次提交