Now
MAIN commitmail json YAML
src/sys/arch/x86/x86/intr.c@1.139
/
diff
/
nxr@1.139
src/sys/arch/xen/include/intr.h@1.50 / diff / nxr@1.50
src/sys/arch/xen/x86/xen_intr.c@1.10 / diff / nxr@1.10
src/sys/arch/xen/x86/xen_ipi.c@1.29 / diff / nxr@1.29
src/sys/arch/xen/xen/clock.c@1.75 / diff / nxr@1.75
src/sys/arch/xen/xen/if_xennet_xenbus.c@1.82 / diff / nxr@1.82
src/sys/arch/xen/xen/pciback.c@1.18 / diff / nxr@1.18
src/sys/arch/xen/xen/xbd_xenbus.c@1.91 / diff / nxr@1.91
src/sys/arch/xen/xen/xbdback_xenbus.c@1.70 / diff / nxr@1.70
src/sys/arch/xen/xen/xencons.c@1.47 / diff / nxr@1.47
src/sys/arch/xen/xen/xenevt.c@1.52 / diff / nxr@1.52
src/sys/arch/xen/xen/xennetback_xenbus.c@1.73 / diff / nxr@1.73
src/sys/arch/xen/xen/xpci_xenbus.c@1.21 / diff / nxr@1.21
src/sys/arch/xen/xenbus/xenbus_comms.c@1.21 / diff / nxr@1.21
src/sys/arch/xen/include/intr.h@1.50 / diff / nxr@1.50
src/sys/arch/xen/x86/xen_intr.c@1.10 / diff / nxr@1.10
src/sys/arch/xen/x86/xen_ipi.c@1.29 / diff / nxr@1.29
src/sys/arch/xen/xen/clock.c@1.75 / diff / nxr@1.75
src/sys/arch/xen/xen/if_xennet_xenbus.c@1.82 / diff / nxr@1.82
src/sys/arch/xen/xen/pciback.c@1.18 / diff / nxr@1.18
src/sys/arch/xen/xen/xbd_xenbus.c@1.91 / diff / nxr@1.91
src/sys/arch/xen/xen/xbdback_xenbus.c@1.70 / diff / nxr@1.70
src/sys/arch/xen/xen/xencons.c@1.47 / diff / nxr@1.47
src/sys/arch/xen/xen/xenevt.c@1.52 / diff / nxr@1.52
src/sys/arch/xen/xen/xennetback_xenbus.c@1.73 / diff / nxr@1.73
src/sys/arch/xen/xen/xpci_xenbus.c@1.21 / diff / nxr@1.21
src/sys/arch/xen/xenbus/xenbus_comms.c@1.21 / diff / nxr@1.21
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.
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.