Re: [PATCH -tip/cpus4096-v2] cpumask: fix cpumask ofcall_function_data

From: Ingo Molnar
Date: Mon Oct 27 2008 - 08:59:26 EST



* Ingo Molnar <mingo@xxxxxxx> wrote:

>
> * Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote:
>
> > On Friday 24 October 2008 15:47:20 Hiroshi Shimamoto wrote:
> > > From: Hiroshi Shimamoto <h-shimamoto@xxxxxxxxxxxxx>
> >
> > 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/