JPH07219785A - Device and method for controlling operating system - Google Patents

Abstract

PURPOSE:To reduce the program size and the corresponding storage area of plural OSs of hierarchical structure. CONSTITUTION:A memory 4 is provided with a control table area 41 for storing control table information which is common to the OS specifications A2 and B3 of the high and low orders of hierarchical structure, control table areas 43 and 44 for storing control table information respectively peculiar to the OS specifications A2 and B3, and a pointer area 42 holding the storage address of control table information to the control table areas 43 and 44. The OS specification A2 is provided with a common information reference means 21 referring to the control table area 41 and a table information reference means 22 referring to the control table area 43. The OS specification B3 is provided with a table information reference means 31 referring to control table information in the control table area 44.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an operating system (OS) management device, and more particularly to a plurality of OS management devices having a hierarchical structure for incorporating devices.

[0002]

2. Description of the Related Art Since an OS for embedding a device is applied to devices of various scales, various levels of functional specifications are required according to the scale of the devices to be embedded, and a plurality of different functions are required. It is often required to deal with. On the other hand, in this type of device, since the capacity of the memory is limited, the required amount of the memory area for storing the OS compatible program needs to be suppressed as small as possible.

Conventionally, a plurality of OSs corresponding to different functions are set as a plurality of different OSs independent of each other.
When a plurality of them, for example, two functions are required, prepare two OSs corresponding to each of the above two functions, or
Alternatively, it is necessary to prepare an OS having a specification including the above two functions.

As an example of this kind of OS, the real-time OS described in RX116 Real-Time Operating System User's Manual Third Edition (Reference 1) issued by NEC Corporation in June 1990 has a system timer. However, the OS specification A has a task scheduling function according to the priority, and the priority of the management target is 32 levels with the priority of 0 to 31, and the priority of the management target on the OS specification A that is lower than the OS specification A is 0. There are 256 levels of 255, and two O's in a hierarchical structure with the OS specification B in which a processing program can be defined when an exception occurs and when a task or more ends
S is implemented.

Referring to FIG. 6, which shows a block diagram of a conventional OS management device described in Document 1, this conventional OS management device includes task 1 to be managed, the above-mentioned OS specifications A5 and OS specifications B6, and OS specifications. A5 and a memory 7 storing management tables 71 and 72 of respective systems of the OS specification B6.

The OS specification A5 and the OS specification B6 respectively include management table reference means 51 and 52 for referring to the management table information.

Referring to FIGS. 7A and 7B showing the contents of the management tables 71 and 72, respectively, the management table 7
1 is a system time area 711 in OS specification A,
The current running task area 712 indicating the ID of the currently executing task of the OS specification A, the task priority search map 431 for 32 levels in the OS specification A, and the task ready queue 432 for these 32 levels are managed. Table 7
2 is a system time area 721 in OS specification B,
The current running task area 722 of the OS specification B, the task priority search map 441 for 256 levels at the time of execution of the OS specification B, the task ready queue 442 for these 256 levels, and the exception handling corresponding to exception processing and termination processing A termination handler registration area 443 is included.

Next, the operation of the conventional operating system management apparatus will be described with reference to FIGS. First, when operating under the OS specification A, the management table 71 is operated by the management table reference means 51. The system time 711 is incremented as follows each time a timer interrupt is input to the OS. When a timer interrupt is input to the OS from a timer unit (not shown), an interrupt handler corresponding to the timer interrupt, that is, a clock handler (not shown) is started. The clock handler counts up the value of the system time 711. The currently running task 712 displays the ID of the task under execution corresponding to this interrupt process.

Next, when operating under the OS specification B, the management table reference means 52 operates the management table 72. As in the case of OS specification A described above, the system time area 721 is incremented each time a timer interrupt is input to the OS. The currently running task area 722 displays the ID of the task being executed corresponding to the interrupt process.

As described above, the management tables necessary for the operation are individually mounted corresponding to the OSs corresponding to the two processing OS specifications A and B, and the processing modules for operating the individual management tables are provided. That is, the management table reference means is also implemented for each OS.

Therefore, information that should be common to a plurality of OSs, such as system time and currently running task, is treated as completely different objects. Therefore, information of the same type in the management table and processing modules for them are handled for each OS. The configuration was inefficient because it was set to.

[0012]

The above-mentioned conventional operating system management device requires a plurality of OSs to realize a plurality of functions, and an OS management table corresponding to each of these OSs and the OS managements thereof. Since the processing means for operating the table is separately provided, there is a drawback that the required amount of the memory area for storing the OS compatible program increases. In addition, there is a drawback that the labor and cost for owning and managing the plurality of OSs increase.

[0013]

An operating system management apparatus of the present invention comprises an operating system having a hierarchical structure composed of a first upper operating system and a second operating system lower than the first operating system. In an operating system management device including a storage unit that stores management table information in which management information is generated in the form of a table, the storage unit serves as first and second tasks corresponding to the first and second operating systems. A first table area for storing common first management table information, and second and third storage areas for respectively storing second and third management table information unique to each of the first and second tasks. A table area and the second and third table areas And an address storage unit that holds a storage address of the third management table information, and the first operating system refers to the first management table information in the first table area. Means and a second table information reference means for referring to the second management table information of the second table area, wherein the second operating system controls the third management of the third table area. The third table information reference means for referring to the table information is provided.

The operating system management method of the present invention is a method for managing an operating system having a hierarchical structure composed of a first upper operating system and a second operating system lower than the first operating system. A first table area for storing first management table information common to the first and second tasks corresponding to the first and second operating systems, and a second table and a second table specific to each of the first and second tasks. Second and third table areas for respectively storing third management table information, and address storage means for holding storage addresses of the second and third management table information in the second and third table areas Storage means having a first operating system, the first operating system And a second table information reference means for referring to the second management table information in the second table area. In the operating system management method of the operating system management device, the second operating system has a third table information reference unit for referring to the third management table information of the third table area, The step of setting the instruction address of the address storage means to either one of the second and third management tables corresponding to the operation of either one of the second operating system, and the first table information reference means. The first and second tables are referred to by referring to the address storage means and the first table area. Common table processing, the second table information reference means refers to the second table area, and executes unique processing of the first task; and the third table information. And a step of referring to the third table area to execute a process unique to the second task.

[0015]

Embodiments of the present invention will now be described with reference to the drawings. The operating system management apparatus of the present embodiment is the same as the conventional one, that is, OS specifications A and B of hierarchical structure 2
Assume a system consisting of two OSs.

Referring to FIG. 1 which is a block diagram showing an embodiment of the present invention, an operating system management apparatus according to the present embodiment shown in this figure has a task 1 similar to the conventional one, an OS specification A2 including an OS specification B3, and an OS specification A2. A management table 41 holding information common to each system of the OS specifications A2 and B3, a pointer area 42 in which pointers to the management tables 43 and 44 are stored, and an OS specification A2
And a memory 4 storing management tables 43 and 44 respectively holding system-specific information of OS specification B3.

The OS specification A2 is a common information reference means 21 for referring to the common management table information of the management table 41.
And a management table reference unit 22 for referring to management table information specific to the OS specification A2, and the OS specification B3
Is provided with a management table reference means 31 for referring to management table information specific to the OS specification B3.

Referring to FIG. 2, which shows the contents of the memory 4,
The management table 41 includes a system time area 411 common to the OS specifications A2 and B3, a current running task area 412 indicating the ID of the currently executing task of the OS specifications A2 and B3, and the pointer area 42 described above. The management table 43 includes a task priority search map 431 for 32 levels similar to the conventional management table 71 and a task ready queue 432, and the management table 44 includes 256 levels similar to the conventional management table 72. Task priority search map 441, task ready queue 442, and exception / termination handler registration area 443.

Next, the operation of this embodiment will be described with reference to FIGS. 1 and 2 and FIG. 3 which is a flowchart of the processing of this embodiment. First, when operating with the OS specification A2 (step S1), processing is performed using the common information reference means 21, and the pointer instruction in the pointer area 42 is set as the management table 43 (step S2). The system time area 411 is incremented as follows each time a timer interrupt is input to the OS (step S3). When a timer interrupt is input from the timer unit (not shown) to the OS, an interrupt handler corresponding to this timer interrupt, that is, a clock handler (not shown) is started. The clock handler counts up the value in the system time area 411. The currently running task area 412 displays the ID of the task being executed corresponding to the interrupt process. The processes up to this point are common to the OS specifications A2 and B3.

Next, the management table reference means 22 is used to perform the processing unique to the OS specification A2. As an example, the processing when the currently running task transits to the waiting state and causes task dispatch will be described. When this task dispatch is required, the OS specification A2 first refers to the currently running task area 412 and the pointer area 42 (step S4), and the current running task recorded in the currently running task area 412. Is deleted from the task ready queue 432 (step S5). Next, with reference to the task priority search map 431, it is searched which task of which priority is to be dispatched as the running state next (step S6). Finally, the head task of the task ready queue 432 corresponding to the obtained priority is changed to the running state (step S7).

Next, when operating the OS specification B3 on the OS specification A2 (step S8), first, the processing is performed using the common information reference means 21, and the instruction of the pointer in the pointer area 42 is managed in the management table. It is changed to 44 (step S9). Next, as in the case of the OS specification A2 described above, the system time area 411 is incremented each time a timer interrupt is input to the OS (step S1).
0). The currently running task area 412 displays the ID of the task being executed corresponding to the interrupt process.

First, as in the case of the OS specification A2, the processing when the currently running task transits to the waiting state and causes task dispatch will be described. When the situation in which this task dispatch becomes necessary, the OS specification B3 first refers to the currently running task area 412 and the pointer area 42 respectively (step S11), and thereby the current running task recorded in the currently running task area 412. Is deleted from the task ready queue 442 (step S12). Next, referring to the task priority search map 441, it is searched which task of which priority is to be dispatched next as the running state (step S13). Finally, the head task of the task ready queue 442 corresponding to the obtained priority is changed to the running state (step S14).

Next, the process of defining an exception handling handler, which is a function peculiar to the OS specification B3, will be explained. A CPU exception such as an event that causes a temporary interruption during the execution of a program or an unexpected data input occurs. When it occurs, the OS specification B3 first refers to the pointer area 42, and the management table 44 designated by the pointer area 42.
With reference to the exception / end handler registration area 443, the CPU exception handler processing arranged at the corresponding address is executed.

As described above, the OS on the OS specification A2
When the processing corresponding to the specification B3 is executed, the information in the management table corresponding to the common information is used as it is, and the instruction of the pointer in the pointer area is changed to the management table of the OS specification B3 unique information. The specification B3 unique information management table can be realized by having only unique information other than the above common information as the content of the unique information management table.

Next, referring to FIG. 4 which is a block diagram showing a second embodiment of the operating system management apparatus of the present invention, the difference between the first embodiment shown in this figure and the first embodiment is that the memory is different. 4 instead of 4, the management table 41 corresponding to the OS specification A2 and OS specification B3 common information similar to the first embodiment, and the pointer area 8 instead of the management table 43
Management table 43A corresponding to OS specification A unique information including 1
And a management table 44 including, instead of the management table 44, a pointer area 82 corresponding to the OS specification B3 unique information.
That is, the memory 8 including the B and the management table 83 is provided.

Referring to FIG. 5, which shows the contents of the memory 8,
The management table 43A has the same OS specification A as that of the first embodiment.
32 levels of task priority search map 43 in 2
1 and task ready queue 432 for these 32 levels
In addition to the above, the management table 44 further includes a pointer area 81 for storing a pointer corresponding to the OS specification B3 unique information, and the management table 44 has the same task priority search map 4 as in the first embodiment.
41 and the task ready queue 442, a pointer area 82 corresponding to the OS specification B3 unique information held in the management table 83 is included. The management table 83 is the first
An exception / termination handler registration area 443 corresponding to the CPU and system call similar to the embodiment of FIG.

In this embodiment, the size of the task priority search map and task ready queue similar to those of the first embodiment is larger in the OS specification B3 than in the OS specification A2 having a hierarchical structure.
A system consisting of two OSs of OS specification B3 is assumed.

Similar to the first embodiment, a process when the currently running task transits to the waiting state and causes task dispatch will be described. Since the operation in the case of executing the OS specification A2 is the same as that of the first embodiment described above, the description thereof will be omitted.

Next, when operating the OS specification B3 on the OS specification A2, the pointer area 42 indicates the pointer area 82 and the pointer area 82 indicates the management table 83.
The description is omitted because it is the same as the first embodiment except that

When a CPU exception occurs during execution of the OS specification B3, the OS specification B3 first refers to the pointer area 42, and the pointer area 8 designated by the pointer area 42.
Exception handler registration area 8 for OS specification B specific information 2
The address 31 is referred to, and the CPU exception handler located at that address is executed.

Even if a CPU exception occurs during execution of the OS specification A2, only 0 is stored as the unique information corresponding to the OS specification A2 in the pointer area 81 designated by the pointer area 42. The OS of OS specification A2 skips the CPU exception to proceed with the operation, and
It is possible to separate the processing corresponding to the management table 83 that does not require processing in the S specification A2.

In this embodiment, by separating the frequently used tasks in the OS specification B from the less frequently used tasks such as CPU exception processing, the memory capacity corresponding to the management table area can be further reduced. It is possible to further reduce the memory capacity for operation.

[0033]

As described above, the operating system management apparatus of the present invention includes a common table area for storing management table information common to upper and lower OSs in a hierarchical structure, and each of the upper and lower OSs. Upper and lower unique table areas for respectively storing unique management table information and address storage means for holding storage addresses of the upper and lower unique management table information, and the upper OS refers to common table information. Means and an upper table information reference means, and the lower OS includes lower table information reference means, thereby dividing the common management table information and individual management table information other than the common management table information. Since it can be stored in the memory, the required memory area corresponding to each OS can be reduced.

Further, there is an effect that the labor and cost for possessing and managing each of these OSs can be saved.

[Brief description of drawings]

FIG. 1 is a block diagram showing a first embodiment of an operating system management device of the present invention.

2 is a diagram showing the contents of the memory of FIG. 1. FIG.

FIG. 3 is a flowchart showing an example of processing of this embodiment.

FIG. 4 is a block diagram showing a second embodiment of the operating system management device of the present invention.

5 is a diagram showing the contents of the memory of FIG. 4. FIG.

FIG. 6 is a block diagram showing an example of a conventional operating system management device.

FIG. 7 is a diagram showing the contents of the memory of FIG.

[Explanation of Codes] 1 task 2,5 OS specification A 3,6 OS specification B 4,7,8 memory 21 common information reference means 22, 31, 51, 61 management table reference means 41, 43, 44, 83, 43A , 44A management table 42, 81, 82 pointer area 411, 711, 721 system time area 412, 712, 722 current running task area 431, 441 task priority search map 432, 442 task ready queue 443 exception / end handler registration area

Claims (3)

[Claims] 1. A management table in which information for managing an operating system having a hierarchical structure composed of a first upper operating system and a second lower operating system of the first operating system is generated in a table form. In an operating system management device provided with a storage means for storing information, the storage means stores first management table information common to the first and second tasks corresponding to the first and second operating systems. Table areas, second and third table areas storing second and third management table information unique to each of the first and second tasks, and the second and third table areas. To the address holding the storage addresses of the second and third management table information A scan storage unit, the first operating system references the first management table information of the first table area first
Table information referencing means and second table information referencing means for referencing the second management table information in the second table area, wherein the second operating system is in the third table area. Third referring to third management table information
An operating system management device, comprising: 2. The storage means further comprises a fourth management table area for storing fourth management table information unique to the third task corresponding to the second operating system, and the second and third management table areas. 2. The operating system management device according to claim 1, wherein the management table area is provided with an address storage unit that holds a storage address of the fourth management table information in the fourth management table area. 3. A first operating system and a second operating system for managing an operating system having a hierarchical structure composed of a first upper operating system and a lower second operating system of the first operating system. Corresponding first and second
A first table area for storing first management table information common to each task, and second and third storage areas for respectively storing second and third management table information unique to each of the first and second tasks. Storage means having three table areas and address storage means for storing the storage addresses of the second and third management table information in the second and third table areas, and the first operating system First table information reference means for referring to the first management table information in the first table area, and second table information reference means for referring to the second management table information in the second table area. Has and
A third operation system in which the second operating system refers to the third management table information in the third table area.
In the operating system management method of the operating system management apparatus having the table information reference means, the instruction address of the address storage means corresponding to the operation of one of the first and second operating systems Setting in any one of the management tables No. 3 and No. 3, and the first table information reference unit refers to the address storage unit and the first table area to perform common processing of the first and second tasks. And a step in which the second table information reference unit refers to the second table area to perform a process unique to the first task, and the third table information reference unit includes the third table information reference unit. 3 table area to execute the processing unique to the second task. Characteristic operating system management method.