From: Avri Altman <Avri.Altman@wdc.com>
To: Stanley Chu <stanley.chu@mediatek.com>,
Bart Van Assche <bvanassche@acm.org>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"alim.akhtar@samsung.com" <alim.akhtar@samsung.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kuohong.wang@mediatek.com" <kuohong.wang@mediatek.com>,
"peter.wang@mediatek.com" <peter.wang@mediatek.com>,
"chun-hung.wu@mediatek.com" <chun-hung.wu@mediatek.com>,
"andy.teng@mediatek.com" <andy.teng@mediatek.com>,
"chaotian.jing@mediatek.com" <chaotian.jing@mediatek.com>,
"cc.chou@mediatek.com" <cc.chou@mediatek.com>
Subject: RE: [RFC PATCH v3] scsi: ufs: Quiesce all scsi devices before shutdown
Date: Mon, 27 Jul 2020 10:46:49 +0000 [thread overview]
Message-ID: <SN6PR04MB46401CB0D89FFD24496B33A6FC720@SN6PR04MB4640.namprd04.prod.outlook.com> (raw)
In-Reply-To: <1595409534.27178.19.camel@mtkswgap22>
>
> Hi Bart,
>
> On Sat, 2020-07-11 at 20:21 -0700, Bart Van Assche wrote:
> > On 2020-07-06 06:22, Stanley Chu wrote:
> > > +static void ufshcd_cleanup_queue(struct scsi_device *sdev, void *data)
> > > +{
> > > + if (sdev->request_queue)
> > > + blk_cleanup_queue(sdev->request_queue);
> > > +}
> >
> > No SCSI LLD should ever call blk_cleanup_queue() directly for
> > sdev->request_queue. Only the SCSI core should call blk_cleanup_queue()
> > directly for that queue.
>
> Got it.
>
> So may I focus on fixing racing first by quiecsing all SCSI devices only
> and do not touch blk_cleanup_queue() in UFS driver, just like v2?
>
>
> > > int ufshcd_shutdown(struct ufs_hba *hba)
> > > {
> > > int ret = 0;
> > > + struct scsi_target *starget;
> > >
> > > if (!hba->is_powered)
> > > goto out;
> > > @@ -8612,7 +8632,25 @@ int ufshcd_shutdown(struct ufs_hba *hba)
> > > goto out;
> > > }
> > >
> > > + /*
> > > + * Quiesce all SCSI devices to prevent any non-PM requests sending
> > > + * from block layer during and after shutdown.
> > > + *
> > > + * Here we can not use blk_cleanup_queue() since PM requests
> > > + * (with BLK_MQ_REQ_PREEMPT flag) are still required to be sent
> > > + * through block layer. Therefore SCSI command queued after the
> > > + * scsi_target_quiesce() call returned will block until
> > > + * blk_cleanup_queue() is called.
> > > + *
> > > + * Besides, scsi_target_"un"quiesce (e.g., scsi_target_resume) can
> > > + * be ignored since shutdown is one-way flow.
> > > + */
> > > + ufshcd_scsi_for_each_sdev(ufshcd_quiece_sdev);
> > > +
> > > ret = ufshcd_suspend(hba, UFS_SHUTDOWN_PM);
> > > +
> > > + /* Set queue as dying to not block queueing commands */
> > > + ufshcd_scsi_for_each_sdev(ufshcd_cleanup_queue);
> > > out:
> > > if (ret)
> > > dev_err(hba->dev, "%s failed, err %d\n", __func__, ret);
> > >
> >
> > What is the purpose of ufshcd_shutdown()? Why does this function exist?
> > How about removing the calls to ufshcd_shutdown() and invoking power
> down
> > code from inside sd_suspend_common() instead?
>
> ufshcd_shutdown() configures below things different from or more than
> what sd_suspend_common() can do now,
>
> - Set link as OFF state
> - Regulator and clock toggling according to required low-power state for
> shutdown
> - Auto BKOP toggling
> - Vendor-specific shutdown flow ...etc.
>
> Therefore UFS shutdown callback would be still required.
And this is also why, that each chipset vendor implement its own dev_pm_ops.
Thanks,
Avri
>
> Thanks,
> Stanley Chu
prev parent reply other threads:[~2020-07-27 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 13:22 [RFC PATCH v3] scsi: ufs: Quiesce all scsi devices before shutdown Stanley Chu
2020-07-12 1:31 ` Stanley Chu
2020-07-12 3:21 ` Bart Van Assche
2020-07-22 9:18 ` Stanley Chu
2020-07-27 10:46 ` Avri Altman [this message]
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=SN6PR04MB46401CB0D89FFD24496B33A6FC720@SN6PR04MB4640.namprd04.prod.outlook.com \
--to=avri.altman@wdc.com \
--cc=alim.akhtar@samsung.com \
--cc=andy.teng@mediatek.com \
--cc=asutoshd@codeaurora.org \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=cang@codeaurora.org \
--cc=cc.chou@mediatek.com \
--cc=chaotian.jing@mediatek.com \
--cc=chun-hung.wu@mediatek.com \
--cc=jejb@linux.ibm.com \
--cc=kuohong.wang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matthias.bgg@gmail.com \
--cc=peter.wang@mediatek.com \
--cc=stanley.chu@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;
as well as URLs for NNTP newsgroup(s).