[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201009022228.07626.rjw@sisk.pl>
Date: Thu, 2 Sep 2010 22:28:07 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Tejun Heo <htejun@...il.com>
Cc: Stephan Diestelhorst <stephan.diestelhorst@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
"linux-pm@...ts.osdl.org" <linux-pm@...ts.osdl.org>,
Stephan Diestelhorst <stephan.diestelhorst@...il.com>
Subject: Re: [PATCH] libata: skip EH autopsy and recovery during suspend
On Thursday, September 02, 2010, Tejun Heo wrote:
> Hello,
>
> On 09/02/2010 10:16 PM, Rafael J. Wysocki wrote:
> > Putting the issue at hand aside, I'm not really sure if using SCSI EH for
> > suspending the controller is a good idea. It seems overly complicated and
> > it doesn't match the new PCI suspend model with separate ->suspend(),
> > ->freeze() and ->poweroff() callbacks. Moreover, the passing of pm_message_t
> > back and forth doesn't make things clear either.
> >
> > Would it be possible to rework this thing entirely at one point?
>
> Well, I think I would need more than that to rework the whole thing.
> There are a lot of benefits in sharing the same path between probing /
> error handling and suspend/resuming. ATA has a lot of quirks which
> have to be dealt with and it will be very fragile to scatter handling
> logics over multiple separate paths. We definitely can try to make
> the plumbing from power management easier to follow.
That would be very nice. In particular, I'd like to get rid of the
pm_message_t thing if possible. And I'd like to avoid putting the
controller into D3 before creating hibernation image. :-)
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists