Hummm.... Todd (or Quinn?)....
I think your third possibility is very good... however...:
a) what do you think about making (with a programmer option) an interrupt
service thread NON-INTERRUPTABLE or, anyway, allowing a priority-based
interrupt management ?
b) I don't know if, in the future, it will be implemented a kind of memory
management based on swapping. In this case, any interrupt service thread must
not be swapped!
Bye,
Corrado
On Sun, 24 Oct 1999, Todd L. Miller wrote:
>
> The third possibility is a hybrid of the two. Have a well-known
> class, say jos.system.machine, which has [add|remove]InterruptListener
> methods adding listeners to a well-known (constant static***) array of
> vectors therein. The kernel can then extract this information and schedule
> the interested threads appropriately (i.e. at the top of the queue,
> aborting the current thread). This solution is efficient, exposes the
> internals of the scheduler minimally to the Java, and imposes minimal
> restrictions on the Java code. Combined with a timer mechanism
> (jos.system.machine.setTimer()?) (and native support for it!), this should
> make the driver writers' jobs much simpler. It should also translate
> pretty closely into the JavaOS/B model whenever we might implement it.
--
======================================================
Eng. Corrado Santoro - PhD Student
Unversity of Catania - Engineering Faculty
Institute of Computer Science and Telecommunications
Viale A. Doria, 6 - 95125 CATANIA (ITALY)
Tel: +39 095 7382365 Fax: +39 095 7382397
EMail: [EMAIL PROTECTED]
Personal Home Page:
http://www.cdc.unict.it/~csanto
ARCA Mobile Agent Framework Home Page:
http://netra.cdc.unict.it/ARCA
======================================================
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
