Adaptive Domain Environment For Operating Systems - Architecture

Architecture

Adeos implements a queue of signals. Each time that a peripheral sends a signal, the different operating systems that are running in the machine are awakened, in turn, and must decide if they will accept (handle), ignore, discard, or terminate the signal. Signals not handled (or discarded) by an OS are passed to the next OS in the chain. Signals that are terminated are not propagated to latter stages.

As Adeos has to ensure equal and trusted access to the hardware it takes control of some hardware commands issued by the different OSes, but it also must not intrude too much on the different OSes’ normal behavior. Each OS is encompassed in a domain over which it has total control. This domain may include a private address space and software abstractions such as process, virtual memory, file-systems, etc. Adeos does not attempt to impose any policy of usage of the hardware except as needed for its own survival. The task of determining policy is left to the system architect.

Read more about this topic:  Adaptive Domain Environment For Operating Systems

Famous quotes containing the word architecture:

    “All architecture is great architecture after sunset; perhaps architecture is really a nocturnal art, like the art of fireworks.”
    —Gilbert Keith Chesterton (1874–1936)

    “They can do without architecture who have no olives nor wines in the cellar.”
    —Henry David Thoreau (1817–1862)

    “In short, the building becomes a theatrical demonstration of its functional ideal. In this romanticism, High-Tech architecture is, of course, no different in spirit—if totally different in form—from all the romantic architecture of the past.”
    —Dan Cruickshank (b. 1949)