Chipset support for managing hardware interrupts in a virtual machine system

• US 7,302,511 B2
• Filed: 10/13/2005
• Issued: 11/27/2007
• Est. Priority Date: 09/30/2003
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Anderson, Andrew V., Neiger, Gilbert, Bennett, Steven M., Uhlig, Richard, Jeyasingh, Stalinselvaraj, Kagi, Alain, Cota-Robles, Erik
• Primary Examiner(s): Ray; Gopal C.
• Application Number:
  US11/251,282
• Publication Number:
  US 20060036791A1
• Time in Patent Office: 775 Days
• Field of Search: 710260-269, 710/200, 710/40, 710/48, 710/49, 712/224, 712/244, 718/1, 718/100, 718/103, 718/108, 711/6, 711/151, 711/203, 700/1
• US Class Current: 710/260
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked

Abstract

In one embodiment, an apparatus includes a set of multiplex blocks coupled with an interrupt controller and multiple interrupt request lines, and a virtual machine monitor block (VMM) coupled to the set of multiplex blocks. Each multiplex block corresponds to a distinct interrupt request line. Each multiplex block is to route the interrupt request signal received via the corresponding interrupt request line either to the interrupt controller or the VMM block depending on a current configuration value of this multiplex block.

Claims

1. A method comprising:

receiving, at a multiplex block, an interrupt request signal from a device via an interrupt request line coupled with the multiplex block; and

determining, based on a current configuration value of the multiplex block, whether the interrupt request signal is to be sent to an interrupt controller or a virtual machine monitor (VMM) block coupled to the multiplex block,

wherein the current configuration value of the multiplex block requires that the interrupt request signal be sent to the interrupt controller or the VMM block depending on whether the device is managed by a currently-operating virtual machine (VM) or is not managed by the currently-operating VM respectively.

2. The method of claim 1 further comprising determining whether the interrupt request signal sent to the VMM block is masked based on data stored in a mask register of the VMM block.

3. The method of claim 1 further comprising updating a corresponding indicator in a status register of the VMM block upon receiving the interrupt request signal at the VMM block.

4. The method of claim 1 further comprising:

determining that the interrupt request signal received at the VMM block is not masked;

asserting an internal signal;

combining the internal signal with an external signal generated by an external signal source; and

transmitting the combined signal to a processor.

5. The method of claim 4 wherein:

the external signal is a non-maskable interrupt (NMI) signal; and

the designated external signal source is a NMI source.

6. A method comprising:

identifying one or more interrupt request lines that are coupled to one or more devices managed by a virtual machine (VM);

configuring one or more multiplex blocks to route only interrupt request signals on the one or more interrupt request lines associated with the VM to an interrupt controller;

configuring one or more multiplex blocks to route interrupt request signals on interrupt request lines that are not managed by the VM to a vritual machine monitor (VMM) block; and

generating a request to transfer control to the VM.

7. The method of claim 6 further comprising:

configuring a mask register in the VMM block to cause blocking of interrupt request signals routed to the VMM block.

8. The method of claim 7 further comprising:

restoring a state saved during a previous operation of the VM in the interrupt controller.

9. A machine-readable medium containing instructions which, when executed by a processing system, cause the processing system to perform a method, the method comprising:

identifying one or more interrupt request lines that are coupled to one or more devices managed by a virtual machine (VM);

configuring one or more multiplex blocks to route only interrupt request signals on the one or more interrupt request lines associated with the VM to an interrupt controller;

configuring one or more multiplex blocks to route interrupt request signals on interrupt request lines that are not managed by the VM to a virtual machine monitor (VMM) block; and

generating a request to transfer control to the VM.

10. The machine-readable medium of claim 9 wherein the method further comprises:

configuring a mask register in the VMM block to cause masking/unmasking of interrupt request signals routed to the VMM block.

11. The machine-readable medium of claim 10 wherein the method further comprises:

restoring a state saved during a previous operation of the VM in the interrupt controller.

12. An apparatus comprising:

an interrupt controller;

a virtual machine monitor (VMM) block; and

a multiplex block, couplable with the interrupt controller and the VMM block, to receive an interrupt request signal from a device via an interrupt request line coupled with the multiplex block, and to determine, based on a current configuration value of the multiplex block, whether the interrupt request signal is to be sent to the interrupt controller or the VMM block,

wherein the current configuration value of the multiplex block requires that the interrupt request signal be sent to the interrupt controller or the VMM block depending on whether the device is managed by a currently-operating virtual machine (VM) or is not managed by the currently-operating VM respectively.

13. The apparatus of claim 12 wherein the VMM block comprises a mask register to store data indicating whether the interrupt request sent to the VMM block is masked.