On Mon, Nov 16, 2020 at 07:22:11PM +0100, Manuel Bouyer wrote: > On Sun, Nov 15, 2020 at 07:24:16PM +0100, Roger Pau Monné wrote: > > On Sun, Nov 15, 2020 at 06:49:38PM +0100, Manuel Bouyer wrote: > > > Hello, > > > I spent some more time debugging NetBSD as a PVH dom0 on Xen, > > > With Roger's patch to avoid a Xen panic, the NetBSD kernel stalls > > > configuring devices. At first I though it was an issue with hardware > > > interrupts, but it more likely is an issue with Xen timer events. > > > Specifically: virtual CPU 0 stops receiving timer events, while other > > > CPUs keep receiving them. I tried to force a timer rearm but this didn't > > > help. > > > The event is not masked nor pending on Xen or NetBSD, as confirmed by 'q'. > > > Others events (the Xen console, the debug event) are properly received > > > by CPU0. I don't know how to debug this more at this point. > > > > You could try to use dom0_vcpus_pin command line option and then dump > > the timers using the 'a' debug key, this way you can see if CPU0 has a > > timer pending (which would be the vCPU0 timer). > > thanks, this helped. This was a bug in the NetBSD kernel, which would show > up only when there are enough physical device interrupts (which explains why > I didn't notice it on PVH domUs)
Great! So all interrupts are working as expected now? Roger.
