Re: [PATCH] make voyager work again after the cpumask_t changes

[Andrew Morton]

William Lee Irwin III <wli@xxxxxxxxxxxxxx> wrote:
>
> > (Actually it is legitimate: you may want to run a NR_CPUS=48 kernel on a
> > 2-way voyager just for testing purposes).  I'll drop your patch in as-is,
> > and maybe Bill can take a look at cpumaskifying it sometime?
> 
> I'm not convinced it's worth it; AIUI there are architectural limits to
> Voyager that prevent it from ever supporting > 32x in hardware,

Sure.  But we want a kernel which was compiled with NR_CPUS>32 to still
boot and run correctly on voyager.

Yes, the code as-is will happen to work, but dtrt and all that.

-
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/