Re: Solving suspend-level confusion

[David Brownell]

On Thursday 05 August 2004 23:13, Nigel Cunningham wrote:

> > > device_resume_tree(&default_device_tree);
> > > 
> > > Proof of the pudding coming :>
> > 
> > Sounds good.  Will it be possible to remove devices during
> > these tree operations?  Probably never the current one.
> 
> Ummm. I suppose so. It's only affecting the PM section and not the
> device tree proper, so I don't see why it should cause any failures.

If you're not changing dpm_sem usage, it's a self-deadlock
situation.  I guess that bug needs to be fixed in its own right.


> > And (evil chuckle) how will it behave if two tasks are doing
> > that concurrently?  The no-overlap case would be fully
> > parallel, I'd hope!
> 
> All of the operations still use dpm_sem, so really strange things
> shouldn't happen. That said, if you're trying to suspend to disk and ram
> at the same time, you get what you deserve, 

Telling one subsystem to suspend as deeply as possible doesn't
mean no other subsystem will be needed much sooner.  And
why you'd suspend a system "to disk" when the system only
has some flash ram?  :)

- Dave
-
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/