JP2019114197A - Computer system - Google Patents

Abstract

To provide a computer system having an expansion method for an IO space for causing the number of connections of an IO device to be a large number without providing a dedicated circuit.SOLUTION: A computer system is configured by using: a BIOS holding an IO resource management table for separately managing an IO device group, and holding an interruption handler for switching IO space information allocated to each IO device managed by the IO resource management table in accordance with an SMI; and computer hardware including a chip set for generating an SMI each time access is generated between OS-IO devices and the access is made to a virtual IO space, and configured to enable access between the OS-IO devices by reading the interruption handler in accordance with the SMI and switching IO space information allocated to each IO device through a prescribed IO space secured on a CPU with reference to the IO resource management table.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a computer system, and more particularly to a management method that enables connection of a large number of IO devices (input / output devices).

  In IA (Intel Architecture), which is one architecture of a computer system, when a plurality of IO devices are operatively connected, IO space is allocated to each IO device.

  The IO space of the IA architecture has a capacity limit of 64 kilobytes. For this reason, when attempting to mount a large number of devices consuming IO space, if the IO space is exhausted, it becomes impossible to allocate IO space to some IO devices. As a result, an event occurs that can not use the IO device to which the IO space can not be allocated.

  With regard to this problem, attempts have been made to increase the number of IO devices that are operatively connected using technology to expand the IO space. For example, Patent Document 1 describes a technique for converting an IO space into a memory mapped IO space using a dedicated circuit.

Japanese Patent Application Laid-Open 7-200391

  In the IA standard architecture, when allocating IO space to individual IO devices in BIOS (Basic Input / Output System), each IO device is operatively connected using up to 64 kilobytes of IO space. In addition, when IO space is more than 64 kilobytes of IO devices connected, connection of some IO devices becomes inoperable due to lack of IO space.

  The IO space expansion method disclosed in Patent Document 1, which is one measure to increase the number of connected IO devices, requires a dedicated circuit.

  The present invention has been made in view of the above problems, and it is an object of the present invention to provide a computer system having an IO space expansion method that increases the number of connected IO devices without providing a dedicated circuit. Do.

  A computer system according to an embodiment of the present invention holds an IO resource management table for individually managing IO devices physically connected to an IO interface, and each IO managed in the IO resource management table The BIOS holds an interrupt handler that switches IO space information allocated to devices according to System Management Interrupts (SMI), and access occurs between the OS (Operating System) and IO devices, and virtual IO space is accessed. Each time the system management interrupt is generated, the interrupt handler is read out according to the system management interrupt, and each IO device is read via a predetermined IO space secured on a CPU (Central Processing Unit). Allocated to Computer hardware configured to allow access between OS-IO devices via the IO interface by switching the specified IO space information with reference to the IO resource management table; .

  In an IO device access method by a computer system according to an embodiment of the present invention, a BIOS holds an IO resource management table for individually managing IO devices physically connected to an IO interface, and the IO resource The interrupt handler that switches the IO space information allocated to each IO device managed by the management table according to the system management interrupt is held, and the computer hardware causes the chipset to access between the OS-IO devices and the virtual IO Each time the space is accessed, a system management interrupt is generated, and in response to the system management interrupt, the CPU reads the interrupt handler stored in the BIOS, and each of the CPUs receives a predetermined IO space secured in the CPU. I The IO space information allocated to the device is switched with reference to the IO resource management table, and the access between the OS and IO devices is established based on the switched IO space information through the IO interface. I assume.

  According to the present invention, it is possible to provide a computer system having an IO space expansion method for increasing the number of connected IO devices without providing a dedicated circuit.

It is a block diagram showing composition of computer system 1 of an embodiment. FIG. 6 is an explanatory view showing an IO resource management table used in the computer system 1 in a visualized manner. 5 is a flowchart showing an IO device access method of the computer system 1; It is a block diagram showing another composition of computer system 1 of an embodiment. 5 is a flowchart illustrating an exemplary initialization process of the computer system 1; 5 is a flowchart illustrating an example of IO space virtualization processing of the computer system 1;

  Embodiments of the present invention will be described based on the drawings.

[Embodiment]
FIG. 1 is a block diagram showing the configuration of a computer system 1 according to the embodiment.

  The computer system 1 is a computer system adopting an IA. The computer system 1 includes computer hardware 10 and a BIOS 20 (BIOS ROM) as physical components. The computer hardware 10 includes a CPU, a memory, a chip set, and peripheral circuits that employ an IA. The computer hardware 10 also includes an IO interface 30 for physically connecting the IO device group 40. Software operating on the computer hardware 10 (CPU) includes an OS and a driver for each IO device.

  The computer hardware 10 (chip set) is created to generate a system management interrupt (SMI) in response to an access to the virtual IO space from the OS (device driver). By having this function, the BIOS receives a system management interrupt generated by the CPU for each access between the OS and IO devices, and executes a process of switching an IO space to be described later in the IO system management interrupt mode.

  The IO device group 40 is a general IO device, at least one or more are connected, and a large number are connected as needed.

  The BIOS 20 holds and manages the IO resource management table 21. The BIOS 20 also holds the interrupt handler 22.

  The IO resource management table 21 records IO space information allocated to each IO device for individually managing the IO device group 40 physically connected to the IO interface 30.

  FIG. 2 is an explanatory diagram visualizing the data structure of the IO resource management table 21. As shown in FIG. The IO resource management table 21 includes, for each IO device (device A and device B in the figure), virtual IO port information that defines the use port of a predetermined IO space, device IO information where IO space information is recorded, including. The virtual IO port information includes virtual IO index port information and virtual IO data port information that define the used port of each IO device in a predetermined IO space in the CPU. Also, the IO space information for each IO device includes a virtual IO base address functioning as an IO base address and a virtual IO size functioning as an IO size. The virtual IO base address and the virtual IO size include the IO base address and the IO size of the IO device when temporarily reassigning each IO device in the IO space switching process. Further, in the IO resource management table 21, it is desirable that configuration address information be provided for each IO device as illustrated. The device configuration address information includes an address used when setting an IO port address for each IO device. Similarly, a table number may be allocated to the IO resource management table 21 for each IO device.

  The interrupt handler 22 is read by the CPU in response to a system management interrupt notified in response to an access between each IO device and the OS, and IO space information allocated to each IO device managed in the IO resource management table 21 Switch according to the access destination IO device.

  When rewriting the IO space information in the predetermined IO space, the interrupt handler 22 reads the IO space information of the corresponding IO device from the IO resource management table with the virtual IO port information of the IO device as an argument, and is allocated to the corresponding IO device The value of the IO space is set in a predetermined IO space.

  Further, when rewriting the IO space information in the predetermined IO space, the interrupt handler 22 reads the IO space information of the corresponding IO device from the IO resource management table 21 using the table number of the IO device as an argument and allocates it to the corresponding IO device The value of the IO space may be set in a predetermined IO space.

  The present invention provides an IO space expansion method that increases the number of connected IO devices without providing a dedicated circuit by incorporating the BIOS 20 having the above configuration into the computer system 1 adopting IA.

  The operation of computer system 1 operates generally as shown in the flowchart of FIG.

  The IO device access method provided by the computer system 1 includes the step of recording IO space information on a large number of IO devices physically connected in advance in the IO resource management table 21 with the system configuration described above. (F101).

  Next, when an access between the OS and IO devices occurs, the computer hardware 10 (chipset) is a target before accessing the IO port of the target IO device and acquiring a value (device IO information). Each time a system management interrupt indicating that access to the IO port of the IO device has occurred is generated (F102).

  Next, the computer hardware 10 (CPU) detects a system management interrupt generated by the chipset, and reads the interrupt handler 22 from the BIOS 20 (F103).

  Next, the interrupt handler 22 rewrites the IO space information based on the IO resource management table 21 with regard to the use IO port of the corresponding IO device accessed in the predetermined IO space secured on the CPU as IO space switching processing. (F104). That is, as IO space switching processing, the CPU refers to the virtual IO address and virtual IO size of the corresponding IO device recorded in the IO resource management table 21 from the BIOS 20, and temporarily stores the IO space for the corresponding IO device. assign.

  After that, the OS accesses the IO device using the rewritten IO space information (F105).

  Explaining the above operation from another point of view, the computer hardware 10 generates a system management interrupt and enters the system management interrupt mode when the device driver accesses the IO port (virtual IO port) through the OS. Transition. The computer hardware 10 refers to the IO resource management table 21 under the system management interrupt mode, and switches the IO space to the virtual IO address and virtual IO size allocated to the corresponding IO device. After the virtual IO emulation processing, the OS accesses the IO device using the rewritten IO space information.

  The subsequent operation is the same as that of the IA computer system in which the IO space is not virtualized, and operates as follows. In the case of write access from the device driver to the Index register of the virtual IO port, the CPU calculates the address of the allocated IO space from the value of Index, and stores the read data in the Data register. In the case of write access from the device driver to the Data register of the virtual IO port, the CPU calculates the address of the allocated IO space from the Index value, and writes the value of the Data register to the corresponding register.

  The IO space is switched to IO space information of the target IO device by the flow F103 and the flow F104. By including the step of switching the IO space information in the computer hardware 10 using this system management interrupt, it is possible to virtually switch the IO space to the IO space information required by the target IO device. As a result, this switching is performed each time, and each hardware can access the OS-IO devices using the IO space allocated to each IO device.

  As described above, when access to any IO device from the OS occurs, the computer hardware 10 uses the IO address and size values based on the IO resource management table 21 managed in the BIOS 20 on the CPU. By sequentially arranging in the predetermined IO space, virtualization of the IO space is realized.

  In the above IO device access method, when the interrupt handler 22 rewrites the IO space information, it has been described that the virtual IO space is set with the virtual IO port information of the IO device as an argument, but the table number of the IO device is used as an argument The virtual IO space may be set.

  For example, a virtual IO port may be installed as shown in FIG. 4 using a table number as an argument. By configuring in this way, when corresponding to virtual IO ports of a plurality of IO devices, the number of times of newly allocating Index and Data ports for each IO device decreases, and as a result, IO space is not further consumed. It becomes possible.

  Here, the invention will be described by exemplifying initialization processing of the computer system 1 and IO space virtualization processing.

  FIG. 5 is a flowchart showing an example of initialization processing of the computer system 1. By this process, the interrupt handler 22 and the IO resource management table 21 can be initialized.

  The BIOS 20 initializes the interrupt handler 22 and the IO resource management table 21 at the time of POST (Power On Self Test). First, the BIOS 20 initializes the virtual IO Index and Data variables used in initialization, sets the Table No variable in the IO resource management table 21 to "1", and sets the device configuration address to "0" ( S501).

  Next, the BIOS 20 checks whether the IO device requires the IO space using the device configuration address (S502), and if the IO space is required (503), acquires the IO size from the IO device (S504) ). The BIOS 20 sets the address of the virtual IO Index port, the address of the Data port, the virtual IO base address, the virtual IO size, and the device configuration address in the table column indicated by the Table No variable of the IO resource management table 21 (S505).

  Next, the BIOS 20 increments the virtual IO Index, virtual IO Data, and Table No variables (S506).

  Next, after incrementing the device configuration address (S507), the BIOS 20 checks whether there is another IO device (S508). If there is another IO device, the BIOS 20 again carries out a process (S502) to confirm whether the IO device requires the IO space. If there is no other IO device, the BIOS 20 performs setting to generate an SMI from the chipset when access to the virtual IO Index and Data Port registered in the IO resource management table 21 is received (S 509).

  By operating the computer system 1 in this manner, the interrupt handler 22 and the IO resource management table 21 can be initialized.

  FIG. 6 is a flowchart showing an example of IO space virtualization processing of the computer system 1. This IO space virtualization process is executed by the interrupt handler 22 read by the CPU. When the SMI from the chipset is received from the OS (device driver) for the virtual IO port, the interrupt handler 22 is read from the BIOS 20 to the CPU. Thereafter, the interrupt handler 22 virtually operates the IO space as follows (performs virtual IO emulation processing).

  The interrupt handler 22 searches the IO resource management table 21 for information on the accessed virtual IO port (S601).

  Next, based on the IO device configuration address and virtual IO base address information in the IO resource management table 21, the interrupt handler 22 performs setting of the IO base address and validity of IO space for the corresponding IO device. (S602).

  Next, the interrupt handler 22 determines whether the write is to the virtual IO Index (S603), and if applicable (Yes in S603), the value stored in the virtual IO Index Port is added to the IO base address Read access is performed on the address (S604).

  Thereafter, the interrupt handler 22 stores the read data in the virtual IO Data Port (S605). If it is not a write to the virtual IO Index (No in S603), the interrupt handler 22 subsequently determines whether it is a write to the virtual IO Data (S606), and if applicable, the virtual IO Index Port for the IO base address The value of virtual IO Data is written to the address obtained by adding the value stored in. If the write to the virtual IO Index or the write to the virtual IO Data is not performed (No in S606), the interrupt handler 22 does not access the corresponding IO device.

  Thereafter, the interrupt handler 22 clears the IO base address and invalidates the IO space for the corresponding IO device (S608).

  By operating the computer system 1 in this manner, the IO handler can implement IO space virtualization processing.

  As described above, the computer system to which the present invention is applied can provide a virtual IO space in which the number of connected IO devices is increased without providing a dedicated circuit.

  The present invention constructs a virtual IO space with BIOS 20 in order to avoid exhaustion of IO space, switches the IO space actually used by BIOS 20 for access to the virtual IO space from the CPU, and then switches to the IO device Make access to As a result, by using the virtual IO space, it is possible to implement many IO devices without worrying about the exhaustion of the IO space.

  When the IO space is exhausted, an error may be detected in POST (PowerOnSelfTest) and the system may not start up. The invention also makes it possible to improve the case.

  The present invention has been described by exemplifying the embodiment. However, the specific configuration of the present invention is not limited to the above-described embodiment, and any changes without departing from the scope of the present invention are included in the present invention. For example, modifications such as separation and merging of block configurations and replacement of procedures in the above-described embodiment are free as long as the purpose of the present invention and the functions to be described are satisfied, and the above description does not limit the present invention.

Also, some or all of the above embodiments may be described as follows. The following appendices do not limit the present invention at all.
[Supplementary Note 1]
An IO resource management table for individually managing an IO device group physically connected to an IO interface is held, and IO space information allocated to each IO device managed in the IO resource management table is used as a system management interrupt With the BIOS that holds the interrupt handler that switches accordingly
The chipset includes a chipset for generating the system management interrupt each time access is made between the OS-IO device and the virtual IO space is accessed, and the interrupt handler is read in response to the system management interrupt and reserved on the CPU. Is configured to allow access between OS-IO devices through the IO interface by switching the IO space information allocated to each IO device with reference to the IO resource management table via the predetermined IO space. Computer hardware, and
A computer system comprising:

[Supplementary Note 2]
The IO resource management table includes, for each IO device, virtual IO port information that defines a use port of the predetermined IO space, and device IO information in which the IO space information is recorded.
In the virtual IO port information for each IO device, a virtual index port and a virtual data port which define a use port of a predetermined IO space in the CPU are recorded,
In the IO space information for each IO device, a virtual IO base address functioning as an IO base address and a virtual IO size functioning as an IO size are recorded.
The computer system according to claim 1, characterized in that:

[Supplementary Note 3]
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the corresponding IO device from the IO resource management table with the virtual IO port information of the IO device as an argument, to the corresponding IO device The computer system according to claim 1 or 2, wherein the value of the allocated IO space is set in the predetermined IO space.

[Supplementary Note 4]
In the IO resource management table, a table number is assigned to each IO device,
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the IO device from the IO resource management table using the table number of the IO device as an argument, and allocates the IO device to the IO device. The computer system according to claim 1 or 2, wherein the value of the IO space is set in the predetermined IO space.

[Supplementary Note 5]
The BIOS holds an IO resource management table for individually managing IO devices physically connected to an IO interface, and a system for allocating IO space information allocated to each IO device managed in the IO resource management table Hold an interrupt handler that switches according to the management interrupt,
The computer hardware causes the chipset to generate the system management interrupt each time access is made between OS-IO devices and the virtual IO space is accessed.
In response to the system management interrupt, the CPU reads an interrupt handler stored in the BIOS, and IO space information allocated to each IO device is managed through the predetermined IO space secured in the CPU. Refer to the table and switch,
An IO device access method comprising establishing access between OS-IO devices based on switched IO space information via the IO interface.

[Supplementary Note 6]
The IO resource management table includes, for each IO device, virtual IO port information that defines a use port of the predetermined IO space, and device IO information in which the IO space information is recorded.
In the virtual IO port information for each IO device, a virtual index port and a virtual data port which define a use port of a predetermined IO space in the CPU are recorded,
In the IO space information for each IO device, a virtual IO base address functioning as an IO base address and a virtual IO size functioning as an IO size are recorded.
The IO device access method according to claim 5, characterized in that:

[Supplementary Note 7]
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the corresponding IO device from the IO resource management table with the virtual IO port information of the IO device as an argument, to the corresponding IO device The IO device access method according to any one of appendices 5 or 6, wherein the value of the allocated IO space is set in the predetermined IO space.

[Supplementary Note 8]
In the IO resource management table, a table number is assigned to each IO device,
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the IO device from the IO resource management table using the table number of the IO device as an argument, and allocates the IO device to the IO device. The IO device access method according to any one of appendices 5 or 6, wherein the value of the IO space is set in the predetermined IO space.

1 computer system 10 computer hardware 20 BIOS
21 IO resource management table 22 interrupt handler 30 IO interface 40 IO device group

Claims (8)

An IO resource management table for individually managing an IO device group physically connected to an IO interface is held, and IO space information allocated to each IO device managed in the IO resource management table is used as a system management interrupt With the BIOS that holds the interrupt handler that switches accordingly
The chipset includes a chipset for generating the system management interrupt each time access is made between the OS-IO device and the virtual IO space is accessed, and the interrupt handler is read in response to the system management interrupt and reserved on the CPU. Is configured to allow access between OS-IO devices through the IO interface by switching the IO space information allocated to each IO device with reference to the IO resource management table via the predetermined IO space. Computer hardware, and
A computer system comprising: The IO resource management table includes, for each IO device, virtual IO port information that defines a use port of the predetermined IO space, and device IO information in which the IO space information is recorded.
In the virtual IO port information for each IO device, a virtual index port and a virtual data port which define a use port of a predetermined IO space in the CPU are recorded,
In the IO space information for each IO device, a virtual IO base address functioning as an IO base address and a virtual IO size functioning as an IO size are recorded.
The computer system according to claim 1, characterized in that:   When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the corresponding IO device from the IO resource management table with the virtual IO port information of the IO device as an argument, to the corresponding IO device The computer system according to claim 1 or 2, wherein the value of the allocated IO space is installed in the predetermined IO space. In the IO resource management table, a table number is assigned to each IO device,
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the IO device from the IO resource management table using the table number of the IO device as an argument, and allocates the IO device to the IO device. The computer system according to claim 1 or 2, wherein the value of the IO space is set in the predetermined IO space. The BIOS holds an IO resource management table for individually managing IO devices physically connected to an IO interface, and a system for allocating IO space information allocated to each IO device managed in the IO resource management table Hold an interrupt handler that switches according to the management interrupt,
The computer hardware causes the chipset to generate the system management interrupt each time access is made between OS-IO devices and the virtual IO space is accessed.
In response to the system management interrupt, the CPU reads an interrupt handler stored in the BIOS, and IO space information allocated to each IO device is managed through the predetermined IO space secured in the CPU. Refer to the table and switch,
An IO device access method comprising establishing access between OS-IO devices based on switched IO space information via the IO interface. The IO resource management table includes, for each IO device, virtual IO port information that defines a use port of the predetermined IO space, and device IO information in which the IO space information is recorded.
In the virtual IO port information for each IO device, a virtual index port and a virtual data port which define a use port of a predetermined IO space in the CPU are recorded,
In the IO space information for each IO device, a virtual IO base address functioning as an IO base address and a virtual IO size functioning as an IO size are recorded.
The IO device access method according to claim 5, characterized in that:   When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the corresponding IO device from the IO resource management table with the virtual IO port information of the IO device as an argument, to the corresponding IO device 7. The IO device access method according to claim 5, wherein the value of the allocated IO space is set in the predetermined IO space. In the IO resource management table, a table number is assigned to each IO device,
When switching the IO space information in the predetermined IO space, the interrupt handler reads the IO space information of the IO device from the IO resource management table using the table number of the IO device as an argument, and allocates the IO device to the IO device. 7. The IO device access method according to claim 5, wherein the value of the IO space is set in the predetermined IO space.

Images