Messages in this thread | | | Date | Mon, 27 Oct 2008 13:59:04 +0100 | From | Ingo Molnar <> | Subject | Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask of call_function_data |
| |
* Ingo Molnar <mingo@elte.hu> wrote:
> > * Rusty Russell <rusty@rustcorp.com.au> wrote: > > > On Friday 24 October 2008 15:47:20 Hiroshi Shimamoto wrote: > > > From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> > > > > Ingo, because of these concerns I recommend you revert > > d4de5ac3b5e70928c86e3e5ac311f16cbf2e9ab3 (cpumask: > > smp_call_function_many()) for now, and apply this less contentious > > version. > > ok - applied it to tip/cpus4096-v2, thanks Rusty! > > If there's any chance for this in v2.6.28 then only if we disable > the dynamic API branch altogether [CONFIG_MAXCPUS] and keep that for > v2.6.29. This means we'd bring in the API changes which should have > trivial impact only - and none of the riskier changes.
in any case, i've started testing tip/cpus4096-v2 again on x86 - the problem with d4de5a above was the only outstanding known issue, right?
Ingo
| |