> I'm not sure I understand what you mean here. In any case, at least
> on S/390, doing a SIGP to an invalid CPU will simply get you an
> 'not operational' indication (condition code 3), so in fact the
> only problem *is* the busy loop on num_cpus ...
On other architectures it can get nasty if you send an interprocessor
interrupt out onto the bus for an invalid cpu destination.
Since not having the online map will be a problem for you I'll add the
mask = ... & cpu_online_map to cover the concerns you have.
Thanks,
Zwane
-- function.linuxpower.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/