From: Aru <aru.kolappan@oracle.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, manjunath.b.patil@oracle.com,
rama.nichanamatlu@oracle.com
Subject: Re: [PATCH 1/1] net/mlx5: update debug log level for remote access error syndromes
Date: Tue, 1 Nov 2022 00:23:56 -0700 [thread overview]
Message-ID: <3ba046cf-7cb1-bb0b-7310-360ff7cfcde6@oracle.com> (raw)
In-Reply-To: <Y1jKHcBdcUnluIdU@unreal>
Hi Leon,
On 10/25/22 10:48 PM, Leon Romanovsky wrote:
> On Tue, Oct 25, 2022 at 02:22:01AM -0700, Arumugam Kolappan wrote:
>> The mlx5 driver dumps the entire CQE buffer by default for few syndromes.
>> Some syndromes are expected due to the application behavior [ex:
>> MLX5_CQE_SYNDROME_REMOTE_ACCESS_ERR, MLX5_CQE_SYNDROME_REMOTE_OP_ERR and
>> MLX5_CQE_SYNDROME_LOCAL_PROT_ERR]. Hence, for these syndromes, the patch
>> converts the log level from KERN_WARNING to KERN_DEBUG. This enables the
>> application to get the CQE buffer dump by changing to KERN_DEBUG level
>> as and when needed.
>>
>> Suggested-by: Leon Romanovsky <leon@kernel.org>
>> Signed-off-by: Arumugam Kolappan <aru.kolappan@oracle.com>
>> ---
>> drivers/infiniband/hw/mlx5/cq.c | 30 ++++++++++++++++++++++--------
>> 1 file changed, 22 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/infiniband/hw/mlx5/cq.c b/drivers/infiniband/hw/mlx5/cq.c
>> index be189e0..d665129 100644
>> --- a/drivers/infiniband/hw/mlx5/cq.c
>> +++ b/drivers/infiniband/hw/mlx5/cq.c
>> @@ -267,10 +267,25 @@ static void handle_responder(struct ib_wc *wc, struct mlx5_cqe64 *cqe,
>> wc->wc_flags |= IB_WC_WITH_NETWORK_HDR_TYPE;
>> }
>>
>> -static void dump_cqe(struct mlx5_ib_dev *dev, struct mlx5_err_cqe *cqe)
>> +static void dump_cqe(struct mlx5_ib_dev *dev, struct mlx5_err_cqe *cqe,
>> + struct ib_wc *wc, int dump)
>> {
>> - mlx5_ib_warn(dev, "dump error cqe\n");
>> - mlx5_dump_err_cqe(dev->mdev, cqe);
>> + const char *level;
>> +
>> + if (!dump)
>> + return;
>> +
>> + mlx5_ib_warn(dev, "WC error: %d, Message: %s\n", wc->status,
>> + ib_wc_status_msg(wc->status));
> Aren't you interested "to hide" this print too? Right now, it will
> be printed without relation to your "dump" variable value.
Thanks for pointing out this. Yes. This line also needs to be covered by
debug log level.
Current existing functions ("mlx5_ib_warn(), mlx5_ib_err() ...) do not
accept log-level as argument.
So I've added a new fn: mlx5_ib_log(..) which takes log-level as the
first argument and print it accordingly.
The updated patch will be posted in the next email for your review.
>> +
>> + if (dump == 1)
>> + level = KERN_WARNING;
>> +
>> + if (dump == 2)
>> + level = KERN_DEBUG;
> Please change dump_cqe() arguments to receive level directly, so you
> will set "dump = KERN_DEBUG" and not not "dump = 2" in
> mlx5_handle_error_cqe().
Yes. This is also taken care in the updated patch.
Also I've updated the subject line as you mentioned in the other email.
Thanks
Aru
>
> Thanks
prev parent reply other threads:[~2022-11-01 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 9:22 [PATCH 1/1] net/mlx5: update debug log level for remote access error syndromes Arumugam Kolappan
2022-10-26 5:48 ` Leon Romanovsky
2022-10-26 5:58 ` Leon Romanovsky
2022-11-01 7:23 ` Aru [this message]
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=3ba046cf-7cb1-bb0b-7310-360ff7cfcde6@oracle.com \
--to=aru.kolappan@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=rama.nichanamatlu@oracle.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).