Re: [linux-pm] Re: Hibernation considerations
- From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jul 2007 12:20:58 -0400 (EDT)
On Fri, 20 Jul 2007, Milton Miller wrote:
We can't do this unless we have frozen tasks (this way, or another)
before
carrying out the entire operation.
What can't we do? We've already worked with the drivers to quesce the
hardware and put any information to resume the device in ram. Now we
ask them to put their device in low power mode so we can go to sleep.
Even if we schedule, the only thing userspace could touch is memory.
Userspace can submit I/O requests. Someone will have to audit every
driver to make sure that such I/O requests don't cause a quiesced
device to become active. If the device is active, it will make the
memory snapshot inconsistent with the on-device data.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [linux-pm] Re: Hibernation considerations
- From: david
- Re: [linux-pm] Re: Hibernation considerations
- From: Milton Miller
- Re: [linux-pm] Re: Hibernation considerations
- References:
- Re: [linux-pm] Re: Hibernation considerations
- From: Milton Miller
- Re: [linux-pm] Re: Hibernation considerations
- Prev by Date: RE: [PATCH 4/7] I/OAT: Split PCI startup from DMA handling code
- Next by Date: Re: Regression with sys_time() speedup patch
- Previous by thread: Re: [linux-pm] Re: Hibernation considerations
- Next by thread: Re: [linux-pm] Re: Hibernation considerations
- Index(es):
Relevant Pages
|