--- - branch: MAIN date: Mon Dec 24 14:55:42 UTC 2018 files: - new: '1.139' old: '1.138' path: src/sys/arch/x86/x86/intr.c pathrev: src/sys/arch/x86/x86/intr.c@1.139 type: modified - new: '1.50' old: '1.49' path: src/sys/arch/xen/include/intr.h pathrev: src/sys/arch/xen/include/intr.h@1.50 type: modified - new: '1.10' old: '1.9' path: src/sys/arch/xen/x86/xen_intr.c pathrev: src/sys/arch/xen/x86/xen_intr.c@1.10 type: modified - new: '1.29' old: '1.28' path: src/sys/arch/xen/x86/xen_ipi.c pathrev: src/sys/arch/xen/x86/xen_ipi.c@1.29 type: modified - new: '1.75' old: '1.74' path: src/sys/arch/xen/xen/clock.c pathrev: src/sys/arch/xen/xen/clock.c@1.75 type: modified - new: '1.82' old: '1.81' path: src/sys/arch/xen/xen/if_xennet_xenbus.c pathrev: src/sys/arch/xen/xen/if_xennet_xenbus.c@1.82 type: modified - new: '1.18' old: '1.17' path: src/sys/arch/xen/xen/pciback.c pathrev: src/sys/arch/xen/xen/pciback.c@1.18 type: modified - new: '1.91' old: '1.90' path: src/sys/arch/xen/xen/xbd_xenbus.c pathrev: src/sys/arch/xen/xen/xbd_xenbus.c@1.91 type: modified - new: '1.70' old: '1.69' path: src/sys/arch/xen/xen/xbdback_xenbus.c pathrev: src/sys/arch/xen/xen/xbdback_xenbus.c@1.70 type: modified - new: '1.47' old: '1.46' path: src/sys/arch/xen/xen/xencons.c pathrev: src/sys/arch/xen/xen/xencons.c@1.47 type: modified - new: '1.52' old: '1.51' path: src/sys/arch/xen/xen/xenevt.c pathrev: src/sys/arch/xen/xen/xenevt.c@1.52 type: modified - new: '1.73' old: '1.72' path: src/sys/arch/xen/xen/xennetback_xenbus.c pathrev: src/sys/arch/xen/xen/xennetback_xenbus.c@1.73 type: modified - new: '1.21' old: '1.20' path: src/sys/arch/xen/xen/xpci_xenbus.c pathrev: src/sys/arch/xen/xen/xpci_xenbus.c@1.21 type: modified - new: '1.21' old: '1.20' path: src/sys/arch/xen/xenbus/xenbus_comms.c pathrev: src/sys/arch/xen/xenbus/xenbus_comms.c@1.21 type: modified id: 20181224T145542Z.175553e634688a06f4d7e37b8b74a6faa5df6961 log: | Bifurcate the interrupt establish functions between XEN and non-XEN Thus intr_establish_xname() becomes xen_intr_establish_xname() etc. One consequence of this is that dom0 devices expect the native function calls to be available and we thus provide weak aliasing for dom0 builds to succeed. XEN and non-XEN devices are distinguished by the PIC they are established on. XEN interrupts are exclusively established on xen_pic, while dom0 interrupts are established on natively available PICs. This allows us an orthogonal path to xen device management (eg: xenstore events) in XENPVHVM, without having to worry about unifying the vector entry paths, etc., which is quite challenging. module: src subject: 'CVS commit: src/sys/arch' unixtime: '1545663342' user: cherry