Searched hist:316145 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-11-stable/sys/dev/isp/ | ||
| H A D | isp_sbus.c | diff 316145 Wed Mar 29 15:50:57 MDT 2017 mav MFC r315307: Refactor interrupt handling. Instead of single isp_intr() function doing all possible magic, introduce four different functions to handle mailbox operation completions, async events, response and ATIO queues. The goal is to isolate different code paths to make code more readable, and to make easier support for multiple interrupt vectors. Even oldest hardware in many cases can identify what code path it should run on interrupt. Contemporary hardware can assign them to different interrupt vectors. |
| H A D | ispvar.h | diff 316145 Wed Mar 29 15:50:57 MDT 2017 mav MFC r315307: Refactor interrupt handling. Instead of single isp_intr() function doing all possible magic, introduce four different functions to handle mailbox operation completions, async events, response and ATIO queues. The goal is to isolate different code paths to make code more readable, and to make easier support for multiple interrupt vectors. Even oldest hardware in many cases can identify what code path it should run on interrupt. Contemporary hardware can assign them to different interrupt vectors. |
| H A D | isp_pci.c | diff 316145 Wed Mar 29 15:50:57 MDT 2017 mav MFC r315307: Refactor interrupt handling. Instead of single isp_intr() function doing all possible magic, introduce four different functions to handle mailbox operation completions, async events, response and ATIO queues. The goal is to isolate different code paths to make code more readable, and to make easier support for multiple interrupt vectors. Even oldest hardware in many cases can identify what code path it should run on interrupt. Contemporary hardware can assign them to different interrupt vectors. |
| H A D | isp_freebsd.c | diff 316145 Wed Mar 29 15:50:57 MDT 2017 mav MFC r315307: Refactor interrupt handling. Instead of single isp_intr() function doing all possible magic, introduce four different functions to handle mailbox operation completions, async events, response and ATIO queues. The goal is to isolate different code paths to make code more readable, and to make easier support for multiple interrupt vectors. Even oldest hardware in many cases can identify what code path it should run on interrupt. Contemporary hardware can assign them to different interrupt vectors. |
| H A D | isp.c | diff 316145 Wed Mar 29 15:50:57 MDT 2017 mav MFC r315307: Refactor interrupt handling. Instead of single isp_intr() function doing all possible magic, introduce four different functions to handle mailbox operation completions, async events, response and ATIO queues. The goal is to isolate different code paths to make code more readable, and to make easier support for multiple interrupt vectors. Even oldest hardware in many cases can identify what code path it should run on interrupt. Contemporary hardware can assign them to different interrupt vectors. |
Completed in 292 milliseconds