[lkml]   [2007]   [Jul]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjecthibernation/snapshot design [was Re: [PATCH] Remove process freezer from suspend to RAM pathway]

    > > 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 hibernation-specific
    > > equivalent) for hibernation (in that case there shouldn't be a problem with
    > > any task waiting on I/O while the freezer is running ;-)).
    > I don't see the need for a freezer for snapshot but that's a different
    > issue. (stop_machine looks good enough to me).

    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).

    (cesky, pictures)
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-07-09 00:15    [W:0.036 / U:0.732 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site