From: Bart Van Assche <bvanassche@acm.org>
To: peter.wang@mediatek.com, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, avri.altman@wdc.com,
alim.akhtar@samsung.com, jejb@linux.ibm.com
Cc: wsd_upstream@mediatek.com, linux-mediatek@lists.infradead.org,
chun-hung.wu@mediatek.com, alice.chao@mediatek.com,
cc.chou@mediatek.com, chaotian.jing@mediatek.com,
jiajie.hao@mediatek.com, powen.kao@mediatek.com,
qilin.tan@mediatek.com, lin.gui@mediatek.com,
tun-yu.yu@mediatek.com, eddie.huang@mediatek.com,
naomi.chu@mediatek.com, ed.tsai@mediatek.com,
quic_nguyenb@quicinc.com
Subject: Re: [PATCH v8 2/3] ufs: core: fix error handler process for MCQ abort
Date: Mon, 23 Sep 2024 11:19:28 -0700 [thread overview]
Message-ID: <f08fbc51-22a7-4c13-b9d4-ee7f4920bcfa@acm.org> (raw)
In-Reply-To: <20240923080344.19084-3-peter.wang@mediatek.com>
On 9/23/24 1:03 AM, peter.wang@mediatek.com wrote:
> When the error handler successfully aborts a MCQ request,
> it only releases the command and does not notify the SCSI layer.
> This may cause another abort after 30 seconds timeout.
> This patch notifies the SCSI layer to requeue the request.
>
> Additionally, ignore the OCS: ABORTED CQ slot after MCQ mode
> SQ cleanup. This makes the behavior of MCQ mode consistent with
> that of legacy SDB mode.
>
> Also, print logs for OCS: ABORTED and OCS_INVALID_COMMAND_STATUS
> for debugging purposes.
Although I like the approach of this patch, two comments below.
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index a6f818cdef0e..b5c7bc50a27e 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -5405,9 +5405,15 @@ ufshcd_transfer_rsp_status(struct ufs_hba *hba, struct ufshcd_lrb *lrbp,
> break;
> case OCS_ABORTED:
> result |= DID_ABORT << 16;
> + dev_warn(hba->dev,
> + "OCS aborted from controller = %x for tag %d\n",
> + ocs, lrbp->task_tag);
> break;
Including the OCS status in this message seems redundant to me.
> case OCS_INVALID_COMMAND_STATUS:
> result |= DID_REQUEUE << 16;
> + dev_warn(hba->dev,
> + "OCS invaild from controller = %x for tag %d\n",
> + ocs, lrbp->task_tag);
Also here, including the OCS status in this message seems redundant to me.
Please change "invaild" into "invalid".
> @@ -5526,6 +5532,18 @@ void ufshcd_compl_one_cqe(struct ufs_hba *hba, int task_tag,
> ufshcd_update_monitor(hba, lrbp);
> ufshcd_add_command_trace(hba, task_tag, UFS_CMD_COMP);
> cmd->result = ufshcd_transfer_rsp_status(hba, lrbp, cqe);
> +
> + /*
> + * Ignore MCQ OCS: ABORTED posted by the host controller.
> + * This makes the behavior of MCQ mode consistent with that
> + * of legacy SDB mode.
> + */
> + if (hba->mcq_enabled) {
> + ocs = ufshcd_get_tr_ocs(lrbp, cqe);
> + if (ocs == OCS_ABORTED)
> + return;
> + }
Why only ignore the OCS_ABORTED status in MCQ mode? Is my understanding
correct that MediaTek controllers can also report this status in legacy
mode?
Thanks,
Bart.
next prev parent reply other threads:[~2024-09-23 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 8:03 [PATCH v8 0/3] fix abort defect peter.wang
2024-09-23 8:03 ` [PATCH v8 1/3] ufs: core: fix the issue of ICU failure peter.wang
2024-09-23 8:03 ` [PATCH v8 2/3] ufs: core: fix error handler process for MCQ abort peter.wang
2024-09-23 18:19 ` Bart Van Assche [this message]
2024-09-24 8:48 ` Peter Wang (王信友)
2024-09-23 8:03 ` [PATCH v8 3/3] ufs: core: add a quirk for MediaTek SDB mode aborted peter.wang
2024-09-23 18:15 ` Bart Van Assche
2024-09-24 8:51 ` Peter Wang (王信友)
2024-09-24 19:36 ` Bart Van Assche
2024-09-25 5:19 ` Peter 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=f08fbc51-22a7-4c13-b9d4-ee7f4920bcfa@acm.org \
--to=bvanassche@acm.org \
--cc=alice.chao@mediatek.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=ed.tsai@mediatek.com \
--cc=eddie.huang@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=jiajie.hao@mediatek.com \
--cc=lin.gui@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=naomi.chu@mediatek.com \
--cc=peter.wang@mediatek.com \
--cc=powen.kao@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=quic_nguyenb@quicinc.com \
--cc=tun-yu.yu@mediatek.com \
--cc=wsd_upstream@mediatek.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