Searched hist:178092 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-10.1-release/sys/sys/ | ||
| H A D | cpuset.h | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| H A D | interrupt.h | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/arm/arm/ | ||
| H A D | intr.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/kern/ | ||
| H A D | kern_cpuset.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| H A D | kern_intr.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/powerpc/powerpc/ | ||
| H A D | intr_machdep.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/sparc64/sparc64/ | ||
| H A D | intr_machdep.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/x86/x86/ | ||
| H A D | intr_machdep.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
| /freebsd-10.1-release/sys/ia64/ia64/ | ||
| H A D | interrupt.c | diff 178092 Fri Apr 11 01:26:41 MDT 2008 jeff - Add the interrupt vector number to intr_event_create so MI code can lookup hard interrupt events by number. Ignore the irq# for soft intrs. - Add support to cpuset for binding hardware interrupts. This has the side effect of binding any ithread associated with the hard interrupt. As per restrictions imposed by MD code we can only bind interrupts to a single cpu presently. Interrupts can be 'unbound' by binding them to all cpus. Reviewed by: jhb Sponsored by: Nokia |
Completed in 392 milliseconds