{"ref":"refs/heads/master","commits":[{"author":{"name":"Sepherosa Ziehau","email":"153549eac10244a41dca49732ef831d5104286aa@dragonflybsd.org"},"sha":"c83c147ec7809044a209b1ea4b3cc251ab6474df","message":"intr: Per-cpu MI interrupt information array\n\n- Interrupt information is only recorded in its target CPU's interrupt\n  information array.\n- Interrupt threads, emergency polling threads, interrupt livelock\n  processing and hardware interrupt threads scheduling only access\n  the interrupt information of the CPU they are running on; they have\n  already been locked to the interrupt's target CPU.\n- Location of SWI information is saved in a global array swi_info_ary,\n  since scheduling SWI does not necessarily happens on the CPU that\n  SWI thread is running, we need a quick and correct way find the SWI\n  information.\n- Factor out sched_ithd_intern, which accept interrupt information\n  (struct intr_info) instead of interrupt number.  Split the original\n  sched_ithd() into sched_ithd_soft(), which schedules SWI thread, and\n  sched_ithd_hard() which schedules hardware interrupt thread.\n- vmstat(8) interrupt reporting w/ -v is augmented to print the interrupts'\n  target CPU.\n\nThis paves way to the per-cpu MD interrupt description table","url":"https://api.github.com/repos/DragonFlyBSD/DragonFlyBSD/commits/c83c147ec7809044a209b1ea4b3cc251ab6474df"}],"head":"c83c147ec7809044a209b1ea4b3cc251ab6474df","push_id":54041358,"size":1}