Same applies when doing the reverse mapping.The only reason to use the ipi_mapping thing is if we need non
In other words, the ipi_mask won't always necessarily be linear to facilitate
the 1:1 mapping that this approach assumes.
It is a solvable problem, but I think we're losing the elegance that promoted
going into this direction and I think sticking to using struct ipi_mapping
(with some enhancements to how it's exposed an integrated by/into generic
code) is a better approach.
consecutive masks, i.e. cpu 5 and 9.
I really don't want to have it mandatory as it does not make any sense
for systems where the IPI is a single per_cpu interrupt. For the
linear consecutive space it is just adding memory and cache footprint
for no benefit. Think about machines with 4k and more cpus ....