[lkml]   [2007]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] Cpu-hotplug: Using the Process Freezer (try2)
    On Mon, Apr 02, 2007 at 08:16:12AM +0200, Ingo Molnar wrote:
    > hm, shouldnt the make be frozen immediately?
    > doesnt the 'please freeze ASAP' flag get propagated to all tasks,
    > immediately? After that point any cloning activity should duplicate that
    > flag too, resulting in any new child freezing immediately too.

    afaics, setting the 'please freeze asap' flag is racy wrt dup_task_struct
    (where the child's tsk->thread_info->flags are copied from its parent?).
    Secondly, from what I understand, it takes a 'flag to be set + signal marked
    pending' for the child task to be frozen. If that is the case, then
    copy_process may not propogae the signal to the child, which could mean
    mean that we can be in a catch-up game in freeze_processes, trying to
    freeze processes we didnt see in earlier passes.

    I think copy_process() can check for something like this:



    if (freezing(current))
    freeze_process(p); /* function exported by freezer */



    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-04-02 11:23    [W:2.262 / U:0.664 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site