| /openbsd/sys/arch/alpha/include/ |
| H A D | cpuconf.h | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | intr.h | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| /openbsd/sys/arch/alpha/pci/ |
| H A D | pci_1000.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_eb64plus.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_1000a.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_up1000.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_6600.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_axppci_33.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_2100_a50.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_550.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_kn20aa.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | pci_eb164.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | sio_pic.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| /openbsd/sys/arch/alpha/tc/ |
| H A D | tcasic.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| /openbsd/sys/arch/alpha/dev/ |
| H A D | shared_intr.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| /openbsd/sys/arch/alpha/alpha/ |
| H A D | interrupt.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|
| H A D | machdep.c | c62181b1 Thu Jun 15 20:08:29 GMT 2006 brad <brad@openbsd.org> Rework the interrupt code, shaving some cycles off in the process.
Rather than an "iointr" routine that decomposes a vector into an
IRQ, we maintain a vector table directly, hooking up each "iointr"
routine at the correct vector. This also allows us to hook device
interrupts up to specific vectors.
From thorpej NetBSD
Tested by myself and a number of end-users.
|