CN102043643B - How to install an interrupt event handler - Google Patents

Abstract

The invention relates to a method for installing an interrupt event handler, which is suitable for a computer system to install the interrupt event handler under an operating system to service an interrupt event. In the method, a virtual function of the multi-function peripheral component interconnect device is established through the BIOS, and one unused or virtual interrupt pin is selected to simulate a virtual interface device through the interrupt pin and the virtual function. Then, the interrupt related data of the virtual interface device is recorded to the interrupt routing table through the basic input output system. And then, setting and obtaining the interrupt number of the virtual interface device according to the interrupt routing table through the operating system, and installing an interrupt event processing program according to the interrupt number. The method for installing the interrupt event handler provided by the invention is used for installing the interrupt event handler aiming at the interrupt event without the corresponding peripheral component interconnection device.

Description

How to install an interrupt event handler

technical field

The present invention relates to an interrupt service mechanism, in particular to a method for installing an interrupt event processing program for an interrupt event without a corresponding Peripheral Component Interconnect (referred to as: PCI) device.

Background technique

Interrupt Request (Interrupt Request, referred to as: IRQ) is used to notify and request the central processing unit to suspend work when a certain device is about to perform a specific action, so that the central processing unit executes the corresponding calculation action. Traditional computers use Programmable Interrupt Controller (PIC for short) or Advanced Programmable Interrupt Controller (APIC for short) to receive interrupt requests and send corresponding interrupt signals to central processing unit.

Generally speaking, under the operating system, for example, when an application such as hot plug occurs, the peripheral device will send an interrupt event (event) to trigger an interrupt to start a corresponding interrupt event handler (interrupt event handler). However, this interrupt does not have a corresponding Peripheral Component Interconnect (referred to as: PCI) device in the computer system, so it cannot share the interrupt request with other PCI devices, so the operating system cannot find the corresponding handler for this interrupt. , so the operating system cannot service this interrupt event.

Contents of the invention

The object of the present invention is to provide a method for installing an interrupt event processing program, so as to install the interrupt event processing program for interrupt events that do not have a corresponding Peripheral Component Interconnect (PCI) device.

The embodiment of the present invention provides a method for installing an interrupt event processing program, which is suitable for a computer system to use the interrupt event processing program to serve an interrupt event under an operating system. Here, the computer system includes a basic input output system (Basic Input Output System, referred to as: BIOS) and a multifunctional peripheral component interconnect (abbreviated as: PCI) device, wherein the multifunctional peripheral component interconnect device has no Use or dummy interrupt pin. The method includes: establishing a virtual function in the multifunction peripheral device interconnection through the basic input output system, and selecting one of the unused or virtual interrupt pins to emulate a virtual function through the selected interrupt pin and the virtual function virtual interface device; record the interrupt-related data of the virtual interface device to the interrupt routing table through the basic input and output system; set and obtain the interrupt number of the virtual interface device according to the interrupt routing table through the operating system; and install the virtual interface device according to the interrupt number through the operating system Interrupt event handler.

In an embodiment of the present invention, the step of setting and obtaining the interrupt number of the virtual interface device by the operating system according to the interrupt routing table includes: according to the bus number, device number and interrupt number of the virtual interface device recorded in the interrupt routing table Pin number, set and get the interrupt number of the virtual interface device.

In an embodiment of the present invention, the above-mentioned step of installing the interrupt event processing program according to the interrupt number through the operating system includes: according to the interrupt number, installing the interrupt event processing program into the corresponding interrupt number column of the interrupt vector table through the operating system bit inside.

In an embodiment of the present invention, the above-mentioned interrupt routing table includes an interrupt request routing (IRQRouting) table of a Programmable Interrupt Controller (Programmable Interrupt Controller, referred to as: PIC), a multi-processor specification (Multi-Processor Specification, referred to as : MPS) configuration form and advanced configuration and power interface (Advanced Configuration and PowerInterface, referred to as: ACPI) form.

In an embodiment of the present invention, the above-mentioned method for installing an interrupt event handler further includes: reserving an interrupt request to the virtual interface device through the BIOS, and setting the interrupt request as a level trigger.

In an embodiment of the present invention, the above-mentioned MPI device will not be disabled.

Based on the above, the embodiment of the present invention emulates a virtual interface device through the existing PCI device, so as to connect the interrupt event sent by the hardware device to any interrupt pin, so that the operating system can install the corresponding interrupt event handler to serve This interrupt event.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail with reference to the accompanying drawings.

Description of drawings

FIG. 1 is a flowchart of a method for installing an interrupt event handler according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a simulation-virtual interface device according to an embodiment of the present invention.

Description of main component symbols:

200: computer system; 210: central processing unit;

220: North Bridge Chip; 230: South Bridge Chip;

240: PIC controller; 250: wiring register;

260: IO APIC controller; 270: PCI device;

280: virtual interface device;

S105-S120: each step of the method for installing an interrupt event processing program according to an embodiment of the present invention.

Detailed ways

In order to make the content of the present invention clearer, the following specific examples are given as examples in which the present invention can actually be implemented.

FIG. 1 is a flowchart of a method for installing an interrupt event handler according to an embodiment of the present invention. Referring to FIG. 1, in step S105, a virtual interface device is simulated by a Basic Input Output System (BIOS for short). Specifically, the BIOS establishes a virtual function in a multi-function peripheral component interconnection (multi-function PCI device) device, and selects one of the unused or virtual interrupt pins of the multi-function PCI device to pass This interrupt pin is used with virtual functions to emulate a virtual interface device.

For example, FIG. 2 is a schematic diagram of simulating a virtual interface device according to an embodiment of the present invention. Please refer to FIG. 2 , in this embodiment, the computer system 200 includes a central processing unit 210 , a north bridge chip 220 and a south bridge chip 230 . The south bridge chip 230 includes a programmable interrupt controller (Programmable Interrupt Controller, referred to as: PIC controller) 240, a routing register 250, and an IO Advanced Programmable Interrupt Controller (IO Advanced Programmable Interrupt Controller, referred to as: IO APIC controller) 260 and PCI device 270.

The PIC controller 240 and the IO APIC controller 260 are used to receive the interrupt request sent by the peripheral device (not shown), so as to generate a corresponding PCI interrupt signal and send it to the central processing unit 210, so that the central processing unit 210 can respond to this request. PCI interrupt signal to start and execute the corresponding interrupt event handler.

In this embodiment, the BIOS (not shown) looks for a multi-function PCI device that will not be disabled in the computer system 200, such as the PCI device 270 in the south bridge chip 230, to simulate a virtual PCI device 270 using the PCI device 270 interface device. Here, the PCI device 270 has multiple functions (function 0-6) and interrupt pins INT A, B. Because the PCI device 270 only has and uses INT A, B, so INT C, D are non-existent interrupt pins (that is, virtual interrupt pins). Therefore BIOS just selects a non-existing interrupt pin (for example, INT C), and establishes a non-existing function (for example, function 7) from PCI device 270, thereby simulates a non-existing virtual interface device 280, namely Virtual PCI device bus0/device31/function 7 with interrupt pin INT C.

Here, the interrupt event in this embodiment is, for example, a hot plug interrupt event of a hardware device. Because the hot-swap interrupt event does not have a corresponding PCI device, the virtual interface device 280 simulated by the interrupt pin INT C and function 7 of the PCI device 270 makes the central processing unit 210 think that the hot-swap interrupt event is caused by the virtual interface device 280 issued.

The virtual interface device 280 is connected to the PIRQ G pin of the south bridge chip 230 via the path PIRQ G, and its corresponding wiring temporary register 250 is a PIRQ G temporary register (its temporary register address is, for example, 6Ah), which stores An interrupt request number, such as IRQ5. In addition, the virtual interface device 280 is also connected to the interrupt pin 22 of the IOAPIC controller 260 .

After simulating the above-mentioned virtual interface device 280 , then return to FIG. 1 , in step S110 , record the interrupt-related data of the virtual interface device 280 into the interrupt routing table through the BIOS. Generally speaking, the interrupt routing table provided by BIOS includes: Programmable Interrupt Controller (Programmable Interrupt Controller, referred to as: PIC) interrupt request routing (IRQ Routing) table, multi-processor specification (Multi-Processor Specification, referred to as: MPS) ) configuration form and advanced configuration and power interface (Advanced Configuration and Power Interface, referred to as: ACPI) form, for the operating system in standard mode (PIC), MPS mode (APIC) or ACPI mode (PIC or APIC ) under use.

Furthermore, when the operating system is in PIC mode, the BIOS will reserve an interrupt request for the virtual interface device 280, and set the interrupt request as a level trigger. Moreover, the BIOS will create an entry in the PIR (PCI Interrupt Request) table to record the interrupt-related data of the virtual interface device 280 .

For example, taking FIG. 2 as an example, the items of the PIR table are: <00h, 0F8h, 0062h, 0DC58h, 0061h, 0DC58h, 006Ah, 00020h, 0000, 00000, 00, 0>. Among them, 00h means that the bus number is 0; 0F8h means that the device number is 31; A bitmap (bitmap) of scratchpad addresses and available interrupt request numbers. That is to say, the interrupt pin INT C (the interrupt pin used by the virtual interface device 280) of the PCI device with bus number 0/device number 31 is connected to the interrupt router (interrupt router) whose register address is 6Ah , and the available interrupt request number is 5.

Furthermore, in the PIC mode, the BIOS will also create the item of the virtual interface device in the program (method)_PRT of the AML (ACPI Machine Language) program in the ACPI table. Taking Figure 2 as an example, this item is: Package () {0x001FFFFF, 2, LNKG, 0}, where 001F means that the device number is 31, 2 means INT C, and the program (method) LNKG is used to report IRQ Number.

In addition, in the MPS mode, the BIOS also creates an item in the MPS table. Referring to Figure 2, this item can be divided into source (resource) and destination (destination). The source records the bus number, interrupt pin number and device number, for example, "0:PCI,7eh:INT_C#1fh", 0 represents the bus number, 1fh represents the device number. The purpose records the identification code, interrupt pin number, polarity, trigger condition, etc. of the IO APIC controller 260, for example, "2, 22, Low, Level, INT", 2 represents the IO APIC controller 260 The identification code, 22 represents the interrupt pin number, Low represents the low polarity, and Level represents the level trigger; that is to say, the interrupt pin 22 of the IO APIC controller 260 numbered 2 will be triggered when the low level is active.

In addition, in the ACPI APIC mode, the program (method)_PRT of the AML program in the ACPI table creates the item of the virtual interface device. For example: Package(){0x001FFFFF, 2, 0, 22}, where 001F represents the device number, 2 represents INT C, and 22 represents the global interrupt pin number of the IO APIC controller; that is to say, bus number 0/device The interrupt pin INTC of the PCI device number 31 (the interrupt pin used by the virtual interface device 280 ) will be connected to the interrupt pin number 22 of the global interrupt pin.

After that, in step S115, the operating system can set and obtain the interrupt number of the virtual interface device according to the interrupt routing table. Furthermore, the initialization program of the interrupt event handler can call the operating system to obtain the interrupt number. The operating system sets the south bridge chip 230 and the north bridge chip 220 according to the bus number, device number and interrupt pin number of the virtual interface device recorded in the interrupt routing table to obtain the interrupt number of the virtual interface device 280 .

Finally, in step S120, the operating system installs the interrupt event handler according to the interrupt number. That is to say, there is an interrupt vector table in the memory, and the operating system will write the entry point of the interrupt event handler into the column of the corresponding interrupt number in the interrupt vector table, so when the central processing unit 210 receives an interrupt , it will go to the interrupt vector table to read the value corresponding to the interrupt number to obtain the entry point of the interrupt event handler, and hand over the control right of the central processing unit (Central Processing Unit, referred to as: CPU) 210 to enter here point.

Take the interrupt event processing program of hardware device hot plugging, when the hardware device is hot-unplugged, the interrupt event processing program will check which hardware device has been removed, and notify other applications or service programs that the hardware device has been removed. was removed to allow it to respond appropriately. For example, the icon of the hardware device is set to a removed state, and the operating system is notified to uninstall (uninstall) the driver of the hardware device controller. On the other hand, when a hardware device is hot-plugged, the interrupt event handler will check which hardware device is plugged in, and notify other application programs or service programs that the hardware device has been plugged in, so that it can take appropriate actions. respond. For example, the icon of the hardware device is set to the plug-in state, and the operating system is notified to install the driver of the hardware device controller.

In summary, the above embodiment is based on simulating a virtual function on a PCI device, and based on the virtual function of the PCI device, the operating system can correctly install the interrupt event handler to the interrupt number of the correct interrupt vector table field. That is to say, since there is no corresponding PCI device for the interrupt event, a virtual interface device is simulated to make the central processing unit believe that the interrupt event is sent by the PCI device. Accordingly, through the method of the above embodiment, the interrupt event sent by the hardware can be connected to any interrupt pin, so that the operating system can install a corresponding interrupt event handler to service the interrupt event.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that: it still Modifications or equivalent replacements can be made to the technical solutions of the present invention, and these modifications or equivalent replacements cannot make the modified technical solutions deviate from the spirit and scope of the technical solutions of the present invention.

Claims (6)

1. A method for installing an interrupt event handler is applicable to a computer system utilizing the interrupt event handler service interrupt event under an operating system, and the computer system includes a basic input output system and a multifunctional peripheral component interconnection device, wherein The MPI includes unused or virtual interrupt pins, and the method includes: Establish a virtual function in the multi-function peripheral component interconnection device through the basic input output system, and select one of the plurality of interrupt pins that are not used or virtual, to communicate with the interrupt pin through the interrupt pin virtual functions to emulate virtual interface devices; recording the interrupt-related data of the virtual interface device into an interrupt routing table through the basic input output system; setting and obtaining the interrupt number of the virtual interface device according to the interrupt routing table through the operating system; and The interrupt event handler is installed by the operating system according to the interrupt number. 2. The method for installing an interrupt event handler according to claim 1, wherein the step of obtaining the interrupt number of the virtual interface device according to the interrupt routing table by the operating system comprises: The interrupt number of the virtual interface device is obtained according to the bus number, device number and interrupt pin number of the virtual interface device recorded in the interrupt routing table. 3. The method for installing an interrupt event handler according to claim 1, wherein the step of installing the interrupt event handler by the operating system according to the interrupt number includes: According to the interrupt number, the interrupt event handler is installed into the corresponding interrupt number field of the interrupt vector table through the operating system. 4. The method for installing an interrupt event handler according to claim 1, wherein said interrupt routing table includes an interrupt request routing table of a programmable interrupt controller, a multiprocessor specification configuration table, and an advanced configuration and power interface sheet. 5. The method for installing an interrupt event handler according to claim 1, further comprising: The BIOS reserves an interrupt request to the virtual interface device, and sets the interrupt request as a level trigger. 6. The method for installing an interrupt event handler as claimed in claim 1, wherein the MPI device will not be disabled.

Images