Sorry, I didn't see the earlier question. Specifically the ISORs for some reason run in the space right after the regular ioapic entries, but "map" to the ioredtbl entries. What they actually map to, now that I think about it again, is done in the global_irq field in the ISOR. We don't start from zero there, but rather from 1. We should have changed it. My bad.
On Mon, Jun 20, 2016 at 7:33 AM Barret Rhoden <[email protected]> wrote: > On 2016-06-17 at 08:57 Kyle Milka <[email protected]> wrote: > > We dynamically get the interrupt vector from ioapic_write to the > > relevant irq in virtio_console. The poke_guest function now posts > > the interrupt vector for a specific device. > > Although I'm not sure about a few things involving virtio IRQs, we can > sort them out as we learn more. > > Merged to master at 4fe578b52434..89c4e6ce669c (from, to] > > You can see the entire diff with 'git diff' or at > https://github.com/brho/akaros/compare/4fe578b52434...89c4e6ce669c > > Thanks, > > Barret > > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
