From: Leon Romanovsky <leon@kernel.org>
To: Michael Margolin <mrgolin@amazon.com>
Cc: jgg@nvidia.com, linux-rdma@vger.kernel.org, sleybo@amazon.com,
matua@amazon.com, gal.pressman@linux.dev,
Yonatan Nachum <ynachum@amazon.com>
Subject: Re: [PATCH for-next v2] RDMA/efa: Extend admin timeout error print
Date: Sun, 6 Jul 2025 10:25:23 +0300 [thread overview]
Message-ID: <20250706072523.GQ6278@unreal> (raw)
In-Reply-To: <20250703182314.16442-1-mrgolin@amazon.com>
On Thu, Jul 03, 2025 at 06:23:14PM +0000, Michael Margolin wrote:
> Add command id to the printed message for additional debug information.
>
> Reviewed-by: Yonatan Nachum <ynachum@amazon.com>
> Signed-off-by: Michael Margolin <mrgolin@amazon.com>
> ---
> drivers/infiniband/hw/efa/efa_com.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
Please don't forget to add changelogs.
>
> diff --git a/drivers/infiniband/hw/efa/efa_com.c b/drivers/infiniband/hw/efa/efa_com.c
> index bafd210dd43e..e6377602a9c4 100644
> --- a/drivers/infiniband/hw/efa/efa_com.c
> +++ b/drivers/infiniband/hw/efa/efa_com.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
> /*
> - * Copyright 2018-2024 Amazon.com, Inc. or its affiliates. All rights reserved.
> + * Copyright 2018-2025 Amazon.com, Inc. or its affiliates. All rights reserved.
> */
<...>
> reinit_completion(&comp_ctx->wait_event);
>
> @@ -557,17 +559,19 @@ static int efa_com_wait_and_process_admin_cq_interrupts(struct efa_comp_ctx *com
> if (comp_ctx->status == EFA_CMD_COMPLETED)
> ibdev_err_ratelimited(
> aq->efa_dev,
> - "The device sent a completion but the driver didn't receive any MSI-X interrupt for admin cmd %s(%d) status %d (ctx: 0x%p, sq producer: %d, sq consumer: %d, cq consumer: %d)\n",
> + "The device sent a completion but the driver didn't receive any MSI-X interrupt for admin cmd %s(%d) status %d (id: %d, sq producer: %d, sq consumer: %d, cq consumer: %d)\n",
> efa_com_cmd_str(comp_ctx->cmd_opcode),
> comp_ctx->cmd_opcode, comp_ctx->status,
> - comp_ctx, aq->sq.pc, aq->sq.cc, aq->cq.cc);
> + comp_ctx->cmd_id, aq->sq.pc, aq->sq.cc,
> + aq->cq.cc);
> else
> ibdev_err_ratelimited(
> aq->efa_dev,
> - "The device didn't send any completion for admin cmd %s(%d) status %d (ctx 0x%p, sq producer: %d, sq consumer: %d, cq consumer: %d)\n",
> + "The device didn't send any completion for admin cmd %s(%d) status %d (id: %d, sq producer: %d, sq consumer: %d, cq consumer: %d)\n",
> efa_com_cmd_str(comp_ctx->cmd_opcode),
> comp_ctx->cmd_opcode, comp_ctx->status,
> - comp_ctx, aq->sq.pc, aq->sq.cc, aq->cq.cc);
> + comp_ctx->cmd_id, aq->sq.pc, aq->sq.cc,
> + aq->cq.cc);
I have very strong feeling that you don't really use these prints in real life.
For example, comp_ctx->cmd_id is printed with %d, while code and comment
around cmd_id in __efa_com_submit_admin_cmd() suggests that it needs to be 0x%X.
It has a lot of information separated to LSB and MSB bits which are not readable
while printing with %d.
You are also printing comp_ctx->status, which is clear from if/else section.
So no, I don't buy this claim for "additional debug information", while
existing is not used.
Thanks
>
> clear_bit(EFA_AQ_STATE_RUNNING_BIT, &aq->state);
> err = -ETIME;
> --
> 2.47.1
>
next prev parent reply other threads:[~2025-07-06 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 18:23 [PATCH for-next v2] RDMA/efa: Extend admin timeout error print Michael Margolin
2025-07-06 7:25 ` Leon Romanovsky [this message]
2025-07-06 16:32 ` Margolin, Michael
2025-07-07 6:28 ` Leon Romanovsky
2025-07-07 9:51 ` Margolin, Michael
2025-07-07 10:28 ` Leon Romanovsky
2025-07-07 11:18 ` Margolin, Michael
2025-08-18 7:55 ` Margolin, Michael
2025-07-07 11:30 ` Gal Pressman
2025-08-25 14:56 ` 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=20250706072523.GQ6278@unreal \
--to=leon@kernel.org \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.com \
--cc=ynachum@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.