WO2012053095A1 - Dispositif d'acceptation de signal d'interruption et dispositif informatique - Google Patents

Dispositif d'acceptation de signal d'interruption et dispositif informatique Download PDF

Info

Publication number
WO2012053095A1
WO2012053095A1 PCT/JP2010/068694 JP2010068694W WO2012053095A1 WO 2012053095 A1 WO2012053095 A1 WO 2012053095A1 JP 2010068694 W JP2010068694 W JP 2010068694W WO 2012053095 A1 WO2012053095 A1 WO 2012053095A1
Authority
WO
WIPO (PCT)
Prior art keywords
interrupt
interrupt signal
pseudo
operating
processing
Prior art date
Application number
PCT/JP2010/068694
Other languages
English (en)
Japanese (ja)
Inventor
寛隆 茂田井
智久 山口
Original Assignee
三菱電機株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機株式会社 filed Critical 三菱電機株式会社
Priority to US13/824,405 priority Critical patent/US9361251B2/en
Priority to JP2012539540A priority patent/JP5372262B2/ja
Priority to PCT/JP2010/068694 priority patent/WO2012053095A1/fr
Priority to DE112010005951T priority patent/DE112010005951T5/de
Priority to CN201080069758.0A priority patent/CN103180829B/zh
Priority to KR1020137008525A priority patent/KR101475640B1/ko
Publication of WO2012053095A1 publication Critical patent/WO2012053095A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24—Handling requests for interconnection or transfer for access to input/output bus using interrupt
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/24—Handling requests for interconnection or transfer for access to input/output bus using interrupt
    • G06F13/26—Handling requests for interconnection or transfer for access to input/output bus using interrupt with priority control
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4812—Task transfer initiation or dispatching by interrupt, e.g. masked
    • G06F9/4831—Task transfer initiation or dispatching by interrupt, e.g. masked with variable priority

Definitions

  • the present invention relates to an interrupt control technique in a multi-operating system environment.
  • one operating system operates, and the OS manages computer resources such as a computer processor, a main storage device (hereinafter simply referred to as main storage), a secondary storage device, and a device.
  • the schedule is made so that the computer can operate efficiently.
  • the OS has characteristics such as an OS having multiple functions and abundant assets such as Windows (registered trademark) and Linux (registered trademark), and a real-time OS specialized in a real-time processing function.
  • multi-operating system capable of operating a plurality of OSs as described above on one computer including a single or a plurality of processors.
  • the multi-OS is described in, for example, Patent Document 1, Patent Document 2, and Patent Document 3.
  • the OS that receives an interrupt request is determined for each interrupt number, and the OS is switched by determining the interrupt number of the generated interrupt (for example, the technique described in Patent Document 1.
  • peripheral devices are added. In this case, the interrupt signal of the computer is limited and cannot be easily added. For this reason, a plurality of peripheral devices often use one interrupt signal line in common, such as a peripheral device group connected to a PCI (Peripheral Component Interconnect) bus.
  • interrupts by a plurality of peripheral devices are collected by an interrupt management apparatus having fewer than the number of peripheral devices, and one interrupt signal line is used in common.
  • the PCI interrupt signal line (interrupt signal) is described in Non-Patent Document 1, for example.
  • the device since an OS that receives an interrupt signal is determined for each interrupt number, a plurality of peripheral devices that perform an interrupt with the same interrupt number (common interrupt number) must be controlled by the same OS. For this reason, there exists a subject that OS required for a device cannot be allocated. In order to solve this, as in the technique of Patent Document 2, the device has a device identification register that can identify the device that generated the interrupt, or the interrupt factor is confirmed in the peripheral device that is related to the OS processing separately. is required.
  • One of the main objects of the present invention is to solve the above-mentioned problems, and it does not have a device identification register. Further, separately from the OS processing, the related peripheral device can be checked for an interrupt factor. Rather, the main purpose is to assign an interrupt from a plurality of peripheral devices that perform an interrupt with a common interrupt number to an appropriate OS among the plurality of OSs.
  • the interrupt signal receiving device is: Manage the operation of two or more OSs (Operating Systems)
  • An interrupt signal receiving device for receiving interrupt signals from a plurality of devices, each of which is designated with an interrupt number to be notified by an interrupt signal, and an OS for processing the interrupt signal is designated as the designated OS, For each of two or more number sharing devices that share the same interrupt number, the designated OS of each number sharing device, a unique value unique to each number sharing device, and a sharing shared by the two or more number sharing devices
  • An OS unique value information storage unit for storing OS unique value information for associating an interrupt number; Conversion value information for storing conversion value information for designating a unique value selected from two or more unique values associated with the shared interrupt number in the OS unique value information as a conversion value of the shared interrupt number for each shared interrupt number A storage unit; When any OS is operating as the operating OS, an interrupt signal for notifying the shared interrupt number is output, and the converted value after the shared interrupt number notified by the interrupt signal is converted according to the converted value information Is the same as the
  • the number sharing device, the OS, and the unique value are associated with each other, and when the converted value converted from the interrupt number matches the unique value associated with the operating OS, the operating OS performs processing on the interrupt signal. If the converted value does not match the eigenvalue, the operating OS is switched. When the same interrupt number is continuously output to the device until the processing by the specified OS is performed on the interrupt signal, and when the converted value converted from the interrupt number matches the unique value associated with the operating OS By switching the conversion value to another unique value, even if multiple devices share the same interrupt number, the interrupt signal must be processed by the specified OS of the device that output the interrupt signal without checking the cause of the interrupt. Can be made.
  • FIG. 3 shows functional blocks of the interrupt signal reception device according to the first embodiment.
  • FIG. 3 is a diagram illustrating a hardware configuration example of the interrupt signal reception device according to the first embodiment.
  • FIG. 4 is a diagram showing an example of an interrupt processing management table according to the first embodiment.
  • FIG. 4 shows an example of a device interrupt number connection table according to the first embodiment.
  • FIG. 5 is a diagram showing an example of an interrupt number priority conversion table according to the first embodiment.
  • FIG. 4 is a diagram showing an example of a device priority management table according to the first embodiment.
  • FIG. 4 is a diagram showing an example of an interrupt use management table according to the first embodiment.
  • FIG. 3 is a flowchart showing a processing flow when an interrupt occurs according to the first embodiment.
  • FIG. 3 is a flowchart showing a processing flow when an interrupt occurs according to the first embodiment.
  • FIG. 4 is a flowchart showing a process flow of a common interrupt transmission process according to the first embodiment.
  • FIG. 3 is a flowchart showing a processing flow of common interrupt transmission processing to another OS according to the first embodiment.
  • FIG. 5 is a diagram illustrating functional blocks of an interrupt signal receiving device according to a second embodiment.
  • FIG. 4 is a diagram illustrating a hardware configuration example of an interrupt signal receiving device according to a second embodiment.
  • FIG. 10 is a diagram illustrating an example of an interrupt processing management table according to the second embodiment.
  • FIG. 10 is a diagram showing an example of an interrupt replication management table according to the second embodiment.
  • FIG. 9 is a flowchart showing a processing flow when an interrupt occurs according to the second embodiment.
  • FIG. 9 is a flowchart showing a processing flow of common interrupt replication processing according to the second embodiment.
  • FIG. 9 is a flowchart showing a processing flow when an interrupt occurs according to the second embodiment.
  • the figure which shows the hardware structural example of the computer apparatus in which the interrupt signal reception apparatus which concerns on Embodiment 1 and 2 is included.
  • Embodiment 1 FIG.
  • what is described as “to part”, “to means” and “to process” may be “to circuit” and “to device”, and “to step” and “to procedure”. It may be.
  • “ ⁇ unit”, “ ⁇ means”, and “ ⁇ processing” described below may be realized by software, firmware, hardware, or a combination thereof.
  • FIG. 1 shows functional blocks of an interrupt signal receiving apparatus 10 included in a multi-OS computer apparatus.
  • the interrupt signal receiving apparatus 10 manages the operations of two OSs, OS-A 150 and OS-B 151.
  • the interrupt signal receiving apparatus 10 is realized by a CPU (Central Processing Unit) 100 and a main memory 110 as shown in FIG. Details of the internal configuration of the interrupt signal receiving apparatus 10 will be described later.
  • the interrupt signal receiving apparatus 10 is connected to the interrupt controller 120 and a plurality of devices 130 to 133 via the bus 140, and receives interrupt signals from the devices 130 to 133.
  • the devices 130 to 133 are a keyboard, a mouse, a network interface, a printer interface, a USB (Universal Serial Bus) controller, and the like.
  • the devices 130 to 133 output an interrupt signal.
  • Each of the devices 130 to 133 is designated with an interrupt number to be notified by an interrupt signal.
  • the interrupt number of device A 130 is 16, the interrupt number of device B (1) 131 is 16, and device B (2)
  • the interrupt number of 132 is 21, and the interrupt number of device B (3) 133 is 22.
  • Each device outputs an interrupt signal notifying the value of the interrupt number specified for each device. Note that both the device A 130 and the device B (1) 131 have an interrupt number of 16, which is common.
  • a device having a common interrupt number is called a number sharing device.
  • An interrupt number shared by the number sharing device is called a shared interrupt number.
  • Each of the devices 130 to 133 is designated with an OS for processing an interrupt signal.
  • the device A 130 causes the OS-A 150 to process the interrupt signal, and the devices 131 to 133 cause the OS-B 151 to process the interrupt signal.
  • the interrupt number output as an interrupt signal from the device A 130 and the interrupt number output as an interrupt signal from the device B (1) 131 are the same, but need to be processed by different OSs.
  • An OS specified for each device is referred to as a specified OS.
  • the designated OS of the device A130 is OS-A15, and the designated OS of the devices 131 to 133 is OS-B151.
  • the devices 130 to 133 continuously output the same interrupt number as an interrupt signal until the interrupt signal is processed by the specified OS (until the interrupt signal is received by the specified OS). To do.
  • the interrupt controller 120 receives interrupt signals from the devices 130 to 133 via the bus 140. As described above, an interrupt signal for notifying an interrupt number is output from the devices 130 to 133, but the interrupt controller 120 converts the interrupt number into an interrupt priority and transmits it to the CPU 100. More specifically, the interrupt controller 120 outputs a signal notifying the interrupt priority to the CPU 100 as an interrupt signal.
  • the interrupt controller 120 refers to the interrupt number priority conversion table in FIG. 5 and converts the interrupt number into an interrupt priority.
  • the interrupt priority 20 is shown for the interrupt number 16 shared by the device A 130 and the device B (1) 131. However, as will be described later, for the interrupt priority 16, In addition to the interrupt priority 20, there is also an interrupt priority 100.
  • the interrupt priority 20 and the interrupt priority 100 are alternately set for the interrupt priority 16 (the interrupt priority is rewritten).
  • the interrupt priority is a conversion value of the interrupt number
  • the interrupt number priority conversion table of FIG. 5 is an example of conversion value information.
  • the devices 130 to 133 repeatedly generate an interrupt signal until the OS processing is performed on the interrupt signal, but the interrupt controller 120 sets an interrupt priority corresponding to the input of the interrupt signal from the devices 130 to 133. It outputs to the interrupt signal receiving apparatus 10 repeatedly. Further, in FIG. 1, there is only one interrupt controller 120, but there may be two or more interrupt controllers.
  • the interrupt signal control unit 11 and the interrupt priority value and the operating OS (OS-A150 or OS-B151) Based on the above, control for causing the operating OS to process the interrupt signal, control for rewriting the interrupt priority value in the interrupt number priority conversion table of FIG. 5, and control for switching the operating OS are performed.
  • the interrupt signal input unit 114 inputs an interrupt signal from the interrupt controller 120.
  • the interrupt signal control unit 11 and the interrupt signal input unit 114 are programs, which are loaded from the secondary storage device to the main memory 110 as shown in FIG.
  • the device interrupt number connection table storage unit 12 is a means for storing the device interrupt number connection table 195, and specifically is a part of the storage area of the main memory 110 as shown in FIG.
  • the device interrupt number connection table 195 is information shown in FIG. 4 and indicates interrupt numbers assigned to the devices for each device.
  • the device interrupt number connection table 195 corresponds to OS unique value information together with a device priority management table 197 described later, and the device interrupt number connection table storage unit 12 corresponds to OS unique value information storage unit together with the device priority management table storage unit 14. To do.
  • the interrupt number priority conversion table storage unit 13 is means for storing the interrupt number priority conversion table 196, and specifically, is a part of the storage area of the main memory 110 as shown in FIG.
  • the interrupt number priority conversion table 196 is information shown in FIG. 5 and is referred to when the interrupt controller 120 converts an interrupt number into an interrupt priority as described above.
  • the interrupt number priority conversion table 196 corresponds to conversion value information
  • the interrupt number priority conversion table storage unit 13 corresponds to a conversion value information storage unit.
  • the device priority management table storage unit 14 is a means for storing the device priority management table 197, and specifically is a part of the storage area of the main memory 110 as shown in FIG.
  • the device priority management table 197 is information shown in FIG. 6, and shows the interrupt priority, the devices 130 to 133, and the OS name that processes the interrupt signal.
  • the device priority management table 197 may be divided for each device used by each OS (for example, a table of device A for OS-A 150 and a table of devices B (1) to (3) for OS-B 151). As shown in FIG. 6, 20 is assigned to the device A 130 as the interrupt priority, and 100 is assigned to the device B (1) 131 as the interrupt priority. As shown in the device interrupt number connection table 195 of FIG.
  • the interrupt number 16 is commonly assigned to the device A 130 and the device B (1) 131 which are number sharing devices. Is different between the device A 130 and the device B (1) 131. That is, the interrupt priority 20 assigned to the device A 130 is a value unique to the device A 130 and is an example of a unique value. Similarly, the interrupt priority 100 assigned to the device B (1) 131 is a value unique to the device B (1) 131, and is an example of a unique value.
  • each number sharing device designation OS is assigned to each number sharing device (device A 130, device B (1) 131).
  • the device interrupt number connection table 195 in FIG. 5 and the device priority management table 197 in FIG. 6 have such characteristics and correspond to OS unique value information.
  • the device priority management table storage unit 14 corresponds to an OS eigenvalue information storage unit together with the device interrupt number connection table storage unit 12.
  • the device interrupt number connection table 195 and the device priority management table 197 may be one table.
  • the interrupt usage management table storage unit 15 is means for storing the interrupt usage management table 198, and specifically, is a part of the storage area of the main memory 110 as shown in FIG.
  • the interrupt usage management table 198 is information shown in FIG. 7, and is information indicating an interrupt number, a candidate OS that uses the interrupt number, and a currently used OS that uses the interrupt number.
  • the interrupt processing management table storage unit 16 is means for storing the interrupt processing management table A200 and the interrupt processing management table B201, and specifically, is a part of the storage area of the main memory 110 as shown in FIG.
  • the interrupt processing management table A200 and the interrupt processing management table B201 are information shown in FIG. 3, and one or more are prepared for each OS.
  • the interrupt processing management table A200 is a table for the OS-A 150
  • the interrupt processing management table B201 is a table for the OS-B 151.
  • the interrupt processing management table A200 is referred to when an interrupt signal is input while the OS-A 150 is operating
  • the interrupt processing management table B201 is referred to when an interrupt signal is input while the OS-B 151 is operating. .
  • the OS storage unit 17 is means for storing the OS-A 150 and the OS-B 151, and specifically, is a part of the storage area of the main memory 110 as shown in FIG. OS-A 150 and OS-B 151 may be duplicates of the same OS.
  • the OS-A 150 and OS-B 151 include a device driver 160, a device driver B161, an interrupt process A170, and an interrupt process B171. There may be a plurality of interrupt processes A170 and B171 for each OS.
  • the OS-A 150 and OS-B 151 each have a function included in a normal OS.
  • the program code read into the main memory 110 may be a part of each of the OS-A 150 and the OS-B 151.
  • the analysis unit 111 inputs an interrupt signal from the interrupt controller 120 via the interrupt signal input unit 114 and corresponds to the interrupt priority notified by the interrupt signal and is currently operating.
  • the processing for the interrupt signal is determined with reference to the interrupt processing management table (FIG. 3) corresponding to the OS. For example, when an interrupt signal is input while the OS-A 150 is operating and the interrupt priority notified by the input interrupt signal is 20, a record corresponding to the interrupt priority 20 in the interrupt processing management table A200
  • the OS-A 150 performs the interrupt processing A170 for the interrupt signal, and then changes the interrupt priority value for the interrupt number 16 in the device interrupt number connection table 195 of FIG. Interrupt transmission processing) is performed by the common interrupt transmission unit 113.
  • the OS switching unit 112 When an interrupt signal is input while the OS-A 150 is operating and the interrupt priority notified by the input interrupt signal is 100, a record corresponding to the interrupt priority 100 in the interrupt processing management table A200 , The OS switching unit 112 is caused to perform processing (OS switching processing) for switching the operating OS from OS-A 150 to OS-B 151.
  • processing OS switching processing
  • OS switching process a process for switching the operating OS from the OS-B 151 to the OS-A 150.
  • the OS switching unit 191 saves the context of the OS being executed (contents of various registers in the CPU 100), and writes back the context of the switching destination OS. Also, the interrupt processing management table is switched.
  • the common interrupt transmission unit 113 rewrites the interrupt priority in the interrupt number priority conversion table 196 in FIG.
  • the interrupt processing management table A 200 and the interrupt processing management table B 201 correspond to each of the OS-A 150 and OS-B 151, and the interrupt priority (corresponding to each OS in the device priority management table 197 ( Interrupt processing and common interrupt transmission processing (conversion value information update processing) are defined for (eigenvalue).
  • the analysis unit 111 reads the interrupt processing management table of the operating OS from the interrupt processing management table storage unit 16, and the interrupt number common interrupt number of the interrupt signal has priority over the interrupt number.
  • the same interrupt priority (unique value) as the interrupt priority (converted value) after being converted by the interrupt controller 120 according to the degree conversion table 196 is extracted from the interrupt processing management table of the operating OS.
  • the analysis unit 111 is the number sharing device in which the output source of the interrupt signal is the operating OS as the designated OS.
  • the operating OS is caused to execute an interrupt process for the interrupt signal.
  • the analysis unit 111 selects another interrupt priority associated with the shared interrupt number in the device priority management table 197 in the common interrupt transmission unit 113 as the common interrupt transmission process, and the selected interrupt priority is The interrupt number priority conversion table 196 is updated as specified.
  • the analysis unit 111 causes the OS switching unit 112 to stop the operating OS, and a new OS other than the operating OS is newly created. Start as an operating OS.
  • the interrupt processing A170 makes an inquiry to the device A130 as to whether it is the output source of the interrupt signal. If the output source of the interrupt signal is the device A130, the device driver A160 or the like executes processing for the interrupt signal. . Thereafter, the interrupt priority corresponding to the interrupt number 16 shown in the interrupt number priority conversion table 196 in FIG. In this case, since the interrupt signal is processed by the OS-A 150 that is the designated OS, the device A 130 does not repeatedly transmit the interrupt signal.
  • the interrupt processing A170 does not process the interrupt signal from the device B (1) 131, and thereafter, the interrupt shown in FIG.
  • the interrupt priority shown in the number priority conversion table 196 is changed to 100.
  • the device B (1) 131 since the interrupt signal is not processed by the designated OS, OS-B 151, the device B (1) 131 repeatedly transmits the interrupt signal.
  • the interrupt signal is converted into an interrupt signal with an interrupt priority of 100 by the interrupt controller 120, and the analysis unit 111 inputs an interrupt signal with an interrupt priority of 100. If the operating OS at this time is OS-B151, an interrupt process B171 is performed.
  • the interrupt processing B 171 inquires of the device B (1) 131 whether it is the output source of the interrupt signal. If the output source of the interrupt signal is the device B (1) 131, the device driver B 161, etc. Executes processing for the interrupt signal. After that, the interrupt priority shown in the interrupt number priority conversion table 196 in FIG. In this case, since the interrupt signal is processed by the OS-B 151 which is the designated OS, the device B (1) 131 does not repeatedly transmit the interrupt signal. On the other hand, if the operating OS at this time is OS-A 150, the operating OS is switched to OS-B 151 by the OS switching process. However, since the interrupt signal is not processed by the designated OS, OS-B 151, the device B (1) 131 repeatedly transmits the interrupt signal.
  • the interrupt signal is converted into an interrupt signal with an interrupt priority of 100 by the interrupt controller 120, and the analysis unit 111 inputs an interrupt signal with an interrupt priority of 100. Since the operating OS is OS-B 151 at this time, the interrupt signal from the device B (1) 131 is appropriately processed by the OS-B 151 in the interrupt processing B171. After that, the interrupt priority shown in the interrupt number priority conversion table 196 in FIG. In this case, since the interrupt signal is processed by the OS-B 151 which is the designated OS, the device B (1) 131 does not repeatedly transmit the interrupt signal.
  • the interrupt signal input unit 114 inputs the interrupt signal from the interrupt controller 120 via the bus 140.
  • the analysis unit 111 extracts a record corresponding to the interrupt priority from the interrupt processing management table A200 and the interrupt processing management table B201 that are currently set. Among the processes included in the extracted record, select an unexecuted process. It does not matter which process is selected with priority.
  • the description will be made assuming that the interrupt processing management table A200 is set (the operating OS is OS-A150) and the interrupt priority 20 is input.
  • the analysis unit 111 selects the interrupt process A170 from the interrupt priority 20 record in the interrupt process management table A200.
  • step S303 the analysis unit 111 determines whether the selected process is a common interrupt transmission process. If it is a common interrupt transmission process, the process proceeds to S304, and if it is different, the process proceeds to S305. In this example, since the selected process is the interrupt process A170, the process proceeds to S305.
  • the analysis unit 111 executes the selected process. In this example, the interrupt process A170 is executed. The interrupt process A170 accesses the device A130 and checks whether the device A130 is an interrupt factor. If the device A 130 is an interrupt factor, the device driver A 160 or the OS-A 150 is requested to process the interrupt signal from the device A 130.
  • the interrupt processing A170 notifies the OS-A 150 that the device A130 is not an interrupt factor if necessary.
  • the analysis unit 111 determines whether there is an unexecuted process among the processes according to the interrupt priority from the interrupt process management table that is currently set. If there is no processing, the interrupt processing is terminated. If there is a process, the process proceeds to S302. In this example, since there is a process, the process proceeds to S302.
  • the analysis unit 111 selects an unexecuted process.
  • the analysis unit 111 selects a common interrupt transmission process from the unexecuted processes in the currently set interrupt process management table A200.
  • the analysis unit 111 determines whether the selected process is a common interrupt transmission process. In this example, since it is a common interrupt transmission process, the process proceeds to S304.
  • the analysis unit 111 requests the common interrupt transmission unit 113 to perform a common interrupt transmission process. More specifically, the interrupt priority currently being processed is transmitted. In this example, the analysis unit 111 transmits the interrupt priority 20 to the common interrupt transmission unit 113 and requests a common interrupt transmission process.
  • the operation procedure of the common interrupt transmission unit 113 will be described with reference to FIG.
  • the common interrupt transmission unit 113 specifies the interrupt priority of the request source.
  • the interrupt processing management table A200 performs processing with an interrupt priority of 20, and the specified interrupt priority is 20.
  • the common interrupt transmission unit 113 identifies an interrupt number from the interrupt number priority conversion table 196 based on the identified interrupt priority. In this example, it is 16.
  • the common interrupt transmission unit 113 selects the OS to which the interrupt processing management table is assigned next from the candidate OS corresponding to the interrupt number from the interrupt use management table 198, and describes it in the use OS.
  • the OS selection criteria may be anything.
  • the OS-B 151 to which the interrupt processing management table is not assigned is selected from OS-A and OS-B, which are candidate OSs corresponding to the interrupt number 16, and described in the use OS.
  • the common interrupt transmission unit 113 uses the device interrupt number connection table 195 and the device priority management table 197, and among the devices sharing the interrupt number specified in S402, the device used by the OS selected in S403. To determine the interrupt priority.
  • the common interrupt transmission unit 113 changes the interrupt priority of the interrupt number priority conversion table 196 in FIG. In this example, the interrupt priority of interrupt number 16 is changed to 100.
  • an operation in which an interrupt signal is generated from the devices 130 to 133 and the interrupt signal is input to the CPU 100 via the interrupt controller 120 and then transmitted to another OS will be described with reference to FIG.
  • a processing example in the case where an interrupt signal from the device B (1) 131 is generated when the OS-A 150 is operating in the CPU 100 will be described in parentheses.
  • the interrupt controller 120 When the interrupt controller 120 receives an interrupt signal from the devices 130 to 133, in S451, the interrupt controller 120 refers to the device interrupt number connection table 196 in the main memory 110 and specifies the interrupt number of the generated interrupt (the interrupt controller 120 Number 16). Next, in S452, the interrupt controller 120 refers to the interrupt number priority conversion table 196 in the main memory 110, converts the interrupt number into an interrupt priority, and transmits the interrupt priority to the CPU 100 (the interrupt controller 120). Transmits the interrupt priority 20 to the CPU 100).
  • the CPU 100 executes the interrupt processing as described in S301 to S306.
  • the common interrupt transfer unit 113 When the common interrupt transfer unit 113 is called, the value of the interrupt number priority conversion table 196 is partially changed (after the interrupt process A170 is executed by the OS-A 150, the common interrupt transfer unit 113 changes the interrupt number The interrupt priority of the interrupt number 16 in the priority conversion table 196 is changed from 20 to 100).
  • the analysis unit 111 checks whether an interrupt is generated from the devices 130 to 133 (since the interrupt of the device B (1) 131 is active unless the interrupt processing B171 of the OS-B 151 is performed). Results in an interrupt being generated)
  • the analysis unit 111 ends the process.
  • the interrupt controller 120 specifies the interrupt number as 16.
  • the interrupt controller 120 transmits the interrupt priority 100 of the interrupt number 16 to the CPU 100 in order to refer to the interrupt number priority conversion table 196 changed in S453.
  • the OS switching unit 112 switches the operating OS to the OS-B 151 by the processes of S301 to S306, and the OS-B 151 executes the interrupt process B171.
  • the common interrupt transmission unit 113 returns the interrupt priority of the interrupt number 16 in the interrupt number priority conversion table 196 from 100 to 20. Since the interrupt process B171 has already been executed, an interrupt from the device B (1) 131 does not occur. Then, in S454, the analysis unit 111 checks whether an interrupt has occurred from the devices 130 to 133, finds that no interrupt has occurred, and ends the process in S455.
  • the priority of the external interrupt is changed. Since the interrupt is cleared if it is an external interrupt from the device A 130, no interrupt is input to the interrupt controller 120 again. If it is an external interrupt from the device B (1) 131, the interrupt remains set (the signal line remains active), so the interrupt is input again.
  • the analysis unit 111 refers to the interrupt number priority conversion table 196, and since the interrupt priority is changed to 100, the OS switching unit 191 is executed and switched to the OS-B 151.
  • the interrupt processing management table A200 is switched to the interrupt processing management table B201, so that the interrupt processing B171 with the interrupt priority 100 is executed.
  • the interrupt signal control unit compares the input interrupt priority with the interrupt priority associated with the operating OS, and if the two match, causes the operating OS to perform interrupt processing, and sets the interrupt number. Change the interrupt priority to convert. On the other hand, if the two do not match, the interrupt signal control unit switches the operating OS. Further, the device continues to output an interrupt signal having the same interrupt number until the interrupt signal is processed by the designated OS.
  • the interrupt signal control section can always process the interrupt signal with the designated OS of the device from which the interrupt signal is output in the interrupt signal at the third time at most. For this reason, even if the same interrupt number is shared by different OSs, the interrupt signal can always be processed by the designated OS of the device from which the interrupt signal is output without determining the cause of the interrupt. In addition, the response time of specific interrupt processing can be increased.
  • the record corresponding to the interrupt priority input on the interrupt processing management table of the operating OS is extracted and the processing indicated in the extracted record is performed.
  • the next process to be performed may be determined by referring to the device interrupt number connection table 195 and the device priority management table 197. That is, the interrupt signal control unit 11 corresponds to the operating OS in the device interrupt number connection table 195 and the device priority management table 197 (OS specific value information) as the interrupt priority (converted value) after the shared interrupt number is converted. When it is the same as the assigned interrupt priority (unique value), the operation OS is caused to execute interrupt processing for the interrupt signal. Furthermore, the interrupt signal control unit 11 describes another interrupt priority associated with the shared interrupt number in the device priority management table 197 in the interrupt number priority conversion table 196.
  • the interrupt signal control unit 11 indicates that the interrupt priority (converted value) after the shared interrupt number is converted is other than the operating OS in the device interrupt number connection table 195 and the device priority management table 197 (OS specific value information).
  • the interrupt priority (unique value) associated with the OS is the same, the operating OS is stopped and an OS other than the operating OS is started as a new operating OS.
  • the device interrupt number connection table 195 and the device priority management table 197 may be used without using the interrupt processing management table.
  • Embodiment 2 FIG. In the first embodiment, the interrupt priority of the interrupt number priority conversion table 196 is changed. Next, the interrupt number is changed between the OSs without changing the interrupt number priority conversion table 196. An embodiment to be shared is shown.
  • FIG. 11 shows functional blocks of the interrupt signal receiving apparatus 10 included in the multi-OS computer apparatus, and corresponds to FIG.
  • FIG. 12 shows an example in which the interrupt signal receiving apparatus 10 shown in FIG. 11 is realized by the CPU 100 and the main memory 110, and corresponds to FIG. 11 and 12, a common interrupt duplication unit 115 is provided instead of the common interrupt transmission unit 113 shown in FIGS. 1 and 2.
  • an interrupt replication management table storage unit 18 is provided in place of the interrupt usage management table storage unit 15 shown in FIGS. 11 and 12, and an interrupt replication management table 199 is provided in place of the interrupt usage management table 198.
  • the contents are different from the interrupt processing management table A200 and the interrupt processing management table B201 shown in FIGS. 1 and 2, in FIG. 11 and FIG.
  • FIG. 12 shows the interrupt processing management table A600 and the interrupt processing management table B601. ing. Since the other elements are the same as those shown in FIGS. 1 and 2, the description thereof is omitted. Below, it demonstrates centering on the difference with Embodiment 1.
  • FIG. 12 demonstrates centering on the difference with Embodiment 1.
  • the interrupt replication management table storage unit 18 is means for storing the interrupt replication management table 199, and specifically is a part of the storage area of the main memory 110 as shown in FIG.
  • the interrupt duplication management table 199 is information shown in FIG. 14, and includes an interrupt number, an interrupt priority candidate (priority candidate) related to the interrupt number, and a duplicated priority for which duplication processing has been completed among the interrupt priorities. Record the degree.
  • the interrupt processing management table A600 and the interrupt processing management table B601 are information shown in FIG. As with the interrupt processing management table A200 and the interrupt processing management table B201, one or more interrupt processing management tables A600 and interrupt processing management tables B601 are provided for each OS. When the OS is switched, an interrupt processing management table of the OS that operates next is set in the CPU 100. In the interrupt process management table A600 and the interrupt process management table B601, a common interrupt duplication process (a pseudo interrupt signal generation process) is defined instead of the common interrupt transmission process of the interrupt process management table A200 and the interrupt process management table B201.
  • a common interrupt duplication process (a pseudo interrupt signal generation process) is defined instead of the common interrupt transmission process of the interrupt process management table A200 and the interrupt process management table B201.
  • the interrupt process management table A 600 and the interrupt process management table B 601 are the same as the interrupt process management table A 200 and the interrupt process management table B 201 except that a common interrupt duplication process is defined instead of the common interrupt transmission process.
  • the interrupt processing management table A600, the interrupt processing management table B601, and the common interrupt replication unit 115 will be described focusing on the common interrupt replication processing.
  • the common interrupt duplication unit 115 performs the device interrupt number connection table 195 and the device priority management. In the table 197, another interrupt priority associated with the shared interrupt number is selected. Furthermore, the common interrupt duplication unit 115 generates an interrupt signal notifying the selected interrupt priority as a pseudo interrupt signal.
  • the pseudo interrupt signal is not an interrupt signal actually output from the devices 130 to 133 but a simulated interrupt signal generated in the interrupt signal control unit 11.
  • the interrupt priority notified by the pseudo interrupt signal is an example of a pseudo conversion value.
  • the analysis unit 111 when interrupt priority 20 is output as an interrupt signal by the interrupt controller 120 for interrupt number 16, and the operating OS at that time is OS-A150, the analysis unit 111 performs interrupt priority in the interrupt processing management table A600. The 20th degree record is extracted, and the interrupt processing A is executed by the OS-A 150 according to the extracted record. Thereafter, the analysis unit 111 causes the common interrupt replication unit 115 to execute a common interrupt replication process. In the common interrupt duplication processing, the common interrupt duplication unit 115 generates an interrupt signal notifying an interrupt priority 100 that is another interrupt priority of the interrupt number 16 as a pseudo interrupt signal. The pseudo interrupt signal does not need to be output to the bus 140, and the common interrupt duplicating unit 115 may notify the interrupt signal input unit 114 of the interrupt priority 100.
  • the common interrupt duplicating unit 115 continuously generates a pseudo interrupt signal until the processing for the pseudo interrupt signal is performed by the OS. Further, when generating the pseudo interrupt signal, the common interrupt duplicating unit 115 masks the interrupt signal of the interrupt number targeted by the pseudo interrupt signal (stops accepting the interrupt signal). That is, the common interrupt replication unit 115 stops accepting the interrupt request with the interrupt number 16.
  • a pseudo interrupt signal (a signal indicating interrupt priority 100) by the common interrupt duplicating unit 115 is input by the interrupt signal input unit 114.
  • the analysis unit 111 extracts the interrupt priority 100 record in the interrupt processing management table A600, and causes the OS switching unit 112 to switch the operating OS to OS-B 151 according to the extracted record.
  • the analysis unit 111 extracts the interrupt priority 100 record in the interrupt processing management table B601, and performs the interrupt processing B on the OS-B 151 according to the extracted record.
  • the common interrupt duplication unit 115 to perform common interrupt duplication processing.
  • the common interrupt duplicating unit 115 cancels the mask for the interrupt signal and resumes accepting the interrupt signal of the interrupt number 16.
  • the interrupt duplication unit 115 may notify the interrupt controller 120 of the interrupt priority notified by the pseudo interrupt signal, and may instruct the interrupt controller 120 to output the pseudo interrupt signal. Also in this case, the interrupt controller 120 continuously outputs the pseudo interrupt signal having the same interrupt priority until the process by the OS is performed on the pseudo interrupt signal.
  • S701 is the same as S301
  • S702 is the same as S302
  • S705 is the same as S305
  • S706 is the same as S306.
  • the analysis unit 111 moves the process to S704.
  • the process proceeds to S705.
  • it is assumed that the selected process is a common interrupt replication process, and the process proceeds to S704.
  • step S ⁇ b> 704 the analysis unit 111 requests the common interrupt duplication unit 115 to perform common interrupt duplication processing.
  • the analysis unit 111 transmits the interrupt priority currently being processed to the common interrupt duplication unit 115 and requests common interrupt duplication processing.
  • the interrupt priority 20 is transmitted.
  • step S801 the common interrupt duplicating unit 115 specifies the interrupt priority of the request source.
  • the process shown in the interrupt priority 20 record of the interrupt processing management table A600 is performed, and the specified interrupt priority is 20.
  • the common interrupt duplication unit 115 searches for a priority candidate sharing the same interrupt number from the interrupt duplication management table 199 based on the identified interrupt priority, and compares it with the identified interrupt priority. In this example, since the interrupt priority is 20, it is the highest priority among the interrupt priorities 20 and 100.
  • the interrupt priority 100 assigned to the interrupt number 16 is extracted together with the interrupt priority 20, but this is because the device interrupt number connection table 195 and the device This is equivalent to referring to the priority management table 197 and extracting the interrupt priority 100 assigned to the interrupt number 16 together with the interrupt priority 20. Therefore, instead of referring to the interrupt replication management table 199, the interrupt priority 100 may be derived by referring to the device interrupt number connection table 195 and the device priority management table 197.
  • the common interrupt replication unit 115 moves the process to S804.
  • the common interrupt replication unit 115 identifies an interrupt number from the interrupt replication management table 199 based on the interrupt priority identified in S801, and masks the external interrupt of that interrupt number.
  • the external interrupt mask may use a function provided in the CPU 100 or a function provided in the interrupt controller 120.
  • the common interrupt replication unit 115 searches for priority candidates sharing the same interrupt number from the interrupt replication management table 199 based on the specified interrupt priority, and generates a pseudo interrupt signal for notifying these priority candidates.
  • the generated pseudo interrupt signal is input through the interrupt signal input unit 114. For example, when there are three interrupt priorities of 20, 50, and 100 with respect to the interrupt number 16, the common interrupt duplicating unit 115 transmits a pseudo interrupt signal that notifies the interrupt priority 50 and a pseudo interrupt signal that notifies the interrupt priority 100. Generate an interrupt signal.
  • the common interrupt duplicating unit 115 inputs only the pseudo interrupt signal that notifies the interrupt priority 50 having a high priority to the interrupt signal input unit 114, and the OS responds to the pseudo interrupt signal that notifies the interrupt priority 50 by the OS. After the interrupt processing is performed, a pseudo interrupt signal for notifying the interrupt priority 100 is input to the interrupt signal input unit 114. Further, as described above, instead of the method of generating the pseudo interrupt signal by the common interrupt replicating unit 115, the common interrupt replicating unit 115 instructs the interrupt controller 120 to generate the pseudo interrupt signal, and the pseudo interrupt from the interrupt controller 120 is generated. The signal may be input to the interrupt signal input unit 114.
  • the common interrupt duplication unit 115 generates a pseudo interrupt signal for notifying the interrupt priority 100 and inputs the pseudo interrupt signal to the interrupt signal input unit 114 will be described.
  • the pseudo interrupt signal input to the interrupt signal input unit 114 is subjected to the processing of S701 to S706 in FIG. 15 as in the case of a normal interrupt signal. Then, when the pseudo interrupt signal becomes the target of the common interrupt duplication process (YES in S703), the process of FIG. 16 is executed on the pseudo interrupt signal.
  • the common interrupt replication process is executed for the pseudo interrupt signal that notifies the interrupt priority 100, and the common interrupt replication unit 115 specifies the interrupt priority 100 (S801) and refers to the interrupt replication management table 199.
  • the processing after comparison with other interrupt priorities assigned to the same interrupt number (S802) will be described. If it is determined in S805 that the priority is the lowest as a result of the comparison in S802 (NO in S803, YES in S805), the common interrupt duplicating unit 115 moves the process to S807. If the priority is not low, the common interrupt replication unit 115 ends the common interrupt replication process.
  • step S807 an interrupt number is specified from the interrupt replication management table 199 based on the interrupt priority specified in step S801, and the external interrupt mask for the interrupt number is canceled.
  • the external interrupt mask of interrupt number 16 is canceled.
  • an operation in which an interrupt signal is generated from the devices 130 to 133 and the interrupt signal is input to the CPU 100 via the interrupt controller 120 and then transmitted to another OS will be described with reference to FIG.
  • a processing example in the case where an interrupt signal from the device B (1) 131 is generated when the OS-A 150 is operating in the CPU 100 will be described in parentheses.
  • the interrupt controller 120 When the interrupt controller 120 receives an interrupt signal from the devices 130 to 133, in S901, the interrupt controller 120 refers to the device interrupt number connection table 195 in the main memory 110 and identifies the interrupt number of the generated interrupt (the interrupt controller 120 Number 16). Next, in S902, the interrupt controller 120 refers to the interrupt number priority conversion table 196 in the main memory 110, converts the interrupt number into an interrupt priority, and transmits the interrupt priority to the CPU 100 (interrupt controller 120). Transmits the interrupt priority 20 to the CPU 100).
  • the CPU 100 executes interrupt processing as described in S701 to 706.
  • the common interrupt replication unit 115 is called, as described above, the external interrupt of the interrupt number is masked by the common interrupt replication unit 115, and a pseudo interrupt notifying other priority candidates is input to the interrupt signal input unit 114.
  • the interrupt signal of interrupt number 16 is masked, and a pseudo interrupt signal of interrupt priority 100 is generated by the common interrupt duplicator 115 and input to the interrupt signal input unit 114.
  • the interrupt priority previously input is The degree 20 is processed in the interrupt processing A170).
  • the analysis unit 111 checks whether another interrupt priority is input to the interrupt signal input unit 114 (in this example, the pseudo interrupt signal with the interrupt priority 100 added in S903 is input).
  • the OS switching unit 112 switches the operating OS to OS-B151 by the processing of S701 to S706, and the interrupt processing B171 is executed by the OS-B151. Further, in the process of S704 after the interrupt process B171 is executed, the common interrupt replication unit 115 determines that the interrupt priority 100 is the lowest priority (YES in S805), and as a result, the interrupt mask of the interrupt number 16 is obtained. To clear. By clearing the interrupt mask of interrupt number 16, when an interrupt signal of interrupt number 16 is generated again, an interrupt signal of interrupt priority 20 is input to the CPU 100. In S904, the analysis unit 111 checks whether another interrupt priority is input to the interrupt signal input unit 114, finds that no other interrupt priority is input, and ends the process in S905.
  • the common interrupt replication unit 115 generates a pseudo interrupt signal with another interrupt priority in S806.
  • the interrupt controller 120 generates another interrupt priority (in this example, the interrupt priority). 100) may be input to the interrupt signal input unit 114.
  • input of a plurality of interrupt priorities by the common interrupt duplicating unit 115 in S806 is omitted.
  • the analysis unit 111 performs an interrupt.
  • a record of interrupt priority 20 in the process management table A600 is extracted, and the OS-A 150 is caused to execute interrupt process A according to the extracted record.
  • the analysis unit 111 causes the common interrupt replication unit 115 to execute a common interrupt replication process.
  • the common interrupt duplication unit 115 generates an interrupt priority 100 that is another interrupt priority of the interrupt number 16 as a pseudo interrupt signal.
  • the analysis unit 111 extracts the record of the interrupt priority 100 in the interrupt processing management table A600, and causes the OS switching unit 112 to switch the operating OS to OS-B 151 according to the extracted record.
  • the analysis unit 111 extracts a record of interrupt priority 100 in the interrupt processing management table B601, and in accordance with the extracted record, the OS -Causes B151 to execute interrupt processing B. Therefore, the interrupt signal is processed by the designated OS regardless of whether the output source of the interrupt signal with the interrupt number 16 is the device A 130 or the device B (1) 131.
  • the analysis unit 111 causes the common interrupt replication unit 115 to perform common interrupt replication processing. In this common interrupt duplication processing, the common interrupt duplication unit 115 cancels the mask for the interrupt signal with the interrupt number 16 and resumes accepting the interrupt signal with the interrupt number 16.
  • FIG. 18 is a diagram illustrating an example of hardware resources of the computer apparatus 1 including the interrupt signal receiving apparatus 10 described in the first and second embodiments. 18 is merely an example of the hardware configuration of the computer apparatus 1, and the hardware configuration of the computer apparatus 1 is not limited to the configuration illustrated in FIG. 18, but may be other configurations. .
  • the computer apparatus 1 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program.
  • the CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
  • the CPU 911 is connected to the interrupt controller 907.
  • the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), and a printer device 906.
  • FDD 904 Flexible Disk Drive
  • CDD compact disk device
  • printer device 906 a storage device such as an SSD (Solid State Drive), an optical disk device, or a memory card (registered trademark) read / write device may be used.
  • the RAM 914 is an example of a volatile memory.
  • the storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
  • the CPU 911 corresponds to the CPU 100 described in the first and second embodiments
  • the RAM 914 corresponds to the main memory 110 described in the first and second embodiments.
  • the interrupt controller 907 corresponds to the interrupt controller 120 described in the first and second embodiments.
  • Other hardware resources correspond to the devices 130 to 133 described in the first and second embodiments.
  • a communication board 915, a keyboard 902, a mouse 903, an interrupt controller 907, an FDD 904, and the like are examples of input devices.
  • the communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.
  • the communication board 915 may be connected to, for example, a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), or the like.
  • a LAN local area network
  • the Internet a wide area network
  • a SAN storage area network
  • the magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
  • OS operating system
  • the programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.
  • the program group 923 includes programs that implement the functions of the internal elements of the interrupt signal control unit 11 and the interrupt signal input unit 114 in the first and second embodiments. These programs are loaded into the RAM 914 and executed by the CPU 911. Is done.
  • the RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
  • the RAM 914 stores various data necessary for processing by the CPU 911.
  • the ROM 913 stores a BIOS (Basic Input Output System) program
  • the magnetic disk device 920 stores a boot program.
  • BIOS Basic Input Output System
  • the BIOS program in the ROM 913 and the boot program in the magnetic disk apparatus 920 are executed, and the operating system 921 is activated by the BIOS program and the boot program.
  • the read information, data, signal value, variable value, and parameter are used for CPU operations such as extraction, search, reference, comparison, calculation, calculation, processing, editing, output, printing, and display.
  • Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
  • the arrows in the flowcharts described in the first and second embodiments mainly indicate input / output of data and signals.
  • Data and signal values are recorded on a recording medium such as a memory of the RAM 914, a flexible disk of the FDD 904, a compact disk of the CDD 905, a magnetic disk of the magnetic disk device 920, other optical disks, a mini disk, and a DVD.
  • Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.
  • the operation of the interrupt signal receiving apparatus 10 shown in the first and second embodiments can be grasped as a method by the steps, procedures, and processes shown in the flowcharts described in the first and second embodiments.
  • firmware stored in the ROM 913.
  • it may be implemented only by software, only by hardware such as elements, devices, substrates, wiring, etc., by a combination of software and hardware, or by a combination of firmware.
  • Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD.
  • the program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer apparatus 1 to function as the “ ⁇ unit” in the first and second embodiments. Alternatively, the computer apparatus 1 is caused to execute the procedures and methods of “units” in the first and second embodiments.

Abstract

Un dispositif d'acceptation de signal d'interruption (10) commande deux OS, associe un OS qui amène des dispositifs (130) et (131) partageant le même numéro d'interruption à exécuter un traitement d'interruption avec une priorité d'interruption inhérente au dispositif, et commande une table de conversion de priorité de numéro d'interruption montrant l'association entre le numéro d'interruption et la priorité d'interruption. Chaque dispositif émet de façon continue une requête d'interruption ayant le même numéro d'interruption jusqu'à ce que le traitement d'interruption soit terminé. Un contrôleur d'interruption (120) convertit le numéro d'interruption en la priorité d'interruption selon la table de conversion de priorité de numéro d'interruption lorsqu'un signal d'interruption est reçu à partir du dispositif (130) ou du dispositif (131). Une unité de commande de signal d'interruption (11) amène un OS en service à exécuter un traitement d'interruption pour changer la priorité d'interruption de la table de conversion de priorité de numéro d'interruption lorsque la priorité d'interruption convertie correspond à une priorité d'interruption associée à l'OS en service. L'unité de commande de signal d'interruption (11) arrête l'OS en service et active d'autres OS lorsque la priorité d'interruption ne correspond pas.
PCT/JP2010/068694 2010-10-22 2010-10-22 Dispositif d'acceptation de signal d'interruption et dispositif informatique WO2012053095A1 (fr)

Priority Applications (6)

Application Number Priority Date Filing Date Title
US13/824,405 US9361251B2 (en) 2010-10-22 2010-10-22 Interrupt signal accepting apparatus and computer apparatus managing operations of at least two operating systems
JP2012539540A JP5372262B2 (ja) 2010-10-22 2010-10-22 割込み信号受付け装置及びコンピュータ装置
PCT/JP2010/068694 WO2012053095A1 (fr) 2010-10-22 2010-10-22 Dispositif d'acceptation de signal d'interruption et dispositif informatique
DE112010005951T DE112010005951T5 (de) 2010-10-22 2010-10-22 Unterbrechungssignal-Annahmevorrichtung und Computervorrichtung
CN201080069758.0A CN103180829B (zh) 2010-10-22 2010-10-22 中断信号接收装置及计算机装置
KR1020137008525A KR101475640B1 (ko) 2010-10-22 2010-10-22 인터럽트 신호 접수 장치 및 컴퓨터 장치

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2010/068694 WO2012053095A1 (fr) 2010-10-22 2010-10-22 Dispositif d'acceptation de signal d'interruption et dispositif informatique

Publications (1)

Publication Number Publication Date
WO2012053095A1 true WO2012053095A1 (fr) 2012-04-26

Family

ID=45974831

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/068694 WO2012053095A1 (fr) 2010-10-22 2010-10-22 Dispositif d'acceptation de signal d'interruption et dispositif informatique

Country Status (6)

Country Link
US (1) US9361251B2 (fr)
JP (1) JP5372262B2 (fr)
KR (1) KR101475640B1 (fr)
CN (1) CN103180829B (fr)
DE (1) DE112010005951T5 (fr)
WO (1) WO2012053095A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020021745A1 (fr) * 2018-07-24 2020-01-30 三菱電機株式会社 Procédé de traitement d'interruption, système informatique, et produit programme

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140079137A (ko) * 2012-12-18 2014-06-26 삼성전자주식회사 불휘발성 메모리를 메인 메모리로 사용하는 컴퓨팅 시스템 및 그것의 데이터 관리 방법
US9678903B1 (en) 2014-10-15 2017-06-13 Intel Corporation Systems and methods for managing inter-CPU interrupts between multiple CPUs
CN105786607B (zh) * 2016-03-24 2019-11-12 宇龙计算机通信科技(深圳)有限公司 一种多系统的冻结与唤醒方法及装置
KR20180083688A (ko) * 2017-01-13 2018-07-23 삼성전자주식회사 애플리케이션 프로세서 및 집적 회로
CN112711549B (zh) * 2021-01-15 2023-08-01 飞腾信息技术有限公司 中断请求信号转换系统和方法、计算装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0540643A (ja) * 1991-08-06 1993-02-19 Nec Corp 複数ｏｓ同時動作時のｈ／ｗ割込み制御方式
JP2000330806A (ja) * 1999-05-21 2000-11-30 Hitachi Ltd 計算機システム
JP2001229038A (ja) * 2000-02-17 2001-08-24 Hitachi Ltd マルチオペレーテング計算機システム

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS61229129A (ja) 1985-04-04 1986-10-13 Nec Corp 仮想計算機システムにおける入出力割込み通知装置
JP4026667B2 (ja) 1997-09-12 2007-12-26 株式会社日立製作所 マルチｏｓ構成方法
JP3546678B2 (ja) 1997-09-12 2004-07-28 株式会社日立製作所 マルチｏｓ構成方法
US6715016B1 (en) * 2000-06-01 2004-03-30 Hitachi, Ltd. Multiple operating system control method
US6785893B2 (en) * 2000-11-30 2004-08-31 Microsoft Corporation Operating system event tracker having separate storage for interrupt and non-interrupt events and flushing the third memory when timeout and memory full occur
US8612992B2 (en) * 2003-04-09 2013-12-17 Jaluna Sa Operating systems
ATE409904T1 (de) * 2003-04-09 2008-10-15 Jaluna Sa Betriebssysteme
JP4523910B2 (ja) 2005-12-13 2010-08-11 三菱電機株式会社 並列処理装置及び並列処理方法及び並列処理プログラム
JP2007206955A (ja) * 2006-02-01 2007-08-16 Sony Corp 情報処理装置および方法、プログラム、並びに記録媒体
JP5014179B2 (ja) 2008-01-25 2012-08-29 三菱電機株式会社 Ｏｓ優先度変更装置及びｏｓ優先度変更プログラム
US7793025B2 (en) * 2008-03-28 2010-09-07 Freescale Semiconductor, Inc. Hardware managed context sensitive interrupt priority level control
US8291135B2 (en) * 2010-01-15 2012-10-16 Vmware, Inc. Guest/hypervisor interrupt coalescing for storage adapter virtual function in guest passthrough mode
US8417862B2 (en) * 2010-10-13 2013-04-09 Lsi Corporation Inter-virtual machine interrupt coalescing

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0540643A (ja) * 1991-08-06 1993-02-19 Nec Corp 複数ｏｓ同時動作時のｈ／ｗ割込み制御方式
JP2000330806A (ja) * 1999-05-21 2000-11-30 Hitachi Ltd 計算機システム
JP2001229038A (ja) * 2000-02-17 2001-08-24 Hitachi Ltd マルチオペレーテング計算機システム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020021745A1 (fr) * 2018-07-24 2020-01-30 三菱電機株式会社 Procédé de traitement d'interruption, système informatique, et produit programme
US11687366B2 (en) 2018-07-24 2023-06-27 Mitsubishi Electric Corporation Interrupt handling method, computer system, and non-transitory storage medium that resumes waiting threads in response to interrupt signals from I/O devices

Also Published As

Publication number Publication date
CN103180829A (zh) 2013-06-26
US9361251B2 (en) 2016-06-07
JP5372262B2 (ja) 2013-12-18
CN103180829B (zh) 2016-08-03
DE112010005951T5 (de) 2013-07-25
KR101475640B1 (ko) 2014-12-22
JPWO2012053095A1 (ja) 2014-02-24
US20130185469A1 (en) 2013-07-18
KR20130052010A (ko) 2013-05-21

Similar Documents

Publication Publication Date Title
JP5372262B2 (ja) 割込み信号受付け装置及びコンピュータ装置
US7373469B2 (en) Data migration method
US7275249B1 (en) Dynamically generating masks for thread scheduling in a multiprocessor system
JP6284130B2 (ja) ローカル・クリア制御
US20070094456A1 (en) Storage system and storage control method
GB2366048A (en) Selecting a preferred path to a storage device
JP2015527632A (ja) 動的アドレス変換テーブルを管理する方法、システムおよびコンピュータ・プログラム
KR20010006887A (ko) 컴퓨터 시스템
WO2008068132A1 (fr) Système et procédé pour migrer des domaines d'un système de traitement de données physiques à un autre
JP2002117002A (ja) 共用型ペリフェラルアーキテクチャ
US20120144146A1 (en) Memory management using both full hardware compression and hardware-assisted software compression
US9665424B2 (en) Recovery improvement for quiesced systems
US20040073777A1 (en) System and method for utilizing a scoreboard to indicate information pertaining to pending register writes
US20150269098A1 (en) Information processing apparatus, information processing method, storage, storage control method, and storage medium
JP5182162B2 (ja) 計算機システム及びｉ／ｏ制御方法
JP2016134041A (ja) 情報処理システム、情報処理装置、メモリアクセス制御方法
JP6716645B2 (ja) ハードウェア内で変換索引バッファ（ｔｌｂ）シュートダウンを指示および追跡するための方法およびシステム、並びに非一時的なコンピュータ可読媒体
US10162530B2 (en) Computer and computer system for collision determination of a command identifier
WO2011039887A1 (fr) Dispositif informatique
JP2005128781A (ja) 系切り替え方法及び情報処理システム
JP2005209055A (ja) ストレージの負荷分散方法
JP5881852B2 (ja) 仮想計算機システム
JP5478372B2 (ja) ゲストｏｓ制御システム
JP2005339079A (ja) データベース管理システムにおける処理代行方法
US10936194B2 (en) Storage device status management for conflict avoidance in a data storage system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10858650

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012539540

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 13824405

Country of ref document: US

ENP Entry into the national phase

Ref document number: 20137008525

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 112010005951

Country of ref document: DE

Ref document number: 1120100059519

Country of ref document: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10858650

Country of ref document: EP

Kind code of ref document: A1