Linux Trace Kernel
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kassey Li <quic_yingangl@quicinc.com>,
	rostedt@goodmis.org,  martin.petersen@oracle.com,
	mathieu.desnoyers@efficios.com,  linux-kernel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,  linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2] scsi: trace: change the rtn log in string
Date: Wed, 14 May 2025 09:39:26 -0400	[thread overview]
Message-ID: <78209d1c512a39b4ebbabda6181110b3c23e6f6b.camel@HansenPartnership.com> (raw)
In-Reply-To: <20250514074456.450006-1-quic_yingangl@quicinc.com>

On Wed, 2025-05-14 at 15:44 +0800, Kassey Li wrote:
> In default it showed rtn in decimal.
> 
> kworker/3:1H-183 [003] ....  51.035474: scsi_dispatch_cmd_error:
> host_no=0 channel=0 id=0 lun=4 data_sgl=1  prot_sgl=0
> prot_op=SCSI_PROT_NORMAL cmnd=(READ_10 lba=3907214  txlen=1 protect=0
> raw=28 00 00 3b 9e 8e 00 00 01 00) rtn=4181
> 
> In source code we define these possible value as hexadecimal:
> 
> include/scsi/scsi.h
> 
> SCSI_MLQUEUE_HOST_BUSY   0x1055
> SCSI_MLQUEUE_DEVICE_BUSY 0x1056
> SCSI_MLQUEUE_EH_RETRY    0x1057
> SCSI_MLQUEUE_TARGET_BUSY 0x1058
> 
> This change shows the string type.
> 
> Signed-off-by: Kassey Li <quic_yingangl@quicinc.com>
> ---
>  include/trace/events/scsi.h | 8 ++++++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/include/trace/events/scsi.h
> b/include/trace/events/scsi.h
> index bf6cc98d9122..56987f98ba4a 100644
> --- a/include/trace/events/scsi.h
> +++ b/include/trace/events/scsi.h
> @@ -240,14 +240,18 @@ TRACE_EVENT(scsi_dispatch_cmd_error,
>  
>  	TP_printk("host_no=%u channel=%u id=%u lun=%u data_sgl=%u
> prot_sgl=%u" \
>  		  " prot_op=%s driver_tag=%d scheduler_tag=%d
> cmnd=(%s %s raw=%s)" \
> -		  " rtn=%d",
> +		  " rtn=%s",
>  		  __entry->host_no, __entry->channel, __entry->id,
>  		  __entry->lun, __entry->data_sglen, __entry-
> >prot_sglen,
>  		  show_prot_op_name(__entry->prot_op), __entry-
> >driver_tag,
>  		  __entry->scheduler_tag, show_opcode_name(__entry-
> >opcode),
>  		  __parse_cdb(__get_dynamic_array(cmnd), __entry-
> >cmd_len),
>  		  __print_hex(__get_dynamic_array(cmnd), __entry-
> >cmd_len),
> -		  __entry->rtn)
> +		  __print_symbolic(rtn, { SCSI_MLQUEUE_HOST_BUSY,
> "HOST_BUSY" },
> +			  { SCSI_MLQUEUE_DEVICE_BUSY, "DEVICE_BUSY"
> },
> +			  { SCSI_MLQUEUE_EH_RETRY, "EH_RETRY" },
> +			  { SCSI_MLQUEUE_TARGET_BUSY, "TARGET_BUSY"
> })
> +		  )

We tend to do global print_symbolics as show_XXX_name definitions at
the top of the file even if they only occur once, just in case some
other trace point wants to use them.

Regards,

James


  parent reply	other threads:[~2025-05-14 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14  7:44 [PATCH v2] scsi: trace: change the rtn log in string Kassey Li
2025-05-14 13:09 ` Steven Rostedt
2025-05-19  9:40   ` Kassey Li quic
2025-05-14 13:39 ` James Bottomley [this message]
2025-05-19  9:37   ` Kassey Li quic
2025-05-14 23:05 ` kernel test robot

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=78209d1c512a39b4ebbabda6181110b3c23e6f6b.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=quic_yingangl@quicinc.com \
    --cc=rostedt@goodmis.org \
    /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