JPH0863420A - Method for incorporating input/output control program - Google Patents

Abstract

PURPOSE: To save the trouble to manually define a mount adapter in advance and prevent a main storage area from being used wastefully when an operating system of a computer system is generated by linking device drivers. CONSTITUTION: Adapters 10 and 11 are provided with adapter identifications i0 and i1 and when the computer system is initialized, a host CPU 3 reads the identifications i0 and i1 in, generates the operating system by linking only necessary drivers d0 and d1 among device drivers d0, d1, d2... in an auxiliary storage device 5, and loads it to the main storage 4.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION In a computer system having a plurality of adapters for connecting a plurality of input / output devices (devices) and a plurality of dedicated input / output control programs (also called device drivers) for controlling these , The host CP during the initialization process of the computer system
U relates to a method of incorporating only a necessary input / output control program into an operating system according to an actually mounted adapter.

In the following drawings, the same reference numerals indicate the same or corresponding parts.

[0003]

2. Description of the Related Art Conventionally, in a system in which device drivers are statically incorporated, each device driver exists as one object file, and all device drivers are linked as part of an operating system. At this time, the information of the adapter to be incorporated into the adapter definition file etc. is defined in advance, and the information necessary for actual control created based on this definition file is reflected in the operating system. .

[0004]

The conventional method requires a procedure of previously defining adapter information in a file, and also requires knowledge for that purpose. Also,
There is a problem in that even device drivers that are not actually needed are linked to the operating system (in a dynamically incorporated system, they are individually loaded into the main memory), and the main memory is wasted.

The present invention is intended to solve the above problems by recognizing an actually mounted adapter, without requiring a troublesome definition, and by incorporating only necessary device drivers into a system.

[0006]

In order to solve the above-mentioned problems, the input / output control program embedding method of the present invention comprises:
Multiple adapters (1 to connect multiple I / O devices)
0, 11, etc.) and a plurality of dedicated input / output control programs (d0, d1, d2, ...) For controlling these, in a computer system (01, etc.), the adapter identification (i0 , I1, etc.), and the host CP is used during the initialization process of the computer system.
Read the adapter identifications of all the adapters in which U (3 etc.) are mounted, and link only the necessary I / O control programs to generate the operating system.

[0007]

[Function] The adapter is provided with an adapter identification, the host CPU is loaded with the adapter identification at the time of initialization processing of the computer system, and only the necessary input / output control program (device adapter) is linked to the operating system. To generate.

[0008]

EXAMPLE An example of a system in which a device driver is linked as one object constituting an operating system and the operating system is created as one executable file will be described below. FIG.
Is an adapter 1 for connecting the input / output devices 20 and 21.
A computer system 01 in which 0 and 11 are implemented is shown.
Each of the adapters 10 and 11 is readable by the host CPU 3 via the system bus 6 and is an adapter identification i.
0 and i1 are provided. Adapter identification i0, i1
Has a memory area required for the host CPU 3 to control the adapter identifications i0 and i1. This memory area is within a certain address range as seen from the host CPU 3.
Each of the adapters 10 and 11 is assigned with a certain boundary (hereinafter, this address is referred to as an adapter address).

The object files d0, d1, d2, ... Of the device driver are present in the auxiliary storage device 5 together with the other object file group f constituting the operating system. FIG. 2 is a flowchart showing the overall flow of the device driver incorporation processing of the computer system according to the present invention. Host CPU
3 first performs a loading process 201 of the operating system and then a creating process 202 of the mounted adapter information table (FIG. 4). As a result, it is checked whether or not there is a change in the mounted adapter (step 203), and if there is no change, the process ends. If there is any change, the created implementation adapter information table is reflected, a process of creating an executable file of a new operating system linked with a necessary device driver is performed (step 204), and then this is loaded into the main memory 4. (Step 20
5).

Details of the process of creating the mounted adapter information table in step 202 in FIG. 2 will be described with reference to FIGS. 3 and 4. Note that FIG. 3 is a flowchart of the process of creating the mounted adapter information table t, and FIG. 4 is an example of the mounted adapter information table t. The host CPU 3 reads the adapter identification (step 3) while sequentially updating the adapter address of the adapter that can be mounted (step 307).
02), it is checked whether the adapter is actually mounted (step 303). If the adapter is installed,
It is checked whether the adapter identifications i0 and i1 read at this time are registered in the adapter identification 401 of the mounted adapter information table t (step 304). If not registered, adapter identification 401, adapter number 402
(Serial number in the same adapter) and adapter address 403 are respectively registered in the mounted adapter information table t (step 305), and if already registered, adapter number 4
02, only the adapter address 403 is added (step 306). These processes are performed for all the adapter mountable addresses while updating the adapter addresses, the mounted adapter information table t is completed and stored in the auxiliary storage device 5, and this process ends (step 301).

Details of step 204 in FIG. 2 will be described with reference to FIG. Device driver object files d0, d1, d2 ... dn are stored in the auxiliary storage device 5.
And another object file group f constituting the operating system, the adapter / device driver correspondence table e and the mounted adapter information table t shown in FIG. First, based on the mounted adapter information table t, an object file t'of a table necessary for controlling the actual adapter is created. Next, referring to the mounted adapter information table t, the adapter identification i of the mounted adapter i
0 and i1 are taken out, and the device driver d corresponding to them is read from the adapter / device driver correspondence table e.
Calculate 0 and d1. By performing a link process 1 on these object file groups, it is possible to create an executable file F of the operating system that incorporates only the device driver required for the mounted adapter.

Thereafter, the newly created executable file F of the operating system is loaded into the main memory 4 (step 205 in FIG. 2).

[0013]

According to the present invention, since the host CPU reads the adapter identification of the adapter during the initialization process to recognize the actually mounted adapter and create the mounted adapter information table t, it is mounted in advance. There is no need to define the adapter to be used.

Further, since only the driver for the actually mounted adapter is incorporated, the main storage area is not wastefully used.

[Brief description of drawings]

FIG. 1 is a configuration diagram of a computer system as an embodiment of the present invention.

FIG. 2 is a flowchart showing the overall flow of an input / output control program incorporation process of the computer system according to the present invention.

FIG. 3 is a flowchart of a process of creating a mounted adapter information table of FIG.

FIG. 4 is a diagram showing a configuration example of a mounted adapter information table.

5 is an explanatory diagram of an operating system creation process in which the necessary device drivers of FIG. 2 are linked.

FIG. 6 is a configuration diagram of an adapter / device driver correspondence table.

[Explanation of symbols]

01 Computer system 3 Host CPU 4 Main memory 5 Auxiliary storage device 6 System bus 10, 11 Adapter 20, 21 I / O device i0, i1, i2, in Adapter identification d0, d1, d2, dn Device driver object file e Adapter Device driver correspondence table f Other object file groups of operating system t Implementation adapter information table t'Object file of table required for implementation adapter control F Executable format file of operating system

Claims (1)

[Claims] 1. A computer system having a plurality of adapters for connecting a plurality of input / output devices and a plurality of dedicated input / output control programs for controlling these, wherein the adapter is provided with an adapter identification, Built-in I / O control program, which reads the adapter identifications of all the adapters in which the host CPU is mounted at the initialization process of the above, and links only the necessary I / O control program to generate the operating system. Method.