On Fri, Nov 13, 2020 at 12:54:57PM +0100, Manuel Bouyer wrote: > On Thu, Nov 12, 2020 at 09:19:39PM +0100, Roger Pau Monné wrote: > > The following might be able to get you going, but I think I need to > > refine the logic a bit there, will have to give it some thought. > > I also tested with xen devel (Xen version 4.15-unstable, Latest ChangeSet: > Wed Nov 4 09:27:22 2020 +0100 git:9ff9705647-dirty). > Your patch is needed there too to avoid the panic. > > As with 4.13, I have problems with interrupts not being properly > delivered. The strange thing is that the counter is not 0, but 3 (wuth 4.13) > or 2 (with 4.15) which would mean that interrupts stop being delivered > at some point in the setup process. Maybe something to do with mask/unmask ? > > The problematc interrupt in identifed as "ioapic2 pin 2" by the NetBSD kernel, > so it's not MSI/MSI-X (not sure it matters though). > Maybe something related to mask/unmask ?
What device do you have on that pin? Is it the only device not working properly? I get from that that MSI/MSI-X is now working fine. You can get some interrupt info from the 'i' and the 'z' debug keys, albeit that won't reflect the state of the emulated IO-APIC used by dom0, which is likely what we care about. There's also the 'M' debug key, but that's only useful for MSI/MSI-X. I can try to prepare a patch to dump some info from the emulated IO-APIC, but I'm afraid I won't get to it until Monday. Roger.
