From: Oliver Neukum <oneukum@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org,
James.Bottomley@hansenpartnership.com,
linux-kernel@vger.kernel.org, teheo@novell.com,
stefanr@s5r6.in-berlin.de, Martin.Leisner@xerox.com
Subject: Re: autosuspend for SCSI devices
Date: Thu, 28 Aug 2008 23:17:37 +0200 [thread overview]
Message-ID: <200808282317.38703.oneukum@suse.de> (raw)
In-Reply-To: <20080828080427.GD15474@elf.ucw.cz>
Am Donnerstag 28 August 2008 10:04:27 schrieb Pavel Machek:
> On Tue 2008-08-26 13:01:43, Oliver Neukum wrote:
> > Am Dienstag 26 August 2008 11:43:55 schrieb Pavel Machek:
> > > > firstly, it doesn't consider error handling before suspending.
> > >
> > > What problems do you see with error handling? This patch does not
> > > touch the error handling, and I do not think it needs to touch it.
> >
> > You'd make scsi driver writers' life easier if you made sure no autosuspends
> > happen while they recover from errors. After all, you have no idea which
> > commands will get through while the bus is in disarray.
>
> Well, they have to handle other commands while bus has problems,
> anyway, right? So I'm not creating any _new_ problems for them.
>
> Pavel
I am afraid this is not true.
Regards
Oliver
/**
* scsi_block_when_processing_errors - Prevent cmds from being queued.
* @sdev: Device on which we are performing recovery.
*
* Description:
* We block until the host is out of error recovery, and then check to
* see whether the host or the device is offline.
*
* Return value:
* 0 when dev was taken offline by error recovery. 1 OK to proceed.
*/
int scsi_block_when_processing_errors(struct scsi_device *sdev)
/**
* scsi_restart_operations - restart io operations to the specified host.
* @shost: Host we are restarting.
*
* Notes:
* When we entered the error handler, we blocked all further i/o to
* this device. we need to 'reverse' this process.
*/
static void scsi_restart_operations(struct Scsi_Host *shost)
next prev parent reply other threads:[~2008-08-28 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 10:56 autosuspend for SCSI devices Pavel Machek
2008-08-22 20:52 ` Rafael J. Wysocki
2008-08-25 8:19 ` Pavel Machek
2008-08-25 8:55 ` Oliver Neukum
2008-08-26 9:43 ` Pavel Machek
2008-08-26 11:01 ` Oliver Neukum
2008-08-28 8:04 ` Pavel Machek
2008-08-28 21:17 ` Oliver Neukum [this message]
2008-09-02 9:08 ` Pavel Machek
2008-09-02 9:39 ` Oliver Neukum
2008-09-02 14:04 ` [linux-pm] " Alan Stern
2008-08-25 19:47 ` Tino Keitel
2008-08-26 9:44 ` Pavel Machek
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=200808282317.38703.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=Martin.Leisner@xerox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=stefanr@s5r6.in-berlin.de \
--cc=teheo@novell.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