Nigel Cunningham writes:
> (Finally catching up on emails since Saturday!)
Yes, I know what you mean; I was occupied with other work stuff on
Friday and not well on Saturday, and by that stage there was a backlog
of about 500 emails for me to wade through... :/
> The freezer is also essential fo
Hi.
On Monday 09 July 2007 09:01:27 Rafael J. Wysocki wrote:
> Hi,
>
> On Monday, 9 July 2007 00:13, Pavel Machek wrote:
> > Hi!
> >
> > > > Actaully, I'm perfectly fine with that, as long as each task blocked
by the
> > > > driver due to suspend has PF_FROZEN (or something similar) set. Then,
On Mon, 9 Jul 2007, Pavel Machek wrote:
On Sun 2007-07-08 16:20:46, [EMAIL PROTECTED] wrote:
On Mon, 9 Jul 2007, Pavel Machek wrote:
Actaully, I'm perfectly fine with that, as long as each task blocked by
the
driver due to suspend has PF_FROZEN (or something similar) set. Then,
at
least theo
On Sun 2007-07-08 16:20:46, [EMAIL PROTECTED] wrote:
> On Mon, 9 Jul 2007, Pavel Machek wrote:
>
> >Actaully, I'm perfectly fine with that, as long as each task blocked by
> >the
> >driver due to suspend has PF_FROZEN (or something similar) set. Then,
> >at
> >least theoretic
On Mon, 9 Jul 2007, Pavel Machek wrote:
Actaully, I'm perfectly fine with that, as long as each task blocked by
the
driver due to suspend has PF_FROZEN (or something similar) set. Then, at
least theoretically, we'll be able to drop the freezer from the suspend
code
path and move it after device
Hi!
> > Freezer is not needed for snapshot -- it is needed so that we can
> > write out the snapshot to disk without the need for special
> > drivers/block/simple-ide-for-suspend.c. (We are doing snapshot, then
> > write to disk from userland code in uswsusp).
>
> Yes.
>
> BTW, this patch:
>
>
Hi!
> >>>Actaully, I'm perfectly fine with that, as long as each task blocked by
> >>>the
> >>>driver due to suspend has PF_FROZEN (or something similar) set. Then, at
> >>>least theoretically, we'll be able to drop the freezer from the suspend
> >>>code
> >>>path and move it after device_suspe
Hi,
On Monday, 9 July 2007 00:13, Pavel Machek wrote:
> Hi!
>
> > > Actaully, I'm perfectly fine with that, as long as each task blocked by
> > > the
> > > driver due to suspend has PF_FROZEN (or something similar) set. Then, at
> > > least theoretically, we'll be able to drop the freezer from
On Mon, 9 Jul 2007, Pavel Machek wrote:
Actaully, I'm perfectly fine with that, as long as each task blocked by the
driver due to suspend has PF_FROZEN (or something similar) set. Then, at
least theoretically, we'll be able to drop the freezer from the suspend code
path and move it after device
Hi!
> > Actaully, I'm perfectly fine with that, as long as each task blocked by the
> > driver due to suspend has PF_FROZEN (or something similar) set. Then, at
> > least theoretically, we'll be able to drop the freezer from the suspend code
> > path and move it after device_suspend() (or the hib
10 matches
Mail list logo
