JPS61143858A - File share method for plural operating systems - Google Patents

Abstract

PURPOSE:To facilitate easy sharing of a file with computers which are actuated by a center OS (operating system) and a secondary OS by securing such a constitution where the task of the center OS can use the file control function of the secondary OS as it is. CONSTITUTION:A computer system consists of a center OS11, a task 12 of the center OS and a secondary OS13d connected to a bus respectively. A task 14f of the OS13 requests the use of a file for a specific task of the OS13 when it wants the use of a file which is under the control of the OS13. A task 14 of the secondary OS received the request issues a file use request to the secondary OS13. Thus the task 14 requests the use of the file to the OS13. Then the task of the OS11 uses directly the file under the control of the OS13.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Application of the Invention] The present invention relates to a computer system, and more particularly to the sharing of files by tasks operating under multiple operating systems (herein referred to as OS).

[Background of the invention]

In a computer system that runs on multiple OS, all OS
A control method has already been proposed in which one OS (hereinafter referred to as core OS) operates another OS (hereinafter referred to as secondary OS) under the control of a control program that manages the OS (Japanese Patent Laid-Open No. 58-181149). issue). According to this control method, as shown in FIG.
Task 12 and secondary 0813 are on the same level. Therefore, since the secondary 0iS13 is a task of the core 0811, it can use the file management function 11-5 of the core 0811, but the task 12 of the core OS cannot directly use the file management function 13-4 of the secondary OS. I can't. The task 12 of the core OS executes the file management function 11-5 of the core 0811 after the secondary 0813 transfers the file to the file of the core OS.
There is no other choice but to use this via .

[Purpose of the invention]

An object of the present invention is to enable tasks of a core OS to easily utilize file management functions of a secondary OS.

[Summary of the invention]

According to the present invention, the tasks of the core OS are performed by the tasks of the secondary OS.
When you want to use a file under the control of the secondary OS, you request a specific task on the secondary OS to use the file, and the task on the secondary OS that receives this request issues a file use request to the secondary OS, and then , allows core OS tasks to directly use files under the control of a secondary OS (without moving them to core OS files).

[Embodiments of the invention]

First, the core OS and secondary OS, which are the premise of this invention,
A computer system operating on the computer system will be explained with reference to FIGS. 3 and 4. This computer system, as shown in Figure 3,
It consists of a processor 1 connected to a bus 4, a main memory 2, and an input/output device 3.

The main memory 2 stores a core 0811, a task group 12 under the core OS, and a secondary OS task 15.
As described later, the core 0811 includes an interrupt vector table, a dispatcher, a trap mapping table, and an I1
The secondary OS task 15 includes a secondary OS and a group of secondary tasks under the secondary OS.

FIG. 4 schematically shows the interrelationships among the programs. The core 0811 is a real-time OS with small overhead as a normal OS, and under it, the core OS
A group 12 of tasks (user tasks that are real-time application programs) are controlled. Core 0811
The interrupt vector table 11-1 in
This is a table that shows entry addresses to the OS for interrupts such as exception traps and external interrupts, and is usually set at a lower address in the computer's memory address. To briefly describe an example of the interface between a task and the OS, a request from the user task group 12 to the core 0811 is sent via an 870 interrupt via the address shown in the interrupt vector table 11-1. When the processing routine of the core OS11 is entered and the processing is completed, control is passed to the original task or another task via the dispatcher 11-2. Core 081
1, a trap mapping table 11-3 that defines processing addresses for each trap type is prepared for each task so that each task can perform unique processing for each trap.

The secondary 0813 includes the core 081 including the task (secondary task) group 14 controlled under this OS.
1 task, i.e. secondary OS task 15
As such, it is controlled by the core 0811, and its position is basically the same as that of other user task groups 12. Note that, of course, within the secondary OS task 15, the secondary task group 14 operates under the control of the secondary 0813 by multi-programming.

There are three main entries to the secondary OS task 15. The first entry is an initial entry 13 - 1 which is the execution address when it is first dispatched by the scheduling of the core 0811 . When control is passed to initial entry 13-1, secondary entry 08
13 initializes the OS, and thereafter starts executing the secondary task group 14. The second en) IJ is the trap entry 13-2. Secondary task group 14
When a trap such as a 5vC1 bus error occurs during execution, a trap entry is entered in the core 0811 according to the address in the interrupt vector table 11-19, and then the trap mapping table 11-1 corresponding to the task in which the trap occurs is entered. According to the address No. 3, the trap entry 13-2 is entered and processing by the secondary OS 13 is performed. The third entry is I10 interrupt entry 13-3. Note that 11-4 is the I10 task group belonging to the core 0811, and 16 to 19 are message queues.

Next, the sharing of file management functions according to the present invention will be explained with reference to FIGS. 1 and 5. This embodiment uses two types of traps in the sharing control process: trap≠1, which causes the core OS to issue a macro instruction, and trap+2, which makes a call to the secondary OS.

First, the secondary OS declares (sets) a macro instruction (hereinafter simply referred to as macro) corresponding to trap*1 in the interrupt vector table of the core OS (see Figure 4, 4O-2).
). The macros corresponding to trap 1 include SER, VE macro, wTMsG macro, RE
There is an MSG macro and an ACKNLG macro.

Server tasks (core OS) tasks with secondary OS
Process 4o-3 is performed to make the task capable of receiving messages from the task. That is, a specific task of the secondary OS stores the 5ERVE macro code in the macro code register belonging to the core OS (Fig.
6) and then set trap≠ to the core OS.
Issue 1.

The core OS that receives this trap 1 refers to the macro code register, issues a 5ERvE macro, and enables the task to function as a server task.

After the above preparation, the task of the core OS is to perform processing 40.
-1, sends a message requesting use of the file management function of the secondary OS to the secondary OS task that has become a server task (hereinafter simply referred to as server task). That is, the task of the core OS puts the request message into the FIFO message queue, issues trap+2 to the core 08, and sends the request message to the core OS.
refers to the interrupt vector table and passes control to the secondary OS (if the jump destination of trap+2 is the secondary OS)
S). The secondary OS that has been given control runs the server task.

Server tasks are WTMSG Mac1:I and REMSG
Issue a macro and if there is a request to use the file management function in the message queue, process it (40-4)
. That is, the server task sets the WTMSG macro code and the REMSG macro code in the macro code register, and issues a trap 1 to the core OS. When the core OS receives this, it refers to the macro code register and issues the WTMSG macro and the R, EMSG macro.

The WTMSG macro allows the server task to receive ACKN, which will be described later.
The execution of core OS tasks is suspended until the LG macro is issued. The REM8G macro takes out the oldest waiting message from the message queue and writes it to a predetermined area.

The server task then sends a trap≠ to the core OS.
2 to request the file management function service of the secondary OS (40-5). That is, the server task issues trap+2 to the core OS. t
rap+2 is the same system call as trap 4P2 used by the core OS task to request use of the secondary OS's file management function in process 40-1. Upon receiving this, the core OS refers to the interrupt vector table and transfers control to the secondary OS. The secondary OS to which control has been transferred makes its file management functions available to the tasks of the core OS.

The server task then sends a response to the usage request to the core OS task (40-6). That is, the server task sets the ACKNLG macro code in the macro code register and issues a trap 1 to the core OS. Upon receiving this, the core OS refers to the macro code register and issues the ACKNLG macro. This ACK
The NLG macro transmits a response to the request to use the file management function to the task of the core OS, causing the task to resume execution, and thus file access via the file management function of the secondary OS is executed.

〔Effect of the invention〕

According to the present invention, since tasks of the core OS can use the file management function of the secondary OS as is (without moving files to the core OS), files can be shared between computers running the core OS and the secondary OS. becomes easier.

[Brief explanation of the drawing]

FIG. 1 is a schematic diagram schematically showing the control process according to the present invention;
Figure 2 is a schematic diagram showing the relationship between the core OS, secondary OS, and tasks, Figure 3 is a program diagram of a computer system running on the core OS and secondary OS, and Figure 4 is a schematic diagram showing the relationship between each program. , FIG. 5 is a flow diagram of one embodiment of the present invention. 11... Core OS, 12... Core OS task, 1
3...Secondary OS, 14...Task of secondary OS, 13-4...File management function of secondary OS.

Claims (1)

[Claims] 1. A core OS and a core OS under the control of this core OS.
In a computer system that operates on multiple OSs, consisting of a secondary OS that is placed on the same level as the task of S,
A process in which the task of the core OS sends a request to use the file management function of the secondary OS to a specific task of the secondary OS, and a process in which the specific task of the secondary OS that receives this request sends a request to use the file management function to the secondary OS. A file sharing method comprising: