> Well, what I had in mind was this: we'll need to
> have a general allocation mechanism for all plugins,
> so they can allocate memory, I/O ports, interrupts,
> etc. When a plugin (which could be the debugger)
> allocates an interrupt, when the interrupt occurs
> it is reflected into the user program to the plugin.
Note that these are somewhat different things:
- A hardware model will allocate a (hardware) IRQ, and will
*generate* from time to time this interrupt. This will then
be signaled to the kernel somehow, where guest control is
transfered to the corresponding handler.
- A debugger will *intercept* a *software* interrupt (int 3),
so that the monitor doesn't call the handler but returns to
the user mode app. I don't see how a hardware model should
need to do this. In fact, except for int3 / int1 I don't
see why a general facility to redirect software interrupts
would be needed ...
Bye,
Ulrich
--
Ulrich Weigand,
IMMD 1, Universitaet Erlangen-Nuernberg,
Martensstr. 3, D-91058 Erlangen, Phone: +49 9131 85-27688
