From: Gautham R Shenoy <ego@in.ibm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
dipankar@in.ibm.com, Gautham Shenoy <ego@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, vatsa@in.ibm.com
Subject: Re: Fw: Re: [mm PATCH 4/6] RCU: (now) CPU hotplug
Date: Tue, 30 Jan 2007 19:32:27 +0530 [thread overview]
Message-ID: <20070130140227.GB7113@in.ibm.com> (raw)
In-Reply-To: <20070130024549.GL1923@linux.vnet.ibm.com>
On Mon, Jan 29, 2007 at 06:45:49PM -0800, Paul E. McKenney wrote:
>
> static int _cpu_down(unsigned int cpu)
> {
> int err;
> struct task_struct *p;
> cpumask_t old_allowed, tmp;
>
> if (num_online_cpus() == 1)
> return -EBUSY;
>
> if (!cpu_online(cpu))
> return -EINVAL;
>
> if (freeze_processes()) {
> err = -EBUSY;
> goto out_freeze_notify_failed;
> }
> err = raw_notifier_call_chain(&cpu_chain, CPU_DOWN_PREPARE,
> (void *)(long)cpu);
> if (err == NOTIFY_BAD) {
> printk("%s: attempt to take down CPU %u failed\n",
> __FUNCTION__, cpu);
> err = -EINVAL;
> goto out_freeze_notify_failed;
> }
>
> /* Ensure that we are not runnable on dying cpu */
> old_allowed = current->cpus_allowed;
> tmp = CPU_MASK_ALL;
> cpu_clear(cpu, tmp);
> set_cpus_allowed(current, tmp);
>
> mutex_lock(&cpu_bitmask_lock);
We won't be needing this lock either, since it forms the core of
the unpopular lock_cpu_hotplug :-)
> p = __stop_machine_run(take_cpu_down, NULL, cpu);
> mutex_unlock(&cpu_bitmask_lock);
Looks good.
I'm wondering if we'll need to try_to_freeze in the fork and exit code
as well :?
Thanks and Regards
gautham.
--
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"
next prev parent reply other threads:[~2007-01-30 14:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070124011519.GG1613@linux.vnet.ibm.com>
[not found] ` <20070124090111.GC27221@in.ibm.com>
[not found] ` <20070124161559.GA1762@linux.vnet.ibm.com>
[not found] ` <20070124210645.GA19650@in.ibm.com>
2007-01-26 19:11 ` Fw: Re: [mm PATCH 4/6] RCU: (now) CPU hotplug Dipankar Sarma
2007-01-26 19:28 ` Andrew Morton
2007-01-26 19:46 ` Dipankar Sarma
2007-01-26 20:17 ` Andrew Morton
2007-01-26 20:44 ` Dipankar Sarma
2007-01-26 21:29 ` Andrew Morton
2007-01-28 22:47 ` Paul E. McKenney
2007-01-28 23:30 ` Andrew Morton
2007-01-29 2:40 ` Paul E. McKenney
2007-01-29 19:12 ` Ingo Molnar
2007-01-30 2:45 ` Paul E. McKenney
2007-01-30 7:33 ` Ingo Molnar
2007-01-30 16:02 ` Paul E. McKenney
2007-01-30 16:44 ` Rafael J. Wysocki
2007-01-30 18:27 ` Andrew Morton
2007-01-30 19:49 ` Paul E. McKenney
2007-01-31 23:10 ` Paul E. McKenney
2007-02-03 0:17 ` Pavel Machek
2007-02-04 4:39 ` Paul E. McKenney
2007-02-04 11:08 ` Rafael J. Wysocki
2007-02-04 12:53 ` Pavel Machek
2007-02-04 13:46 ` Rafael J. Wysocki
2007-02-04 13:50 ` Pavel Machek
2007-02-04 13:59 ` Rafael J. Wysocki
2007-02-03 0:01 ` Pavel Machek
2007-02-03 22:27 ` Rafael J. Wysocki
2007-02-04 0:31 ` Paul E. McKenney
2007-01-30 14:02 ` Gautham R Shenoy [this message]
2007-01-30 16:47 ` Paul E. McKenney
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=20070130140227.GB7113@in.ibm.com \
--to=ego@in.ibm.com \
--cc=akpm@osdl.org \
--cc=dipankar@in.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=vatsa@in.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox