From: Alan Cox <alan@redhat.com>
To: benh@kernel.crashing.org
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox), alan@redhat.com (Alan Cox),
pavel@ucw.cz (Pavel Machek),
torvalds@transmeta.com (Linus Torvalds),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: swsusp: don't eat ide disks
Date: Sun, 3 Nov 2002 11:36:46 -0500 (EST) [thread overview]
Message-ID: <200211031636.gA3GakF14660@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021103162422.27845@smtp.wanadoo.fr> from "benh@kernel.crashing.org" at Nov 03, 2002 05:24:22 PM
> > Jump to PM layer "power off" logic
> >
> >If you do it that way up then no drivers need to be hacked about.
>
> Hrm... thanks to the miracle of having a BIOS that will deal
> with the grunt work of actually shutting down the chipsets,
> resuming them, etc...
As I said "jump to PM layer power off logic"
So after you have suspended you neatly power it all off
> I really don't like the above as it basically bypasse the
> bus ordering, which is the only sane way I see to deal with
> dependencies when the drivers are actually shutting down HW
Bus ordering applies to power off not to suspend to disk sequence
> Then, I volunteer writing a HOWTO explaining clearly what a
> driver should do for proper PM, and I'm pretty sure that won't
> be that nasty and race prone as you are afraid of ;)
Good. It'll be nice to have suspend to disk in 2.7
next prev parent reply other threads:[~2002-11-03 16:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 18:47 swsusp: don't eat ide disks Pavel Machek
2002-11-02 19:39 ` Linus Torvalds
2002-11-02 20:06 ` Alan Cox
2002-11-02 20:25 ` Pavel Machek
2002-11-02 22:04 ` Alan Cox
2002-11-03 20:11 ` Pavel Machek
2002-11-04 1:04 ` Rik van Riel
2002-11-06 12:34 ` Pavel Machek
2002-11-03 14:57 ` benh
2002-11-03 16:25 ` Alan Cox
2002-11-03 16:24 ` benh
2002-11-03 16:36 ` Alan Cox [this message]
2002-11-04 7:47 ` benh
2002-11-03 20:12 ` Pavel Machek
2002-11-03 21:33 ` Alan Cox
2002-11-03 22:09 ` Pavel Machek
2002-11-03 22:41 ` Alan Cox
2002-11-03 22:27 ` Pavel Machek
2002-11-03 23:56 ` Alan Cox
2002-11-04 8:16 ` benh
2002-11-04 13:33 ` Alan Cox
2002-11-03 22:48 ` Linus Torvalds
2002-11-03 22:53 ` Linus Torvalds
2002-11-04 8:08 ` benh
2002-11-04 14:59 ` Linus Torvalds
2002-11-04 15:27 ` Benjamin Herrenschmidt
2002-11-04 9:44 ` Jens Axboe
2002-11-04 13:37 ` Alan Cox
2002-11-03 22:56 ` Pavel Machek
2002-11-03 23:38 ` Linus Torvalds
2002-11-06 13:57 ` Pavel Machek
2002-11-04 7:57 ` benh
2002-11-04 9:39 ` Jens Axboe
2002-11-04 9:50 ` Jens Axboe
2002-11-07 13:06 ` David Woodhouse
2002-11-07 16:15 ` Pavel Machek
2002-11-07 16:18 ` David Woodhouse
2002-11-07 20:52 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 18:26 Grover, Andrew
2002-11-07 22:25 ` David Woodhouse
2002-11-08 11:09 ` Benjamin Herrenschmidt
2002-11-10 11:54 ` Pavel Machek
2002-11-11 6:38 ` David Woodhouse
2002-11-12 17:41 ` 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=200211031636.gA3GakF14660@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=torvalds@transmeta.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