JPH01273151A - Memory window control system for plural oss - Google Patents

Abstract

PURPOSE:To control plural pieces of OSs by the same hardware even in case of the OS of different architecture by trapping a BIOS for controlling a memory window from each guest OS and an instruction for controlling directly the memory window. CONSTITUTION:When a command for executing directly an access to a memory window hardware 3 is issued from application programs 2a-2c, its command executes an access to virtual memory windows 8a-8c. A flow of this access traps the command by an instruction trap mechanism 5, when the command to the memory window hardware 3 is issued from the application programs 2a-2c on guest OSs 1a-1c. In such a way, by referring to a virtual memory window management table 7 in a memory window control part 6, even the OS of different architecture can be controlled by the same hardware.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a memory window control method, and particularly to a memory window control method for multiple OSs [prior art], and FIG. 2 shows a conventional memory window control method for multiple OSes. FIG. In the figure, a guest OS 13 having application programs 2a to 2C, 1a to 1C, is memory window hardware, and 4 is a BiO2 that controls this memory window hardware 3.
It is.

Next, the operation of the multiple OS memory window control method with the above configuration will be described. For example, guest OS la
When controlling the memory window hardware 3 from the above application program 2a, the memory window hardware 3 can be controlled by issuing commands to the BiOS 4. In addition, if a command is issued from the application program 2a to the memory window hardware 3 without going through the BiOS 4, the control of memory quick/do will become a problem, so there is only one physical memory window control of this type. The BiOS 4 controls a plurality of guest OSs having the same architecture, whereas the memory window hardware 3 does not have the same architecture.

[Problem to be solved by the invention]

The above-mentioned conventional memory window control method for multiple OSes The memory window is controlled by the line BIOS, and since a plurality of guest OSes of the same architecture are controlled, it is not possible to control the OSs that do not pass through the BIOS. Moreover, it has the disadvantage that it cannot be controlled unless the guest OS has the same architecture.

[Means to solve the problem]

The memory window control method for multiple OSs according to the invention includes, for each guest OS, a virtual memory window, a virtual memory window management table for managing these virtual memory windows, and means for trapping commands from the guest OS to the memory window. and means for controlling physically existing memory windows and virtual memory windows.

[Effect]

This invention can control OSs of different architectures with the same hardware.

〔Example〕

FIG. 1 is a block diagram showing an embodiment of a memory window control method for multiple OSs according to the present invention.

In the figure, 5 is an instruction trap mechanism for the memory window hardware 3, 6 is a memory window control unit equipped with a virtual memory window management table T shown in the table below, and 8a to 8c are virtual memory windows.

Note that the table is a virtual memory window management table that indicates memory addresses of virtual memory windows in the information processing system.

Next, the operation of the memory window control method for multiple OSs with the above configuration will be explained. First, the physically existing memory window hardware 3 is managed by the memory window control unit 6, so that the application programs 2a, 2b, and 2c of the guests 081a, lb, and 1c can access the memory window hardware 3. It disappears. As a result, when the application programs 2a, 2b, and 2C issue a command to directly access the memory window hardware 3, the command is issued to the virtual memory window 6a.

6b and 6C will be accessed. In this access flow, when a command is issued to the memory window hardware 3 from the application programs 2a, 2b, and 2C on the guest OSs 1a, 1b, and 1c, the command is trapped by the instruction trap mechanism 5. The trapped command is sent to the memory window control unit 6.
, the virtual memory windows ga, 8b, and 8C are accessed while referring to the virtual memory window management table T. When accessing the virtual memory windows 8a, 3b, and 8C from the memory window control unit 6, the memory window control unit 6
By referring to the virtual memory window management table T, even OSs with different architectures can control the same hardware.

〔Effect of the invention〕

As explained in detail above, according to the memory window control method for multiple OSs according to the present invention, by trapping the BIOi9 that controls the memory window from each guest OS and the instruction that directly controls the memory window, different Even in the case of an architectural OS, a plurality of OSs can be controlled by the same hardware.

[Brief explanation of the drawing]

FIG. 1 is a block diagram showing an embodiment of the memory window control method for multiple OSs according to the present invention, and FIG.
2 is a configuration diagram showing a memory window control method of S. FIG. 1a to 1C...Guest OS, 28 to 2C...Application program, 3...Memory window hardware, 50...Instruction trap mechanism, 6...
...Memory window control unit, T...Virtual memory window management table, 8a to 8C...Virtual memory window.

Claims (1)

[Claims] In one information processing system in which multiple OSes operate simultaneously, each guest OS has a virtual memory window, a virtual memory window management table for managing these virtual memory windows, and means for trapping commands from the guest OS to the memory window. 1. A memory window control method for multiple OSs, comprising means for controlling physically existing memory windows and virtual memory windows.