Ulrich Weigand wrote:
> Maybe a more general approach would be better; after all, using the
> APIC commands, you can invoke *any* interrupt vector on any other
> processor (or your own) ... It's just that Linux uses this feature
> only to invoke int 0x30.
>
> For cleaner code, I'd suggest to drop the special handling of the
> PIC IRQs, and use either
>
> - a bitmap set by the host OS dependent part stating just which
> interrupt vectors are to be forwarded
>
> or
>
> - simply forward *all* vectors >= 0x20
If we go with Ramon's plan of passing this info to the monitor,
we could start out by just passing the monitor 0x20..0xff for
now, for reflection back to the host, as in your 2nd option.
We should keep the door open for the possibility of allowing
guest user code to invoke guest OS code via a soft interrupt
if it has been prescanned. We certainly have to trap out
for vectors which overlap other interrupts. This needs
more thought, but let's keep it in mind.
-Kevin
