xen interrupt system

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

Hi!

We all know, NetBSD/Xen's interrupt system needs to be reworked
to meet the demands for future features such as SMP, PV drivers in HVM.

In Xen development tree the interrupt system has been reworked which breaks
NetBSD/Xen Dom0 boot. No, the hypercalls did not change but
everything underneath. The new interrupt system in Xen enlights
the drawbacks of NetBSD/Xen's interrupt system in interrupt lossages,
timeouts and even in sudden freezes before Dom0 has the chance
to start the init process.

The situation is serious: Unless we rework the interrupt system,
Xen 3.3 and Xen 3.4 are the lastest Xen versions NetBSD will work with.


Below is a snippet of the serial console output:


pchb4: Advanced Micro Devices AMD64 Family10h Link Configuration (rev. 0x00)
pchb5 at pci0 dev 25 function 0
pchb5: Advanced Micro Devices AMD64 Family10h HyperTransport Configuration 
(rev. 0x00)
pchb6 at pci0 dev 25 function 1
pchb6: Advanced Micro Devices AMD64 Family10h Address Map Configuration (rev. 
0x00)
pchb7 at pci0 dev 25 function 2
pchb7: Advanced Micro Devices AMD64 Family10h DRAM Configuration (rev. 0x00)
amdtemp1 at pci0 dev 25 function 3: AMD CPU Temperature Sensors (Family10h / 
Family11h)
pchb8 at pci0 dev 25 function 4
pchb8: Advanced Micro Devices AMD64 Family10h Link Configuration (rev. 0x00)
isa0 at pcib0
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
ioapic0: int3 0x930<vector=0x30,delmode=0x1,logical,dest=0x0> 
0x1000000<target=0x1>
Link Device LNKU:
Index  IRQ  Rtd  Ref  IRQs
    0   10   Y     4  10 11 polarity 1 trigger 0

Link Device LNKS:
Index  IRQ  Rtd  Ref  IRQs
    0    7   Y     4  5 7 11 polarity 1 trigger 0

scsibus0: waiting 2 seconds for devices to settle...
uhub0 at usb0: ServerWorks OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1 at usb1: ServerWorks OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2 at usb2: ServerWorks EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
svwsata0 port 0: device present, speed: 1.5Gb/s
wd0 at atabus0 drive 0svwsata0 port 1: PHY offline
svwsata0 port 2: PHY offline
svwsata0 port 3: PHY offline
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 512 tc_skip: 0
: <ST3160815AS>
wd0: 149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 512 tc_skip: 0
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 512 tc_skip: 0
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
probe(mpt0:0:0:0): command timeout
mpt0: recovered from command timeout
svwsata0:0:0: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
atapibus0 at atabus4: 2 targets
cd0 at atapibus0 drive 1: <DV-28E-R, , 1.8A> cdrom removable
probe(mpt0:0:2:0): command timeout
mpt0: recovered from command timeout
probe(mpt0:0:3:0): command timeout
mpt0: recovered from command timeout
probe(mpt0:0:4:0): command timeout
mpt0: recovered from command timeout
probe(mpt0:0:5:0): command timeout
mpt0: recovered from command timeout
probe(mpt0:0:6:0): command timeout
mpt0: recovered from command timeout
probe(mpt0:0:7:0): command timeout
mpt0: recovered from command timeout