lkml.org 
[lkml]   [2011]   [Jan]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC][PATCH 07/17] sched: Serialize p->cpus_allowed and ttwu() using p->pi_lock
    From
    Date
    On Wed, 2010-12-29 at 22:20 +0800, Yong Zhang wrote:
    > > - * The caller (fork, wakeup) owns TASK_WAKING, ->cpus_allowed is stable.
    > > + * The caller (fork, wakeup) owns p->pi_lock, ->cpus_allowed is stable.
    >
    > Yes for wakeup, but not true for fork.
    > I don't see protection in wake_up_new_task().
    > Or am I missing something?

    Ah, true, wake_up_new_task() holds task_rq_lock() which is sufficient,
    but yes, we could also make that pi_lock.




    \
     
     \ /
      Last update: 2011-01-03 12:15    [W:3.734 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site