JPH03189828A - Coordination operation system - Google Patents

Abstract

PURPOSE:To uniformly control the operation rate of each operating system (OS) by actuating a context switcher by a system timer processing actuated at every prescribed time, and switching the OS, while managing and changing operating state information and scheduling information of the OS by the context switcher. CONSTITUTION:A context box 12 defines by its number so as to correspond to each OS (operating system), and has a queue pointer 13 and a context area 14 for storing context information. As for this queue structure, the context box 12 indicated by a context ready queue pointer shows the context box of the OS which is operating at present, and the context boxes 12 are connected, respectively one after another as per the sequence of waiting for the operation of the OS. In such a state, a context switcher actuated by a system timer processing used in common by each OS switches the OS, therefore, each OS can be switched at every prescribed time. In such a manner, the operation rate of each OS can be equalized.

Description

DETAILED DESCRIPTION OF THE INVENTION Field of the Invention The present invention relates to a computer cooperative operation system for running a plurality of operating systems in parallel.

Conventional technology Conventionally, this type of operating system (hereinafter referred to as O8
It is abbreviated as ), one of the multiple O8s becomes the main O8 and manages the other O8s by positioning tasks (or processes), and the operation of each O3 is controlled by the scheduler of the main O3. ing.

Problems to be Solved by the Invention However, in the above-mentioned conventional O8 cooperative operation system,
Occasionally, the operating rate of each O8 depends on the scheduler of the main O8, and it is difficult to make the operating rates of each O3 uniform. Therefore, in order to make the operating rates of each O3 uniform, there is a problem in that an O3 that has a scheduler that uniformly schedules each O8 must be used as the main O8. Furthermore, there is also the problem that the idle time generated in the O8 managed by the main O3 becomes wasted time, reducing the overall operating rate.

The present invention solves such conventional problems, and provides an excellent cooperative operation system that can equalize the operating rate of each O8 and effectively utilize the idle time of each O8 in cooperative operation of O8. With the goal.

Means for Solving the Problems In order to achieve the above objects, the present invention provides each O3
Context box waiting queue and context box ready queue and context box ready queue for indicating the O8's wait and ready state and scheduling information for determining the order of execution within the ready state. The first one for switching to the next O8 in the execution order of the currently operating O3 among the O8s in the ready state that are managed in the queue.
and a second context switcher that switches the currently operating O8 from the text box ready queue to the context box wait queue to put it in the waiting state, and switches control to the next O8 in the execution order in the ready state.
a context switcher, two types of internal interrupt handlers that are activated to execute the first and second context switchers from the system timer and tasks under each O3, respectively, and a second interrupt handler that runs when each O8 is idle. An idle task under the control of each O3 that starts an internal interrupt handler that executes the first context switcher, and a system timer process that is shared by each O8 to start the first context switcher at regular intervals. It is something that

Effects The present invention has the following effects due to the above structure. That is, the first context switcher is activated by a system timer process that is activated at regular intervals, and this first context switcher manages and changes the operating status information and scheduling information of the O3 indicated by the context box ready queue. However, by realizing O8 switching, the operating rate of each O8 can be controlled uniformly, and when an idle time occurs in the active O3, an idle task is activated, and this task generates an internal interrupt that starts the first context switcher. By activating the handler, O8 scheduling and switching occur, which has the effect that idle time can be used effectively.

Embodiment FIGS. 1 to 7 show the structure of an embodiment of the present invention. FIG. 1 shows the structure of a context box and a context box ready queue that store context information of each O8. 11 is a context ready queue pointer, and 12 indicates a context box.

The number of context boxes 12 is defined to correspond to each O8, and has a cue pointer 13 and a context area 14 for storing context information. This queue structure indicates the context box 12 pointed to by the context ready queue pointer 11 or the context box of the O8 that is currently in operation, and the context boxes 12 and 12 of the O8 that are currently in operation are sequentially ordered in the order in which the O8s are waiting for operation.
are connected.

FIG. 2 shows the structure of the context box wait queue. 15 is a context wait queue pointer. This queue structure is necessary to manage the O3s that are waiting for operation, and the queuing order does not need to have any particular meaning.

FIG. 3 shows the processing procedure of the first context switcher, in which the context ready queue 11 and context box 12 of FIG. 1 are operated to realize switching of O8. In FIG. 3, step 31 is a process of storing the context of the corresponding O3 in the context box 12 of the currently operating O3 pointed to by the context ready queue pointer 11 of FIG. Step 32 is a scheduling process of the operating O8, in which the leading context box 12 pointed to by the context ready queue pointer 11 is dequeued and connected to the end of the queue, so that the leading context box 12 waiting to be activated becomes the context ready queue pointer 11. will be pointed out. Therefore, by repeating this step 32, each O8 will be scheduled. Next step 33
is a process of executing the O8-specific scheduler corresponding to the context box 12 pointed to by the context ready queue pointer 11. Step 34 is the operation O3
This is the process of recovering the context.

FIG. 4 shows the processing procedure of the second context switcher. Step 41 is the same process of saving the context of the currently operating O8 as step 31 in FIG. Step 4
2 dequeues the context box 12 of the currently operating O8 pointed to by the context ready queue pointer 11,
This is a process of queuing to the context box waiting queue 15 in FIG. As a result, the currently operating O8 enters the waiting state, and the context ready queue pointer 11
The context box pointed to by will be that of the new operating O8. Step 43 is the process of starting up the scheduler of the new operating O8, which is the same as step 33 in FIG. Step 44 is the same process as step 34 in FIG.

FIG. 5 shows system timer processing. Step 51 shows system timer processing that is uniquely defined for each O3.

Step 52 is the activation process of the first context switcher in FIG.

FIG. 6 shows the processing of each idle task. When the idle task runs, an internal interrupt handler is immediately activated in step 61, and the same handler is activated indefinitely.

FIG. 7 shows an internal interrupt handler activated from the idle task of FIG. This interrupt handler connects the second context switcher as shown in step 71.
Start.

Next, the operation of the above embodiment will be explained. In the above embodiment, when the first context switcher is activated in step 52 in the system timer process of FIG. 5, the first context switcher as shown in FIG.
processing is performed. First, in step 31, the current operating O8 corresponding to the context box at the head of the queue in FIG.
and then in step 32 O8
The context box of the first O8 waiting for operation is placed at the beginning of the context box ready queue, and the O8 becomes the new operating O8.
shall be. Next, in step 33, a scheduler specific to the new operating O8 is activated. Finally, in step 34, control is transferred to the O8 by recovering the context information from the context area of the context box of the O8.
Move to 8.

In this way, according to the above embodiment, the system timer that is activated at a certain time is activated by the first context switcher.
By starting the O8, switching of O8 occurs, and each O8
It is possible to equalize the operating rate of Furthermore, operating O8
When an idle time occurs, that is, when an idle task under the active O3 runs, the task activates an internal interrupt handler as shown in FIG. This internal interrupt handler activates the second context switcher, as shown in FIG. 7, and causes the second context switcher to perform processing as shown in FIG. 4. When idle time occurs in the operating O8 due to this series of processing, the O8 is scheduled and switched.
The idle time of O3 can be effectively utilized.

Effects of the Invention As is clear from the above embodiment, in the present invention, the first context switcher activated by the system timer processing shared by each O3 switches the O3, and therefore switches each O8 at regular intervals. This has the effect that the operating rate of each O3 can be made uniform. Further, by activating the second context switcher after the idle task places the currently active O8 in a waiting state, it is possible to effectively utilize the idle time of the O8 to cause switching of the O8.

[Brief explanation of drawings]

FIG. 1 is a schematic block diagram showing the context box and context box ready queue structure of O8 in one embodiment of the present invention, FIG. 2 is a schematic block diagram showing the context box waiting queue structure, and FIG. 70-chart showing the processing procedure of the switcher, FIG. 4 is a flowchart showing the processing procedure of the second context switcher, FIG. 5 is a flowchart showing system timer processing shared by each O8, and FIG. 6 is a flowchart showing the processing procedure of the second context switcher. FIG. 7 is a flowchart showing the processing of a task. FIG. 7 is a flowchart showing the processing of an internal interrupt handler. 11...Context ready queue pointer 12.
...Context box, 13...Cue pointer 14...Context area, 15...Context waiting queue pointer

Claims (1)

[Claims] System timer processing for multiple operating systems can be shared, and operating system operating states can be scheduled and managed using the wait and ready operating states of each operating system in the context box of each operating system, and the execution order of operating systems in the ready state. It has a connected queue structure, and defines an idle task that is started when there is no runnable task under each operating system under the management of each operating system, that is, when the operating system becomes idle, a first context switcher for switching an operating state in an operating system in a ready state; and placing the currently operating operating system in a waiting state;
and a second context switcher that switches to the next operating system in the execution order in the ready state, defines two types of interrupt handlers that execute the first and second context switchers, respectively, and executes the first and second context switchers, respectively. By activating an interrupt handler that executes the first context switcher, the utilization rate of each operating system is equalized, and by activating an interrupt handler that executes the second context switcher from an idle task of each operating system, the operating system A cooperative operation system that switches systems.