Messages in this thread | | | Date | Tue, 18 Oct 2022 07:59:22 -0700 | From | Yury Norov <> | Subject | Re: [PATCH v2 5/5] lib/cpumask: add FORCE_NR_CPUS config option |
| |
On Tue, Oct 18, 2022 at 05:44:09PM +0300, Andy Shevchenko wrote: > On Tue, Oct 18, 2022 at 07:35:09AM -0700, Yury Norov wrote: > > On Tue, Oct 18, 2022 at 03:50:31PM +0200, Geert Uytterhoeven wrote: > > ... > > > For those who choose FORCE_NR_CPUS, it's required to set NR_CPUS > > to a value that matches to what's parsed from DT. > > > > Can you please look at the draft below that disables FORCE_NR_CPUS > > in allmodconfig? If it's OK with you, I'll send a patch. If you think > > that there are architectures where it's not possible to set correct > > NR_CPUS at compile time for some reason, I'll add ARCH_UNFORCE_NR_CPUS > > option. > > Instead you may simply add > > depends on CONFIG_$ARCH/$MACHINE=n > > and so on to the FORCE_NR_CPUS, no?
Yes, if there's just one machine like that. If there's many of them, the 'depends' list would be too long.
I hope there's no such a weird machines, and we don't need that at all. Let's see what Geert will say.
| |