| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1589336464.3197.68.camel@mtkswgap22>
Date: Wed, 13 May 2020 10:21:04 +0800
From: Stanley Chu <stanley.chu@...iatek.com>
To: "Asutosh Das (asd)" <asutoshd@...eaurora.org>
CC: <linux-scsi@...r.kernel.org>, <martin.petersen@...cle.com>,
<avri.altman@....com>, <alim.akhtar@...sung.com>,
<jejb@...ux.ibm.com>, <beanhuo@...ron.com>, <cang@...eaurora.org>,
<matthias.bgg@...il.com>, <bvanassche@....org>,
<linux-mediatek@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <kuohong.wang@...iatek.com>,
<peter.wang@...iatek.com>, <chun-hung.wu@...iatek.com>,
<andy.teng@...iatek.com>
Subject: Re: [PATCH v1 4/4] scsi: ufs: Fix WriteBooster flush during runtime
suspend
Hi Asutosh,
On Tue, 2020-05-12 at 10:04 -0700, Asutosh Das (asd) wrote:
> Hi Stanley,
>
> On 5/12/2020 3:47 AM, Stanley Chu wrote:
> > Currently UFS host driver promises VCC supply if UFS device
> > needs to do WriteBooster flush during runtime suspend.
> >
> > However the UFS specification mentions,
> >
> > "While the flushing operation is in progress, the device is
> > in Active power mode."
> >
> > Therefore UFS host driver needs to promise more: Keep UFS
> > device as "Active power mode", otherwise UFS device shall not
> > do any flush if device enters Sleep or PowerDown power mode.
> >
> > Fix this by not changing device power mode if WriteBooster
> > flush is required in ufshcd_suspend().
> >
> > Signed-off-by: Stanley Chu <stanley.chu@...iatek.com>
> > ---
> > drivers/scsi/ufs/ufs.h | 1 -
> > drivers/scsi/ufs/ufshcd.c | 39 +++++++++++++++++++--------------------
> > 2 files changed, 19 insertions(+), 21 deletions(-)
> >
> > diff --git a/drivers/scsi/ufs/ufs.h b/drivers/scsi/ufs/ufs.h
> > index b3135344ab3f..9e4bc2e97ada 100644
> > --- a/drivers/scsi/ufs/ufs.h
> > +++ b/drivers/scsi/ufs/ufs.h
> > @@ -577,7 +577,6 @@ struct ufs_dev_info {
> > u32 d_ext_ufs_feature_sup;
> > u8 b_wb_buffer_type;
> > u32 d_wb_alloc_units;
> > - bool keep_vcc_on;
> > u8 b_presrv_uspc_en;
> > };
> >
> > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c
> > index 169a3379e468..2d0aff8ac260 100644
> > --- a/drivers/scsi/ufs/ufshcd.c
> > +++ b/drivers/scsi/ufs/ufshcd.c
> > @@ -8101,8 +8101,7 @@ static void ufshcd_vreg_set_lpm(struct ufs_hba *hba)
> > !hba->dev_info.is_lu_power_on_wp) {
> > ufshcd_setup_vreg(hba, false);
> > } else if (!ufshcd_is_ufs_dev_active(hba)) {
> > - if (!hba->dev_info.keep_vcc_on)
> > - ufshcd_toggle_vreg(hba->dev, hba->vreg_info.vcc, false);
> > + ufshcd_toggle_vreg(hba->dev, hba->vreg_info.vcc, false);
> > if (!ufshcd_is_link_active(hba)) {
> > ufshcd_config_vreg_lpm(hba, hba->vreg_info.vccq);
> > ufshcd_config_vreg_lpm(hba, hba->vreg_info.vccq2);
> > @@ -8172,6 +8171,7 @@ static int ufshcd_suspend(struct ufs_hba *hba, enum ufs_pm_op pm_op)
> > enum ufs_pm_level pm_lvl;
> > enum ufs_dev_pwr_mode req_dev_pwr_mode;
> > enum uic_link_state req_link_state;
> > + bool keep_curr_dev_pwr_mode = false;
> >
> > hba->pm_op_in_progress = 1;
> > if (!ufshcd_is_shutdown_pm(pm_op)) {
> > @@ -8226,28 +8226,27 @@ static int ufshcd_suspend(struct ufs_hba *hba, enum ufs_pm_op pm_op)
> > /* make sure that auto bkops is disabled */
> > ufshcd_disable_auto_bkops(hba);
> > }
> > +
> > /*
> > - * With wb enabled, if the bkops is enabled or if the
> > - * configured WB type is 70% full, keep vcc ON
> > - * for the device to flush the wb buffer
> > + * If device needs to do BKOP or WB buffer flush, keep device
> > + * power mode as "active power mode" and its VCC supply.
> > */
> > - if ((hba->auto_bkops_enabled && ufshcd_is_wb_allowed(hba)) ||
> > - ufshcd_wb_keep_vcc_on(hba))
> > - hba->dev_info.keep_vcc_on = true;
> > - else
> > - hba->dev_info.keep_vcc_on = false;
> > - } else {
> > - hba->dev_info.keep_vcc_on = false;
> > + keep_curr_dev_pwr_mode = hba->auto_bkops_enabled ||
> > + ufshcd_wb_keep_vcc_on(hba);
> > }
> >
> > - if ((req_dev_pwr_mode != hba->curr_dev_pwr_mode) &&
> > - ((ufshcd_is_runtime_pm(pm_op) && !hba->auto_bkops_enabled) ||
> > - !ufshcd_is_runtime_pm(pm_op))) {
> > - /* ensure that bkops is disabled */
> > - ufshcd_disable_auto_bkops(hba);
> > - ret = ufshcd_set_dev_pwr_mode(hba, req_dev_pwr_mode);
> > - if (ret)
> > - goto enable_gating;
> > + if (req_dev_pwr_mode != hba->curr_dev_pwr_mode) {
> > + if ((ufshcd_is_runtime_pm(pm_op) && !hba->auto_bkops_enabled) ||
> > + !ufshcd_is_runtime_pm(pm_op)) {
> > + /* ensure that bkops is disabled */
> > + ufshcd_disable_auto_bkops(hba);
> > + }
> > +
> > + if (!keep_curr_dev_pwr_mode) {
> > + ret = ufshcd_set_dev_pwr_mode(hba, req_dev_pwr_mode);
> > + if (ret)
> > + goto enable_gating;
> > + }
> > }
> >
> > flush_work(&hba->eeh_work);
> >
>
> Can you please confirm that you've tested and found that with the
> previous code, the flush operation in the device was not happening.
>
> If so, please can you let me know the test-case that you ran to figure
> this out.
>
> I'd like to verify this at my end.
Sorry currently I have no easy test cases or scripts available.
To precisely confirm the flush behavior by logs, I added some codes to
query "available WriteBooster buffer" before entering runtime suspend
and after leaving runtime resume, and observe the trend of available
WriteBooster buffer.
My test steps are as below,
1. Create a writer to write large data in a short time to fill-in
WriteBooster buffer.
2. Do something to prevent system suspend
3. Do something to prevent link entering Hibern8, for example, disable
Auto-Hibern8 and disable Hibern8 during clock gating. Because the
Hibern8 period before runtime-suspend is known that VCC is provided and
device can flush WriteBooster buffer if "Flush During H8" is enabled as
upstream kernel currently.
4. Shrink the runtime suspend delay (maybe 100ms ~ 200ms) to make
runtime suspend happen earlier.
5. After "available WriteBosoter buffer" reaches lower-level, for
example, 10%, stop the writer.
6. Observe the trend of WriteBooster available buffer.
In the previous code, the available WriteBooster buffer is increased
very very slowly. Especially no increasing is observed during
runtime-suspend.
After applying this fix, the available WriteBooster buffer is increased
much faster and the increasing can be easily observed during
runtime-suspend.
Thanks,
Stanley Chu
>
> --
> Thanks,
> -asd
>
Powered by blists - more mailing lists