lkml.org 
[lkml]   [2007]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH] Remove process freezer from suspend to RAM pathway
    From
    Date

    > On powerbooks you disable the nonboot CPUs before suspending devices, which
    > simplifies things _a_ _lot_ in comparison with the general case.

    Not that much actually. It avoids having to gather them all in the last
    stage at the low level but that isn't really related to what we are
    talking about right now.

    > If you additionally disable kernel preemption, then you don't need anything
    > like the freezer anyway in that case (except for detecting situations in which
    > the suspend process can deadlock with a task stuck in the D state holding a
    > lock, but that's overkill).

    kernel preemption and SMP have nothing to do with it. You can still
    schedule because one of the driver suspend() callback is schedul'ing,
    maybe waiting for some requests to complete, etc... Happens typically
    with the disk suspend callbacks.

    I agree that it does lower the likelyness of having a userspace process
    pound on the wrong driver at the wrong time though.

    Ben.


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-07-06 11:07    [W:4.165 / U:0.120 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site