From: Bean Huo <huobean@gmail.com>
To: Can Guo <cang@codeaurora.org>, Stanley Chu <stanley.chu@mediatek.com>
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com,
asutoshd@codeaurora.org, jejb@linux.ibm.com,
martin.petersen@oracle.com, stanley.chu@mediatek.com,
beanhuo@micron.com, bvanassche@acm.org, tomas.winkler@intel.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] scsi: ufs: no need to send one Abort Task TM in case the task in DB was cleared
Date: Mon, 10 Aug 2020 17:41:22 +0200 [thread overview]
Message-ID: <5c6f1ad9f703cc5721e081452e869a9ee6bc4ab6.camel@gmail.com> (raw)
In-Reply-To: <5ad1dbd76a0d5d476641a01bfb8bd435@codeaurora.org>
On Thu, 2020-08-06 at 18:07 +0800, Can Guo wrote:
> Hi Bean,
>
> On 2020-08-06 17:50, Bean Huo wrote:
> > >
> > > Please check Stanley's recent change to ufshcd_abort, you may
> > > want to rebase your change on his and do goto cleanup here.
> > > @Stanley correct me if I am wrong.
> > >
> > > But even if you do a goto cleanup here, we still lost the
> > > chances to dump host infos/regs like it does in the old code.
> > > If a cmd was completed but without a notifying intr, this is
> > > kind of a problem that we/host should look into, because it's
> > > pasted at least 30 sec since the cmd was sent, so those dumps
> > > are necessary to debug the problem. How about moving blow prints
> > > in front of this part?
> > >
> > > Thanks,
> > >
> > > Can Guo.
> > >
> > > > }
> > > >
> > > > /* Print Transfer Request of aborted task */
> >
> > Hi Can
> >
> > Thanks, do you mean that change to like this:
> >
> >
> > Author: Bean Huo <beanhuo@micron.com>
> > Date: Thu Aug 6 11:34:45 2020 +0200
> >
> > scsi: ufs: no need to send one Abort Task TM in case the task
> > in
> > was cleared
> >
> > If the bit corresponds to a task in the Doorbell register has
> > been
> > cleared, no need to poll the status of the task on the device
> > side
> > and to send an Abort Task TM.
> > This patch also deletes dispensable dev_err() in case of the
> > task
> > already completed.
> >
> > Signed-off-by: Bean Huo <beanhuo@micron.com>
> >
> > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> > index 307622284239..f7c91ce9e294 100644
> > --- a/drivers/scsi/ufs/ufshcd.c
> > +++ b/drivers/scsi/ufs/ufshcd.c
> > @@ -6425,23 +6425,9 @@ static int ufshcd_abort(struct scsi_cmnd
> > *cmd)
> > return ufshcd_eh_host_reset_handler(cmd);
> >
> > ufshcd_hold(hba, false);
> > - reg = ufshcd_readl(hba, REG_UTP_TRANSFER_REQ_DOOR_BELL);
> > /* If command is already aborted/completed, return SUCCESS
> > */
> > - if (!(test_bit(tag, &hba->outstanding_reqs))) {
> > - dev_err(hba->dev,
> > - "%s: cmd at tag %d already completed,
> > outstanding=0x%lx, doorbell=0x%x\n",
> > - __func__, tag, hba->outstanding_reqs, reg);
> > + if (!(test_bit(tag, &hba->outstanding_reqs)))
> > goto out;
> > - }
> > -
> > - if (!(reg & (1 << tag))) {
> > - dev_err(hba->dev,
> > - "%s: cmd was completed, but without a notifying
> > intr,
> > tag = %d",
> > - __func__, tag);
> > - }
> > -
> > - /* Print Transfer Request of aborted task */
> > - dev_err(hba->dev, "%s: Device abort task at tag %d\n",
> > __func__, tag);
> >
> > /*
> > * Print detailed info about aborted request.
> > @@ -6462,6 +6448,17 @@ static int ufshcd_abort(struct scsi_cmnd
> > *cmd)
> > }
> > hba->req_abort_count++;
> >
> > + reg = ufshcd_readl(hba, REG_UTP_TRANSFER_REQ_DOOR_BELL);
> > + if (!(reg & (1 << tag))) {
> > + dev_err(hba->dev,
> > + "%s: cmd was completed, but without a notifying
> > intr,
> > tag = %d",
> > + __func__, tag);
> > + goto cleanup;
> > + }
> > +
> > + /* Print Transfer Request of aborted task */
> > + dev_err(hba->dev, "%s: Device abort task at tag %d\n",
> > __func__, tag);
> > +
>
> The rest looks good but let below two lines stay where they were.
>
> /* Print Transfer Request of aborted task */
> dev_err(hba->dev, "%s: Device abort task at tag %d\n",
> __func__, tag);
>
>
> Thanks,
>
> Can Guo.
>
Hi Can
I will change it in the next version.
Hi Stanly
would you mind I take your patch into my next version patchset? Since
we both will add a new same goto label. I will keep your patch
authorship.
Thanks,
Bean
next prev parent reply other threads:[~2020-08-10 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 12:35 Bean Huo
2020-08-06 9:03 ` Can Guo
2020-08-06 9:50 ` Bean Huo
2020-08-06 10:07 ` Can Guo
2020-08-10 15:41 ` Bean Huo [this message]
2020-08-10 23:13 ` Stanley Chu
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=5c6f1ad9f703cc5721e081452e869a9ee6bc4ab6.camel@gmail.com \
--to=huobean@gmail.com \
--cc=alim.akhtar@samsung.com \
--cc=asutoshd@codeaurora.org \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=stanley.chu@mediatek.com \
--cc=tomas.winkler@intel.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®