From: Bart Van Assche <bvanassche@acm.org>
To: palash.kambar@oss.qualcomm.com, mani@kernel.org,
alim.akhtar@samsung.com, avri.altman@wdc.com,
peter.griffin@linaro.org, krzk@kernel.org,
peter.wang@mediatek.com, beanhuo@micron.com,
quic_nguyenb@quicinc.com, adrian.hunter@intel.com,
ebiggers@kernel.org, neil.armstrong@linaro.org,
James.Bottomley@HansenPartnership.com,
martin.petersen@oracle.com
Cc: linux-arm-msm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_cang@quicinc.com,
quic_nitirawa@quicinc.com
Subject: Re: [PATCH V1 1/2] ufs: core:Add vendor-specific callbacks and update setup_xfer_req interface
Date: Tue, 14 Oct 2025 09:10:22 -0700 [thread overview]
Message-ID: <d027689e-9c45-4584-ac35-411b74b551a9@acm.org> (raw)
In-Reply-To: <20251014060406.1420475-2-palash.kambar@oss.qualcomm.com>
On 10/13/25 11:04 PM, palash.kambar@oss.qualcomm.com wrote:
> On QCOM UFSHC V6 in MCQ mode, a race condition exists where simultaneous
> data and hibernate commands can cause data commands to be dropped when
> the Auto-Hibernate Idle Timer (AHIT) is near expiration.
>
> To mitigate this, AHIT is disabled before updating the SQ tail pointer,
> and re-enabled only when no active commands remain. This prevents
> conflicting command sequences from reaching the UniPro layer during
> critical timing windows.
>
> To support this:
> - Introduce a new vendor operation `compl_command` to allow vendors to
> handle command completion in a customized manner.
> - Update the argument list for the existing `setup_xfer_req` vendor
> operation to align with the updated UFS core interface.
> - Modify the Exynos-specific `setup_xfer_req` implementation to match
> the new interface and support the AHIT handling logic.
Yikes. Please disable AHIT entirely or disable/enable AHIT from inside
the runtime power management callbacks rather than inventing a new
mechanism for tracking whether any commands are outstanding.
> diff --git a/drivers/ufs/core/ufshcd.c b/drivers/ufs/core/ufshcd.c
> index 568a449e7331..fd771d6c315e 100644
> --- a/drivers/ufs/core/ufshcd.c
> +++ b/drivers/ufs/core/ufshcd.c
> @@ -2383,11 +2383,11 @@ void ufshcd_send_command(struct ufs_hba *hba, unsigned int task_tag,
> memcpy(dest, src, utrd_size);
> ufshcd_inc_sq_tail(hwq);
> spin_unlock(&hwq->sq_lock);
> + hba->vops->setup_xfer_req(hba, lrbp);
What will happen if hba->vops->setup_xfer_req == NULL? Will the above
code trigger a kernel crash?
> @@ -5637,6 +5637,7 @@ void ufshcd_compl_one_cqe(struct ufs_hba *hba, int task_tag,
> }
> cmd = lrbp->cmd;
> if (cmd) {
> + hba->vops->compl_command(hba, lrbp);
> if (unlikely(ufshcd_should_inform_monitor(hba, lrbp)))
> ufshcd_update_monitor(hba, lrbp);
> ufshcd_add_command_trace(hba, task_tag, UFS_CMD_COMP);
Yikes. New unconditional indirect function calls in the hot path are not
acceptable because these have a negative performance impact.
> @@ -5645,6 +5646,7 @@ void ufshcd_compl_one_cqe(struct ufs_hba *hba, int task_tag,
> /* Do not touch lrbp after scsi done */
> scsi_done(cmd);
> } else {
> + hba->vops->compl_command(hba, lrbp);
> if (cqe) {
> ocs = le32_to_cpu(cqe->status) & MASK_OCS;
> lrbp->utr_descriptor_ptr->header.ocs = ocs;
Same comment here.
> diff --git a/drivers/ufs/host/ufs-exynos.c b/drivers/ufs/host/ufs-exynos.c
> index 70d195179eba..d87276f45e01 100644
> --- a/drivers/ufs/host/ufs-exynos.c
> +++ b/drivers/ufs/host/ufs-exynos.c
> @@ -910,11 +910,15 @@ static int exynos_ufs_post_pwr_mode(struct ufs_hba *hba,
> }
>
> static void exynos_ufs_specify_nexus_t_xfer_req(struct ufs_hba *hba,
> - int tag, bool is_scsi_cmd)
> + struct ufshcd_lrb *lrbp)
> {
> struct exynos_ufs *ufs = ufshcd_get_variant(hba);
> u32 type;
> + int tag;
> + bool is_scsi_cmd;
>
> + tag = lrbp->task_tag;
> + is_scsi_cmd = !!lrbp->cmd;
> type = hci_readl(ufs, HCI_UTRL_NEXUS_TYPE);
>
> if (is_scsi_cmd)
I'm about to remove lrbp->cmd so please don't introduce any new users of
this structure member.
Bart.
next prev parent reply other threads:[~2025-10-14 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 6:04 [PATCH V1 0/2] Address race condition in MCQ mode and enhance palash.kambar
2025-10-14 6:04 ` [PATCH V1 1/2] ufs: core:Add vendor-specific callbacks and update setup_xfer_req interface palash.kambar
2025-10-14 16:10 ` Bart Van Assche [this message]
2025-10-18 6:49 ` Palash Kambar
2025-10-14 6:04 ` [PATCH V1 2/2] ufs: ufs-qcom: Disable AHIT before SQ tail update to prevent race in MCQ mode palash.kambar
2025-10-14 16:18 ` Bart Van Assche
[not found] ` <CAGbPq5dhUXr59U_J3W4haNHughkaiXpnc4kAZWXB0SjPdFQMhg@mail.gmail.com>
2025-10-15 15:45 ` Bart Van Assche
2025-10-18 6:44 ` Palash Kambar
2025-10-20 6:53 ` 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=d027689e-9c45-4584-ac35-411b74b551a9@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=adrian.hunter@intel.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=ebiggers@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mani@kernel.org \
--cc=martin.petersen@oracle.com \
--cc=neil.armstrong@linaro.org \
--cc=palash.kambar@oss.qualcomm.com \
--cc=peter.griffin@linaro.org \
--cc=peter.wang@mediatek.com \
--cc=quic_cang@quicinc.com \
--cc=quic_nguyenb@quicinc.com \
--cc=quic_nitirawa@quicinc.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
all inboxes | Powered by JetHome®