Talking with some people last night it seems we need to redo the swsusp (driver). From what I've been told and have seen (from the code) it doesn't talk to the generic subsystems (like block layer, network layer etc). From talks with some kernel developers, they tell me we would have to modify all the drivers to properly handle system suspends. Is it not APM/ACPI's job to bring down the system to a stable state when suspending the machine?
The swsusp should be asking all the generic subsystems. When the machine is about to be suspended it should flush any read/write buffers, stop processing packets and other things.
Am I totally wrong on this? :-)
Shawn.
Shawn Starr
Development Systems Support Analyst, Operations
T: 416-213-2001 ext 179 F: 416-213-2008
[email protected]
http://www.datawire.net
"Sent from my Blackberry handheld"
Make that: Tell all generic subsystems to clear their buffers out and tell other subsystems they are not available. Suspend first then APM/ACPI last. Perhaps we need some sort of flag states to let other kernel subsystems know not to bother asking for requests. The kernel could preempt each subsystem and bring them down in a safe order no?
Shawn.
-----Original Message-----
From: "Shawn Starr" <[email protected]>
Date: Mon, 4 Nov 2002 11:31:42
To: [email protected]
Subject: Call to rewrite swsusp
Talking with some people last night it seems we need to redo the swsusp (driver). From what I've been told and have seen (from the code) it doesn't talk to the generic subsystems (like block layer, network layer etc). From talks with some kernel developers, they tell me we would have to modify all the drivers to properly handle system suspends. Is it not APM/ACPI's job to bring down the system to a stable state when suspending the machine?
The swsusp should be asking all the generic subsystems. When the machine is about to be suspended it should flush any read/write buffers, stop processing packets and other things.
Am I totally wrong on this? :-)
Shawn.
Shawn Starr
Development Systems Support Analyst, Operations
T: 416-213-2001 ext 179 F: 416-213-2008
[email protected]
http://www.datawire.net
"Sent from my Blackberry handheld"
Shawn Starr
Development Systems Support Analyst, Operations
T: 416-213-2001 ext 179 F: 416-213-2008
[email protected]
http://www.datawire.net
"Sent from my Blackberry handheld"
> Talking with some people last night it seems we need to redo the
> swsusp (driver). From what I've been told and have seen (from the
> code) it doesn't talk to the generic subsystems (like block layer,
> network layer etc). From talks with some kernel developers, they
> tell me we would have to modify all the drivers to properly handle
> system suspends. Is it not APM/ACPI's job to bring down the system
> to a stable state when suspending the machine?
> The swsusp should be asking all the generic subsystems. When the
> machine is about to be suspended it should flush any read/write
> buffers, stop processing packets and other things.
> Am I totally wrong on this? :-)
Yes.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?