> > IRQ_MOVE_CLEANUP_VECTOR is the only one of the system IRQ vectors that > > is *below* FIRST_SYSTEM_VECTOR. It is a slow path, so just push it > > into common_interrupt() just before the spurious interrupt handling. > > I'm missing here the "why": > > I can go forward into the set and see that you're splitting the handling based on > vector types and there's event classification and the lowest prio vector is not > going to be hardwired to 0x20, yadda yadda... > > but some of that should be in the text here so that it is clear why it is being done. Per Dave's ask, I am adding details about the benefits that FRED introduces, and then why we make these changes, which should make it clearer. Thanks! Xin