public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <dlemoal@kernel.org>, linux-ide@vger.kernel.org
Cc: linux-scsi@vger.kernel.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	John Garry <john.g.garry@oracle.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Paul Ausbeck <paula@soe.ucsc.edu>,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Joe Breuer <linux-kernel@jmbreuer.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Chia-Lin Kao <acelan.kao@canonical.com>
Subject: Re: [PATCH v3 04/23] scsi: sd: Differentiate system and runtime start/stop management
Date: Fri, 15 Sep 2023 14:26:35 +0200	[thread overview]
Message-ID: <0aa09483-20be-d868-3a89-352c2f793031@suse.de> (raw)
In-Reply-To: <20230915081507.761711-5-dlemoal@kernel.org>

On 9/15/23 10:14, Damien Le Moal wrote:
> The underlying device and driver of a scsi disk may have different
> system and runtime power mode control requirements. This is because
> runtime power management affects only the scsi disk, while sustem level
> power management affects all devices, including the controller for the
> scsi disk.
> 
> For instance, issuing a START STOP UNIT command when a scsi disk is
> runtime suspended and resumed is fine: the command is translated to a
> STANDBY IMMEDIATE command to spin down the ATA disk and to a VERIFY
> command to wake it up. The scsi disk runtime operations have no effect
> on the ata port device used to connect the ATA disk. However, for
> system suspend/resume operations, the ATA port used to connect the
> device will also be suspended and resumed, with the resum operation
> requiring re-validating the device link and the device itseld. In this
> case, issuing a VERIFY command to spinup the disk must be done before
> starting to revalidate the device, when the ata port is being resumed.
> In such case, we must not allow the scsi disk driver to issue START STOP
> UNIT commands.
> 
> Allow a low level driver to refine the scsi disk start/stop management
> by differentiating system and runtime cases with two new scsi device
> flags: manage_system_start_stop and manage_runtime_start_stop. These new
> flags replace the current manage_start_stop flag. Drivers setting the
> manage_start_stop are modifed to set both new flags, thus preserving the
> existing start/stop management behavior.
> 
> Fixes: 0a8589055936 ("ata,scsi: do not issue START STOP UNIT on resume")
> Cc: stable@vger.kernel.org
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
> ---
>   drivers/ata/libata-scsi.c  |  3 +-
>   drivers/firewire/sbp2.c    |  9 +++--
>   drivers/scsi/sd.c          | 78 ++++++++++++++++++++++++++++----------
>   include/scsi/scsi_device.h |  3 +-
>   4 files changed, 69 insertions(+), 24 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		           Kernel Storage Architect
hare@suse.de			                  +49 911 74053 688
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg
Managing Directors: I. Totev, A. Myers, A. McDonald, M. B. Moerman
(HRB 36809, AG Nürnberg)


  reply	other threads:[~2023-09-15 12:26 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  8:14 [PATCH v3 00/23] Fix libata suspend/resume handling and code cleanup Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 01/23] ata: libata-core: Fix ata_port_request_pm() locking Damien Le Moal
2023-09-19 13:21   ` Niklas Cassel
2023-09-19 16:31     ` Damien Le Moal
2023-09-20  7:21       ` Niklas Cassel
2023-09-20  7:30         ` Niklas Cassel
2023-09-20 10:22           ` Damien Le Moal
2023-09-20 10:20         ` Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 02/23] ata: libata-core: Fix port and device removal Damien Le Moal
2023-09-19 13:21   ` Niklas Cassel
2023-09-19 17:42     ` Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 03/23] ata: libata-scsi: link ata port and scsi device Damien Le Moal
2023-09-19 13:21   ` Niklas Cassel
2023-09-19 16:27     ` Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 04/23] scsi: sd: Differentiate system and runtime start/stop management Damien Le Moal
2023-09-15 12:26   ` Hannes Reinecke [this message]
2023-09-15  8:14 ` [PATCH v3 05/23] ata: libata-scsi: Disable scsi device manage_system_start_stop Damien Le Moal
2023-09-15 12:27   ` Hannes Reinecke
2023-09-15  8:14 ` [PATCH v3 06/23] scsi: Do not attempt to rescan suspended devices Damien Le Moal
2023-09-15 12:29   ` Hannes Reinecke
2023-09-19 13:59   ` Niklas Cassel
2023-09-15  8:14 ` [PATCH v3 07/23] ata: libata-scsi: Fix delayed scsi_rescan_device() execution Damien Le Moal
2023-09-15 12:29   ` Hannes Reinecke
2023-09-19 14:00   ` Niklas Cassel
2023-09-15  8:14 ` [PATCH v3 08/23] ata: libata-core: Do not register PM operations for SAS ports Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 09/23] scsi: sd: Do not issue commands to suspended disks on shutdown Damien Le Moal
2023-09-15 12:30   ` Hannes Reinecke
2023-09-15 14:31   ` Bart Van Assche
2023-09-15  8:14 ` [PATCH v3 10/23] ata: libata-core: Fix compilation warning in ata_dev_config_ncq() Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 11/23] ata: libata-eh: Fix compilation warning in ata_eh_link_report() Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 12/23] scsi: Remove scsi device no_start_on_resume flag Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 13/23] ata: libata-scsi: Cleanup ata_scsi_start_stop_xlat() Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 14/23] ata: libata-core: Synchronize ata_port_detach() with hotplug Damien Le Moal
2023-09-15  8:14 ` [PATCH v3 15/23] ata: libata-core: Detach a port devices on shutdown Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 16/23] ata: libata-core: Remove ata_port_suspend_async() Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 17/23] ata: libata-core: Remove ata_port_resume_async() Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 18/23] ata: libata-core: Do not poweroff runtime suspended ports Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 19/23] ata: libata-core: Do not resume " Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 20/23] ata: libata-sata: Improve ata_sas_slave_configure() Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 21/23] ata: libata-eh: Improve reset error messages Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 22/23] ata: libata-eh: Reduce "disable device" message verbosity Damien Le Moal
2023-09-15  8:15 ` [PATCH v3 23/23] ata: libata: Cleanup inline DMA helper functions Damien Le Moal

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=0aa09483-20be-d868-3a89-352c2f793031@suse.de \
    --to=hare@suse.de \
    --cc=acelan.kao@canonical.com \
    --cc=dlemoal@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=john.g.garry@oracle.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@jmbreuer.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=paula@soe.ucsc.edu \
    --cc=rodrigo.vivi@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