Mathias Nyman <mathias.nyman@xxxxxxxxxxxxxxx> writes:
> On 23.3.2020 16.10, Thomas Gleixner wrote:
>>
>> thanks for providing the data. I think I decoded the issue. Can you
>> please test the patch below?
>
> Unfortunately it didn't help.
I did not expect that to help, simply because the same issue is caught
by the loop in fixup_irqs(). What I wanted to make sure is that there is
not something in between which causes the latter to fail.
So I stared at the trace data earlier today and looked at the xhci irq
events. They are following a more or less periodic schedule and the
forced migration on CPU hotplug hits definitely in the time frame where
the next interrupt should be raised by the device.
1) First off all I do not have to understand why new systems released
in 2020 still use non-maskable MSI which is the root cause of all of
this trouble especially in Intel systems which are known to have
this disastrouos interrupt migration troubles.
Please tell your hardware people to stop this.
2) I have no idea why the two step mechanism fails exactly on this
system. I tried the same test case on a skylake client and I can
clearly see from the traces that the interrupt raised in the device
falls exactly into the two step update and causes the IRR to be set
which resolves the situation by IPI'ing the new target CPU.
I have not found a single instance of IPI recovery in your
traces. Instead of that your system stops working in exactly this
situation.
The two step mechanism tries to work around the fact that PCI does
not support a 64bit atomic config space update. So we carefully avoid
changing more than one 32bit value at a time, i.e. we change first
the vector and then the destination ID (part of address_lo). This
ensures that the message is consistent all the time.
But obviously on your system this does not work as expected. Why? I
really can't tell.
Please talk to your hardware folks.
And of course all of this is so well documented that all of us can
clearly figure out what's going on...
Thanks,
tglx
