On Tue, Jul 13 2021 at 14:46, Yongxin Liu wrote:
Affinity change can happen in both interrupt context and non-interrupt context. The paranoia check for interrupt target cpu is not always true in non-interrupt context.
Supressing the warning is just papering over a larger underlying problem which was discussed recently already. I'm working on a fix for that already.
Thanks,
tglx