diff options
| author | Lorenzo Pieralisi <[email protected]> | 2025-08-14 09:41:38 +0000 |
|---|---|---|
| committer | Thomas Gleixner <[email protected]> | 2025-08-24 10:54:06 +0000 |
| commit | 35c23871be0072738ccc7ca00354c791711e5640 (patch) | |
| tree | 317c1accad7bd5b33698eb995a55e921cfbf6042 /drivers/cdx/controller/cdx_controller.c | |
| parent | irqchip/gic-v5: Fix kmemleak L2 IST table entries false positives (diff) | |
| download | kernel-35c23871be0072738ccc7ca00354c791711e5640.tar.gz kernel-35c23871be0072738ccc7ca00354c791711e5640.zip | |
irqchip/gic-v5: Remove undue WARN_ON()s in the IRS affinity parsing
In gicv5_irs_of_init_affinity() a WARN_ON() is triggered if:
1) a phandle in the "cpus" property does not correspond to a valid OF
node
2 a CPU logical id does not exist for a given OF cpu_node
#1 is a firmware bug and should be reported as such but does not warrant a
WARN_ON() backtrace.
#2 is not necessarily an error condition (eg a kernel can be booted with
nr_cpus=X limiting the number of cores artificially) and therefore there
is no reason to clutter the kernel log with WARN_ON() output when the
condition is hit.
Rework the IRS affinity parsing code to remove undue WARN_ON()s thus
making it less noisy.
Signed-off-by: Lorenzo Pieralisi <[email protected]>
Signed-off-by: Thomas Gleixner <[email protected]>
Link: https://lore.kernel.org/all/[email protected]
Diffstat (limited to 'drivers/cdx/controller/cdx_controller.c')
0 files changed, 0 insertions, 0 deletions