[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1334104638.23924.233.camel@gandalf.stny.rr.com>
Date: Tue, 10 Apr 2012 20:37:18 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: paulmck@...ux.vnet.ibm.com
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arjan van de Ven <arjan@...radead.org>,
"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Milton Miller <miltonm@....com>,
"mingo@...e.hu" <mingo@...e.hu>, Tejun Heo <tj@...nel.org>,
KOSAKI Motohiro <kosaki.motohiro@...il.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Linux PM mailing list <linux-pm@...r.kernel.org>
Subject: Re: CPU Hotplug rework
On Tue, 2012-04-10 at 17:28 -0700, Paul E. McKenney wrote:
> > Just to throw out the stupid silly approach.
> >
> > What about creating a "__register_cpu_notifier()" that just does:
> >
> > int __ref __register_cpu_notifier(struct notifier_block *nb)
> > {
> > return raw_notifier_chain_register(&cpu_chain, nb);
> > }
> >
> > Also making cpu_maps_update_begin/done() global (and probably rename
> > them).
I just noticed that the cpu_maps_update_begin/done() are already global.
> >
> > and then in the above code do:
> >
> > cpu_maps_update_begin();
> > __register_cpu_notifier(nb);
> > do_setup();
> > cpu_maps_update_done();
> >
> >
> > Just saying,
>
> That does have some attractive properties, now that you mention it. ;-)
Which property? Stupid or Silly ;-)
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists