From: Bob Pearson <rpearsonhpe@gmail.com>
To: jgg@nvidia.com, zyjzyj2000@gmail.com, jhack@hpe.com,
linux-rdma@vger.kernel.org
Cc: Bob Pearson <rpearsonhpe@gmail.com>, kernel test robot <lkp@intel.com>
Subject: [PATCH for-next v4 0/4] Add error logging to rxe
Date: Fri, 3 Mar 2023 16:16:20 -0600 [thread overview]
Message-ID: <20230303221623.8053-1-rpearsonhpe@gmail.com> (raw)
Primarily to make debugging more efficient, log message types
are added and error logging messages are added to the verbs API
to rxe driver with the goal that each error reported up to
rdma-core will generate at least one message with additional
details and internal errors restricted to debug messages which can
be dynamically turned on.
v4:
Removed a mistaken WARN_ON at line 750 in rxe_verbs.c. This was
hidden by a later fix that covered the error.
v3:
Corrected a debug message referring to err before err was set in
patch 4/4.
Reported-by: kernel test robot <lkp@intel.com>
Link: https://lore.kernel.org/oe-kbuild-all/202302250056.mgmG5a52-lkp@intel.com/
v2:
This set of four patches was split off an earlier series called
"RDMA/rxe: Correct qp reference counting" since it is not really
related.
Bob Pearson (4):
RDMA/rxe: Replace exists by rxe in rxe.c
RDMA/rxe: Change rxe_dbg to rxe_dbg_dev
RDMA/rxe: Extend dbg log messages to err and info
RDMA/rxe: Add error messages
drivers/infiniband/sw/rxe/rxe.c | 16 +-
drivers/infiniband/sw/rxe/rxe.h | 45 +-
drivers/infiniband/sw/rxe/rxe_comp.c | 4 +
drivers/infiniband/sw/rxe/rxe_cq.c | 6 +-
drivers/infiniband/sw/rxe/rxe_icrc.c | 4 +-
drivers/infiniband/sw/rxe/rxe_loc.h | 1 -
drivers/infiniband/sw/rxe/rxe_mmap.c | 6 +-
drivers/infiniband/sw/rxe/rxe_mr.c | 13 -
drivers/infiniband/sw/rxe/rxe_net.c | 4 +-
drivers/infiniband/sw/rxe/rxe_qp.c | 16 +-
drivers/infiniband/sw/rxe/rxe_resp.c | 4 +
drivers/infiniband/sw/rxe/rxe_srq.c | 6 +-
drivers/infiniband/sw/rxe/rxe_verbs.c | 830 +++++++++++++++++++-------
13 files changed, 684 insertions(+), 271 deletions(-)
base-commit: 66fb1d5df6ace316a4a6e2c31e13fc123ea2b644
--
2.37.2
next reply other threads:[~2023-03-03 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 22:16 Bob Pearson [this message]
2023-03-03 22:16 ` [PATCH for-next v4 1/4] RDMA/rxe: Replace exists by rxe in rxe.c Bob Pearson
2023-03-03 22:16 ` [PATCH for-next v4 2/4] RDMA/rxe: Change rxe_dbg to rxe_dbg_dev Bob Pearson
2023-03-03 22:16 ` [PATCH for-next v4 3/4] RDMA/rxe: Extend dbg log messages to err and info Bob Pearson
2023-03-03 22:16 ` [PATCH for-next v4 4/4] RDMA/rxe: Add error messages Bob Pearson
2023-03-24 14:09 ` [PATCH for-next v4 0/4] Add error logging to rxe Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230303221623.8053-1-rpearsonhpe@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=jgg@nvidia.com \
--cc=jhack@hpe.com \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=zyjzyj2000@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).