Control over faults occurring during the operation of guest software in the virtual-machine architecture

• US 7,124,327 B2
• Filed: 06/29/2002
• Issued: 10/17/2006
• Est. Priority Date: 06/29/2002
• Status: Expired due to Term

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Intel Corporation
• Inventors: Anderson, Andrew V., Jeyasingh, Stalinselvaraj, Kagi, Alain, Neiger, Gilbert, Uhlig, Richard, Zou, Xiang, Kozuch, Michael A., Bennett, Steve
• Primary Examiner(s): Bonzo, Bryce P.
• Assistant Examiner(s): Wilson, Yolanda L.
• Application Number:
  US10/184,774
• Publication Number:
  US 20040003323A1
• Time in Patent Office: 1,571 Days
• Field of Search: 714/47, 714/48, 714/38
• US Class Current: 714/38.13
• CPC Class Codes: G06F 11/0712 in a virtual computing platform, e.g. logically partitioned systems
• CPC Class Codes: G06F 11/0775 Content or structure details of the error report, e.g. specific table structure, specific error fields
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects

Abstract

In one embodiment, fault information relating to a fault associated with the operation of guest software is received. Further, a determination is made as to whether the fault information satisfies one or more filtering criterion. If the determination is positive, control remains with the guest software and is not transferred to the virtual machine monitor (VMM).

Claims

1. A method comprising:

receiving fault information relating to a fault associated with an operation of guest software, the fault information comprising at least one of a fault identifier, an error code associated with the fault, and one or more additional data values associated with the fault;

determining whether the fault information satisfies at least one filtering criterion;

refraining from transitioning control to a virtual machine monitor (VMM) if the fault information satisfies the at least one filtering criterion; and

transitioning control to the VMM if the fault information does not satisfy the at least one filtering criterion.

2. The method of claim 1 wherein:

the at least one filtering criterion is at least one control transfer filtering criterion; and

refraining from transitioning control to the VMM further comprises delivering the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

3. The method of claim 1 wherein the fault represents any one of an interrupt, an exception, and a platform event.

4. The method of claim 1 wherein the fault information includes a number of values, each of the number of values being indicative of an occurrence of a particular condition.

5. The method of claim 4 wherein one or more combinations of values of the fault information require a transition to the VMM.

6. The method of claim 1 wherein the at least one filtering criterion is defined using data stored in one or more designated fields.

7. The method of claim 6 wherein the one or more designated fields include a match field and a mask field.

8. The method of claim 6 wherein determining whether the fault information satisfies the at least one filtering criterion comprises combining the fault information with the data stored in one or more designated fields using one or more Boolean logic operations.

9. A method comprising:

determining whether a fault associated with an operation of guest software requires a transition of control to a virtual machine monitor (VMM) using fault information relating to the fault and at least one control transfer filtering criterion, wherein the at least one control transfer filtering criterion is defined using data stored in one or more designated fields, the one or more designated fields comprising a match field and a mask field; and

delivering the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

10. The method of claim 9 wherein the fault information is at least one of a fault identifier, an error code associated with the fault and one or more additional data values associated with the fault.

11. The method of claim 9 wherein the fault represents any one of an interrupt, an exception, and a platform event.

12. The method of claim 9 wherein determining whether the fault associated with the operation of the guest software requires a transition of control to the VMM comprises:

combining the fault information with data stored in the mask field using a bitwise AND operator; and

determining whether the result of the combination matches the data stored in the match field.

13. The method of claim 12 wherein determining whether the fault associated with the operation of the guest software requires a transition of control to the VMM further comprises:

determining that the result of the combination matches the data stored in the match field; and

identifying a value of a corresponding bit in a redirection map, the value of the corresponding bit indicating whether the fault requires a transition of control to the VMM.

14. The method of claim 12 wherein determining whether the fault associated with the operation of the guest software requires a transition of control to the VMM further compnses:

determining that the result of the combination does not match the data stored in the match field;

identifying a value of a corresponding bit in a redirection map; and

inverting the value of the corresponding bit, the inverted value of the corresponding bit indicating whether the fault requires a transition of control to the VMM.

16. The system of claim 12 wherein:

the at least one filtering criterion is at least one control transfer filtering criterion; and

the processor is to refrain from transitioning control to the VMM by delivering the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

15. A system comprising:

a memory having stored therein guest software; and

a processor, coupled to the memory, to execute the guest software, to determine whether fault information relating to a fault associated with an operation of the guest software satisfies at least one filtering criterion, the fault information comprising at least one of a fault identifier, an error code associated with the fault, and one or more additional data values associated with the fault, to refrain from transitioning control to a virtual machine monitor (VMM) if the fault information satisfies the at least one filtering criterion, and to transition control to the VMM if the fault information does not satisfy the at least one filtering criterion.

17. A system comprising:

a memory having stored therein guest software; and

a processor, coupled to the memory, to execute the guest software, to determine whether a fault associated with an operation of guest software requires a transition of control to a virtual machine monitor (VMM) using fault information relating to the fault and at least one control transfer filtering criterion, wherein the at least one control transfer filtering criterion is defined using data stored in one or more designated fields, the one or more designated fields comprising a match field and a mask field, and to deliver the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

18. The system of claim 17 wherein the processor is to determine whether the fault associated with the operation of the guest software requires a transition of control to the VMM by combining the fault information with data stored in the mask field using a bitwise AND operator, and determining whether the result of the combination matches the data stored in the match field.

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

receiving fault information relating to a fault associated with an operation of guest software, the fault information comprising at least one of a fault identifier, an error code associated with the fault, and one or more additional data values associated with the fault;

determining whether the fault information satisfies at least one filtering criterion;

refraining from transitioning control to a virtual machine monitor (VMM) if the fault information satisfies the at least one filtering criterion; and

transitioning control to the VMM if the fault information does not satisfy the at least one filtering criterion.

20. The machine-readable medium of claim 19 wherein:

the at least one filtering criterion is at least one control transfer filtering criterion; and

refraining from transitioning control to the VMM comprises delivering the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

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

determining whether a fault associated with an operation of guest software requires a transition of control to a virtual machine monitor (VMM) using fault information relating to the fault and at least one control transfer filtering criterion, wherein the at least one control transfer filtering criterion is defined using data stored in one or more designated fields, the one or more designated fields comprising a match field and a mask field; and

delivering the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

22. The machine-readable medium of claim 21 wherein the processor is to determine whether the fault associated with the operation of the guest software requires a transition of control to the VMM by combining the fault information with data stored in the mask field using a bitwise AND operator, and determining whether the result of the combination matches the data stored in the match field.