On Thu, 26 Apr 2007, Pavel Machek wrote:
> >
> > Why? Becuase there is no _room_ for inconsistency. There's nothing to be
> > "inconsistent with", since any changes to memory (by things like DMA or
> > other setup that happens while the suspend process is going on) is by
> > _definition_ consistent with the resume image (becasue there is no
> > separate image).
>
> Do you propose to keep DMAs running while suspending-to-RAM?
What part of "suspend a chip" do you have trouble with?
DMA obviously does *not* happen with a suspended device. There's no need
to turn DMA even off - it just doesn't happen!
> > For example, the whole myth that "freeze" needs to shut off DMA is a total
> > and utter *myth*. It needs nothing of the sort at all. Rather than shut
> > off DMA and try to make the hardware be wevy wevy quiet while it's hunting
> > wabbits, it's a lot easier to just do nothing at all on "freeze",
>
> No. Sorry, you are wrong here.
>
> Remember that during resume we run
>
> freeze()
> copy old data into memory
> thaw()
>
> Now, if the old kernel left DMAs running, it could be overwriting
> the data we are copying in.
The *thaw* needs to happen with devices quiescent.
But that sure doesn't have anythign to do with the "snapshot()" path. In
fact, you'll have rebooted the machine in between.
So what does that have to do with "snapshotting"?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
