linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	linux-scsi@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH 0/9] Rework runtime suspend and SCSI domain validation
Date: Fri, 18 Sep 2020 20:45:19 -0700	[thread overview]
Message-ID: <f4ff6be8-84b6-6f08-8657-21238c99df9c@acm.org> (raw)
In-Reply-To: <20200906012219.17893-1-bvanassche@acm.org>

On 2020-09-05 18:22, Bart Van Assche wrote:
> The SCSI runtime suspend and domain validation mechanisms both use
> scsi_device_quiesce(). scsi_device_quiesce() restricts blk_queue_enter() to
> BLK_MQ_REQ_PREEMPT requests. There is a conflict between the requirements
> of runtime suspend and SCSI domain validation: no requests must be sent to
> runtime suspended devices that are in the state RPM_SUSPENDED while
> BLK_MQ_REQ_PREEMPT requests must be processed during SCSI domain
> validation. This conflict is resolved by reworking the SCSI domain
> validation implementation.
> 
> Hybernation and runtime suspend have been retested but SCSI domain
> validation not yet.

Hi Martin and James,

Please advise how to proceed with this patch series. This patch series
includes an important fix for runtime power management. Unfortunately
the only way to fix runtime powermanagement is by reworking SPI DV and
I don't have access to a setup on which I can test the SPI DV changes.

Thanks,

Bart.

  parent reply	other threads:[~2020-09-19  3:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06  1:22 [PATCH 0/9] Rework runtime suspend and SCSI domain validation Bart Van Assche
2020-09-06  1:22 ` [PATCH 1/9] block: Fix a race in the runtime power management code Bart Van Assche
2020-09-06  1:22 ` [PATCH 2/9] ide: Do not set the RQF_PREEMPT flag for sense requests Bart Van Assche
2020-09-06  1:22 ` [PATCH 3/9] scsi: Pass a request queue pointer to __scsi_execute() Bart Van Assche
2020-09-06  1:22 ` [PATCH 4/9] scsi: Rework scsi_mq_alloc_queue() Bart Van Assche
2020-09-06  1:22 ` [PATCH 5/9] scsi: Do not wait for a request in scsi_eh_lock_door() Bart Van Assche
2020-09-06 16:03   ` Alan Stern
2020-09-06  1:22 ` [PATCH 6/9] scsi_transport_spi: Make spi_execute() accept a request queue pointer Bart Van Assche
2020-09-06  1:22 ` [PATCH 7/9] scsi_transport_spi: Freeze request queues instead of quiescing Bart Van Assche
2020-09-09  3:51   ` Bart Van Assche
2020-09-06  1:22 ` [PATCH 8/9] block, scsi, ide: Only process PM requests if rpm_status != RPM_ACTIVE Bart Van Assche
2020-09-06  1:22 ` [PATCH 9/9] block: Do not accept any requests while suspended Bart Van Assche
2020-09-06 16:06 ` [PATCH 0/9] Rework runtime suspend and SCSI domain validation Alan Stern
2020-09-19  3:45 ` Bart Van Assche [this message]
2020-09-21  6:00   ` Hannes Reinecke
2020-09-30  2:47     ` Martin K. Petersen
2020-09-29 12:33   ` Martin Kepplinger

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=f4ff6be8-84b6-6f08-8657-21238c99df9c@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=stern@rowland.harvard.edu \
    /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).