All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
	peterz@infradead.org, mingo@kernel.org,
	Mike Galbraith <efault@gmx.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 1/2] sched: fix init NOHZ_IDLE flag
Date: Mon, 18 Feb 2013 15:33:26 +0100	[thread overview]
Message-ID: <CAFTL4hzu-7uAXLqP+J48DaqLUYQWTESMNwPMYiiwrU2ZoOsgqw@mail.gmail.com> (raw)
In-Reply-To: <CAKfTPtCWudftS2XSM1OC2sR050mYvcAU6Fkt0vjV=C2V+w84Ew@mail.gmail.com>

2013/2/8 Vincent Guittot <vincent.guittot@linaro.org>:
> On 8 February 2013 16:35, Frederic Weisbecker <fweisbec@gmail.com> wrote:
>> What if the following happen (inventing function names but you get the idea):
>>
>> CPU 0                                           CPU 1
>>
>> dom = new_domain(...) {
>>            nr_cpus_busy = 0;
>>            set_idle(CPU 1);                  old_dom =get_dom()
>>                                                      clear_idle(CPU 1)
>> }
>> rcu_assign_pointer(cpu1_dom, dom);
>>
>>
>> Can this scenario happen?
>
> This scenario will be:
>
>  CPU 0                                           CPU 1
>
>  detach_and_destroy_domain {
>             rcu_assign_pointer(cpu1_dom, NULL);
>  }
>
>  dom = new_domain(...) {
>             nr_cpus_busy = 0;
>             set_idle(CPU 1);                  old_dom =get_dom()
>                                                       old_dom is null
>                                                       //clear_idle(CPU
> 1) can't happen because a null domain is attached so we will never
> call nohz_kick_needed which is the only place where we can clear_idle
>  }
>  rcu_assign_pointer(cpu1_dom, dom);

So is the following possible?

= CPU 0 =                                                       = CPU 1=

detach_and_destroy_domain {
            rcu_assign_pointer(cpu1_dom, NULL);
}

dom = new_domain(...) {
             nr_cpus_busy = 0;
             set_idle(CPU 1);
}

clear_idle(CPU 1)

dom = rcu_dereference(cpu1_dom)

//dom == NULL, return

rcu_assign_pointer(cpu1_dom, NULL);


set_idle(CPU 1)

dom = rcu_dereference(cpu1_dom)

//dec nr_cpus_busy, making it negative

  reply	other threads:[~2013-02-18 14:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 10:38 [PATCH v2 0/2] sched: fix nr_busy_cpus Vincent Guittot
2013-01-29 10:38 ` [PATCH v2 1/2] sched: fix init NOHZ_IDLE flag Vincent Guittot
2013-02-01 18:03   ` Frederic Weisbecker
2013-02-04  9:09     ` Vincent Guittot
2013-02-08 15:35       ` Frederic Weisbecker
2013-02-08 17:09         ` Vincent Guittot
2013-02-18 14:33           ` Frederic Weisbecker [this message]
2013-02-18 14:38             ` Frederic Weisbecker
2013-02-18 15:06               ` Vincent Guittot
2013-02-18 15:40                 ` Frederic Weisbecker
2013-02-19 10:29                   ` Vincent Guittot
2013-02-19 10:56                     ` Vincent Guittot
2013-01-29 10:39 ` [PATCH v2 2/2] sched: fix update " Vincent Guittot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFTL4hzu-7uAXLqP+J48DaqLUYQWTESMNwPMYiiwrU2ZoOsgqw@mail.gmail.com \
    --to=fweisbec@gmail.com \
    --cc=efault@gmx.de \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.