RDMA/qedr: iWARP invalid(zero) doorbell address fix.
Subsystems (2)
PATCH 1/1 RDMA/qedr: iWARP invalid(zero) doorbell address fix.
This patch fixes issue introduced by a previous commit where iWARP doorbell address wasn't initialized, causing call trace when any RDMA application wants to use this interface.
Fixes 06e8d1df46ed ("RDMA/qedr: Add support for user mode XRC-SRQ's")
Signed-off-by Michal Kalderon <[email protected]>
Signed-off-by Igor Russkikh <[email protected]>
Signed-off-by Alok Prasad <[email protected]>
--- drivers/infiniband/hw/qedr/verbs.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/infiniband/hw/qedr/verbs.c +9 -0
@@ -1936,6 +1936,15 @@ static int qedr_create_user_qp(struct qedr_dev *dev, }if (rdma_protocol_iwarp (&dev->ibdev,1 )) { + qp->urq.db_rec_db2_addr = ctx->dpi_addr + uresp.rq_db2_offset; + +/* calculate the db_rec_db2 data since it is constant so no +* need to reflect from user +*/ + qp->urq.db_rec_db2_data.data.icid =cpu_to_le16 (qp->icid); + qp->urq.db_rec_db2_data.data.value = +cpu_to_le16 (DQ_TCM_IWARP_POST_RQ_CF_CMD ); + rc = qedr_db_recovery_add(dev, qp->urq.db_rec_db2_addr, &qp->urq.db_rec_db2_data, DB_REC_WIDTH_32B,
Signature · 1 line
2.27.0
Quoted 4 lines · Alok Prasad
This patch fixes issue introduced by a previous commit where iWARP doorbell address wasn't initialized, causing call trace when any RDMA application wants to use this interface.
Include the call trace in the commit message
Jason