From: Bart Van Assche <bvanassche@acm.org>
To: Zhe Wang <zhe.wang1@unisoc.com>,
martin.petersen@oracle.com, jejb@linux.ibm.com,
alim.akhtar@samsung.com, avri.altman@wdc.com,
quic_asutoshd@quicinc.com
Cc: linux-scsi@vger.kernel.org, orsonzhai@gmail.com,
yuelin.tang@unisoc.com, zhenxiong.lai@unisoc.com,
zhang.lyra@gmail.com, zhewang116@gmail.com
Subject: Re: [PATCH] scsi: ufs: core: Add compl_time_stamp_local_clock assignment
Date: Wed, 1 Nov 2023 09:43:07 -0700 [thread overview]
Message-ID: <f1be8bb5-7fac-45b3-a428-d5ba9b1ec260@acm.org> (raw)
In-Reply-To: <20231101071420.29238-1-zhe.wang1@unisoc.com>
On 11/1/23 00:14, Zhe Wang wrote:
> The compl_time_stamp_local_clock assignment seems to have been
> accidentally deleted in the previous patch, so it needs to be added
> again for debugging needs.
>
> Fixes: c30d8d010b5e ("scsi: ufs: core: Prepare for completion in MCQ")
> Signed-off-by: Zhe Wang <zhe.wang1@unisoc.com>
> ---
> drivers/ufs/core/ufshcd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 8382e8cfa414..b35977fa931f 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -5388,6 +5388,7 @@ void ufshcd_compl_one_cqe(struct ufs_hba *hba, int task_tag,
>
> lrbp = &hba->lrb[task_tag];
> lrbp->compl_time_stamp = ktime_get();
> + lrbp->compl_time_stamp_local_clock = local_clock();
> cmd = lrbp->cmd;
> if (cmd) {
> if (unlikely(ufshcd_should_inform_monitor(hba, lrbp)))
Is anyone using the data tracked in compl_time_stamp /
compl_time_stamp_local_clock? I'm wondering whether the code for
tracking command duration can be removed. Otherwise the above patch
looks fine to me.
Thanks,
Bart.
next prev parent reply other threads:[~2023-11-01 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 7:14 [PATCH] scsi: ufs: core: Add compl_time_stamp_local_clock assignment Zhe Wang
2023-11-01 16:43 ` Bart Van Assche [this message]
2023-11-02 7:59 ` Zhe Wang
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=f1be8bb5-7fac-45b3-a428-d5ba9b1ec260@acm.org \
--to=bvanassche@acm.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=orsonzhai@gmail.com \
--cc=quic_asutoshd@quicinc.com \
--cc=yuelin.tang@unisoc.com \
--cc=zhang.lyra@gmail.com \
--cc=zhe.wang1@unisoc.com \
--cc=zhenxiong.lai@unisoc.com \
--cc=zhewang116@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