KR950005798B1 - Method installing scsi unit driver in user level - Google Patents

Abstract

The method adds a SCSI device to a system at user level regardless of operating system organization. It comprises the steps of: (i) using input information of an additional device driver; (ii) changing packet according to characteristic of an additional device; (iii) loading as a part of kernel through a device driver at low level; and (iv) driving a device driver after passing a control right to device driver.

Description

How to install a user-level SCSI device driver

1 is a block diagram schematically showing the configuration of a system to which the present invention is applied.

2 is a flow chart for explaining the method of the present invention.

Figure 3 is a flowchart of the SCSI device driver installation.

Figure 4 is a flow chart of the SCSI device driver operation.

The present invention relates to a method of additionally attaching a SCSI (SCSI) device at a user level to a running system regardless of the configuration of an operating system in a system running small computer system interface (SCSI) devices.

Conventionally, in order to additionally install a new type of device driver, a device driver has to be developed and created, and the system generation procedure must be followed during the configuration and generation of an operating system. As a result, the technical burden, including the interface with other interconnected modules, is considerably high, but it intercepts the interface part of the low-level device for SCSI device operation and transforms the message exchange packet for information exchange. There is a need for a method that can be conveniently installed while the system is running, relieving the burden of reconfiguring the system by transferring control.

The present invention aims to increase system scalability as well as availability by providing a method of matching a new type of SCSI device with other devices without affecting the configuration and creation of the operating system and system startup for such requirements. do.

In order to achieve the above object, the present invention selects information about SCSI driver-related variables and constant values in the locations of the memory in which the operating system is installed in an operating system, and inputs elements for preparing a device driver to be additionally mounted. Extracting and intercepting the control of the low-level device driver copy, modifying the message packet as a SCSI device to suit the characteristics of the additional device, changing the driving method, and reconfiguring the device driver through the kernel memory device. Is mounted in the system reserved area, and the control is transferred to the device driver reconfigured and mounted due to the occurrence of a system-level exception trap at the user level, thereby enabling system expansion for the initial startup of a new device.

The present invention will now be described in detail with reference to the accompanying drawings.

1 is a hardware configuration to which the present invention is applied and shows a connection path between a processor board and a memory board and a SCSI control board.

In a system with a SCSI device driver, the processor board constructs a message packet of the type promised to the memory board and instructs the SCSI control board to start the memory by way of an interrupt delivery. The SCSI control board receives the work order from the processor board and drives the devices connected to the SCSI bus according to the message packet transmitted. Upon completion, the SCSI control board notifies the processor board through an interrupt and waits for new work.

The SCSI control board uses intelligent firmware to communicate with the board by short information. When the SCSI devices are running, the SCSI control board divides the steps into a SCSI packet and processes a series of tasks. However, it also provides a pass-through method that allows processor boards to use SCSI packets directly for vendor unique and separate SCSI driver control, and the SCSI bus provides a daisy chamfer. You can easily add devices to your old devices.

2 is a flow chart for schematically explaining a procedure with a drive by additionally installing a SCSI device according to the present invention. The newly added SCSI device is assigned a device unique number that is selected from a number that does not duplicate an already installed SCSl device.

SCSI devices can be extended by hooks, but always the last connected device should have a terminator. Therefore, remove the breaker after the last device, connect the new device with a SCSI cable, and install the breaker at the end of the new device.

Since the selected device number is important information for the device driver installation, it should be designated as the same value when creating the device driver. When the operating system is loaded into the main memory, the variables for various information can be read at the user level, and these are important items in the device driver creation, and are an important process to extend and configure the system.

3 is a flowchart of a procedure for extracting information from an operating system mounted on a system and additionally mounting a new SCSI device under control of the operating system. For the new device driver, set a variable to distinguish the existing driver and the added driver by the device configuration information and the device number and replace the device number of the new device (10).

To extract the values of the variables from the on-board operating system, it is possible by reading the variable positions 20 through the memory device driver, and the positions of the variables can be found using a symbol table of the kernel file. The necessary variable is the position of the low-level SCSI driver that is responsible for sending messages to the SCSI control board, and is replaced with an instruction to jump to the position of the new device driver at this position (30). In addition, in the configuration information table (unit information table) for each SCSI device, the values of the device characteristics of the new device are set through an initialization operation (40), and then set to be recognized as a usable device (50).

4 is a flow chart of the operation of the driver itself of the retrofit apparatus.

It intercepts the low-level SCSI driver and checks the device number to determine if the new device driver is in control and determines whether it is a packet forwarded to the new device from the forwarded message packet (60). In the case of a packet for a new device (70), in order to transform a SCSI packet according to the device characteristic into a new packet, detailed values of various variables according to the type of short command are collected and completed as necessary in a new packet (80). It converts the command to a SCSI command (90) and transfers control back to the existing SCSI drive (100).

Packet transformation is a device-dependent part, and when various devices are installed according to this principle, new devices can be used without modifying the original kernel and firmware, thus extending the current system to the user level.

The present invention composed of the above-described processing procedure can be additionally installed according to the characteristics of each device even for a separate SCSI device that is not provided in the basic system by the packet modification method of the device driver at the user level, so as to make the system availability and configuration of the operating system Since it is not directly related to creation, it is not affected by the set of limitations of creating a new operating system, which has the adaptive effect of increasing the scalability to add devices while the system is running.

Claims (3)

In the configuration of a processor board, a memory board, and a SCSI control board, a step of using input information of a device driver to be newly added by reading the memory location in which the operating system is mounted while the system is running, and a message packet sent to the SCSI control board Intercepts and modifies the packet according to the characteristics of the device to be added, mounts it as part of the kernel through a newly configured low-level device driver in the reserved area of the system, and handles the user's exception status. And transferring the control right to the reconfigured device driver in the state transitioned to the level to start the driver. The method of claim 1, wherein the mounting step comprises: setting a variable for distinguishing an existing driver from an added driver by the device number and contents of the device configuration information, and replacing the device driver with a device bunny of a new device; Reading the variable position through the driver, substituting the instruction for jumping to the position of the new device driver, and setting values related to the device characteristics of the new device through the initial and working steps. And setting the next flag value to be recognized as a usable device. The method of claim 1, wherein the starting step comprises: checking a device number to determine whether a new device driver is a packet transmitted to a new device from a message packet transmitted by taking over a control right; In order to transform into a SCSI packet according to a characteristic, the steps of completing the necessary values of various variables in a new packet according to the type of short command are completed, replacing the command of the original packet with the SCSI command, and then moving to the existing SCSI drive part. Installing a user-level SCSI device driver comprising the step of passing back control.