Handling faults associated with operation of guest software in the virtual-machine architecture

• US 6,996,748 B2
• Filed: 06/29/2002
• Issued: 02/07/2006
• Est. Priority Date: 06/29/2002
• Status: Active Grant

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Intel Corporation
• Inventors: Uhlig, Richard, Anderson, Andrew V., Bennett, Steve, Cota-Robles, Erik, Jeyasingh, Stalinselvaraj, Kagi, Alain, Neiger, Gilbert
• Primary Examiner(s): Baderman, Scott
• Assistant Examiner(s): Wilson, Yolanda L
• Application Number:
  US10/184,798
• Publication Number:
  US 20040003324A1
• Time in Patent Office: 1,319 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/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06

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 fault filtering criteria. If the determination is positive, the guest software is permitted to disregard the fault.

Claims

1. A method comprising:

receiving fault information relating to a fault associated with an operation of guest software;

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

causing the guest software to ignore the fault if the fault information satisfies the at least one fault filtering criterion; and

delivering the fault to the guest software if the fault information does not satisfy the at least one fault filtering criterion.

2. The method of claim 1 further comprising:

determining that the fault information does not satisfy the at least one fault filtering criterion; and

determining whether the fault information satisfies at least one control transfer filtering criterion.

3. The method of claim 2 further comprising:

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

4. The method of claim 2 further comprising:

transferring control to a virtual machine monitor if the fault information does not satisfy the at least one control transfer filtering criterion.

5. The method of claim 1 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.

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

7. The method of claim 1 wherein determining whether the fault information satisfies the at least one fault filtering criterion comprises:

determining whether the operation of the guest software is a write to a page table entry; and

determining whether the write is an attempt to mark a page being mapped by the page table entry as not present.

8. The method of claim 1 wherein determining whether the fault information satisfies the at least one fault filtering criterion further comprises:

determining whether the operation of the guest software is a write to a page table entry;

determining whether the write is an attempt to mark a page being mapped by the page table entry as present;

determining whether the page being mapped by the page table entry was previously marked as present;

determining whether the write is not an attempt to modify a page frame number; and

determining whether at least one of a group of conditions occurs, the group of conditions including a first condition requiring that the write be an attempt to mark the page mapped by the page table entry as read-only and the second condition requiring that the page being mapped by the page table entry have been previously writeable.

9. A method comprising:

detecting an occurrence of a faulting condition associated with an operation of guest software;

determining whether fault information pertaining to the faulting condition satisfies at least one fault filtering criterion, the determination comprising comparing data associated with the operation of the guest software with data stored in at least one of memory and a processor register; and

determining whether the guest software is permitted to ignore the faulting condition based on the evaluation.

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 condition is associated with an attempt of the guest software to access memory.

12. The method of claim 9 wherein determining whether the fault information satisfies the at least one fault filtering criterion further comprises:

determining whether the operation of the guest software is a write to a page table entry; and

determining whether the write is an attempt to mark a page being mapped by the page table entry as not present.

13. The method of claim 9 wherein determining whether the fault information satisfies the at least one fault filtering criterion further comprises:

determining whether the operation of the guest software is a write to a page table entry;

determining whether the write is an attempt to mark a page being mapped by the page table entry as present;

determining whether the page being mapped by the page table entry was previously marked as present;

determining whether the write is not an attempt to modify a page frame number; and

determining whether at least one of a group of conditions occurs, the group of conditions including a first condition requiring that the write be an attempt to mark the page mapped by the page table entry as read-only and the second condition requiring that the page being mapped by the page table entry have been previously writeable.

14. 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 fault filtering criterion, to cause the guest software to ignore the fault if the fault information satisfies the at least one fault filtering criterion, to determine that the fault information does not satisfy the at least one fault filtering criterion, and to deliver the fault to the guest software.

15. The system of claim 14 wherein the processor is further to determine that the fault information does not satisfy the at least one fault filtering criterion, and to determine whether the fault information satisfies at least one control transfer filtering criterion.

16. The system of claim 15 wherein the processor is further to deliver the fault to the guest software if the fault information satisfies the at least one control transfer filtering criterion.

17. The system of claim 15 wherein the processor is further to transfer control to a virtual machine monitor if the fault information does not satisfy the at least one control transfer filtering criterion.

18. A system comprising:

a memory having stored therein guest software; and

a processor, coupled to the memory, to execute the guest software, to detect an occurrence of a faulting condition associated with an operation of guest software, to determine whether fault information pertaining to the faulting condition satisfies at least one fault filtering criterion, the determination comprising comparing data associated with the operation of the guest software with data stored in at least one of memory and a processor register, and to determine whether the guest software is permitted to ignore the faulting condition based on the evaluation.

19. The system of claim 18 wherein the fault condition is associated with an attempt of the guest software to access memory.

20. The system of claim 18 wherein the processor is to determine whether the fault information satisfies the at least one fault filtering criterion by determining whether the operation of the guest software is a write to a page table entry, and determining whether the write is an attempt to mark a page being mapped by the page table entry as not present.

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:

receiving fault information relating to a fault associated with an operation of guest software;

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

causing the guest software to ignore the fault if the fault information satisfies the at least one fault filtering criterion;

determining that the fault information does not satisfy the at least one fault filtering criterion; and

delivering the fault to the guest software.

22. The machine-readable medium of claim 21 wherein the method further comprises:

determining that the fault information does not satisfy the at least one fault filtering criterion; and

determining whether the fault information satisfies at least one control transfer filtering criterion.

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

detecting an occurrence of a faulting condition associated with an operation of guest software;

determining whether fault information pertaining to the faulting condition satisfies at least one fault filtering criterion, the determination comprising comparing data associated with the operation of the guest software with data stored in at least one of memory and a processor register; and

determining whether the guest software is permitted to ignore the faulting condition based on the evaluation.

24. The machine-readable medium of claim 23 wherein the fault condition is associated with an attempt of the guest software to access memory.