diff options
| author | Marc Zyngier <maz@kernel.org> | 2022-04-05 19:50:39 +0100 |
|---|---|---|
| committer | Thomas Gleixner <tglx@linutronix.de> | 2022-04-10 21:06:30 +0200 |
| commit | 33de0aa4bae982ed6f7c777f86b5af3e627ac937 (patch) | |
| tree | b4443df13aec797af540398751b16d269a12c099 /lib/test_ref_tracker.c | |
| parent | d802057c7c553ad426520a053da9f9fe08e2c35a (diff) | |
| download | linux-stable-33de0aa4bae982ed6f7c777f86b5af3e627ac937.tar.gz linux-stable-33de0aa4bae982ed6f7c777f86b5af3e627ac937.tar.bz2 linux-stable-33de0aa4bae982ed6f7c777f86b5af3e627ac937.zip | |
genirq: Always limit the affinity to online CPUs
When booting with maxcpus=<small number> (or even loading a driver
while most CPUs are offline), it is pretty easy to observe managed
affinities containing a mix of online and offline CPUs being passed
to the irqchip driver.
This means that the irqchip cannot trust the affinity passed down
from the core code, which is a bit annoying and requires (at least
in theory) all drivers to implement some sort of affinity narrowing.
In order to address this, always limit the cpumask to the set of
online CPUs.
Signed-off-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20220405185040.206297-3-maz@kernel.org
Diffstat (limited to 'lib/test_ref_tracker.c')
0 files changed, 0 insertions, 0 deletions