儲存庫 vbox 的更動 14530

時間撮記:

2008-11-24 下午04:28:46 (16 年 以前)

作者:

vboxsync

訊息:

More error logging

位置:

trunk/src/VBox/VMM

檔案:

• HWACCM.cpp (修改) (1 筆差異)
• HWACCMInternal.h (修改) (1 筆差異)
• VMMR0/HWSVMR0.cpp (修改) (1 筆差異)
• VMMR0/HWVMXR0.cpp (修改) (2 筆差異)

trunk/src/VBox/VMM/HWACCM.cpp

@@ -1109 +1109 @@
             LogRel(("VERR_VMX_INVALID_VMCS_PTR: CPU%d Current pointer %RGp vs %RGp\n", i, pVM->aCpus[i].hwaccm.s.vmx.lasterror.u64VMCSPhys, pVM->aCpus[i].hwaccm.s.vmx.pVMCSPhys));
             LogRel(("VERR_VMX_INVALID_VMCS_PTR: CPU%d Current VMCS version %x\n", i, pVM->aCpus[i].hwaccm.s.vmx.lasterror.ulVMCSRevision));
+            LogRel(("VERR_VMX_INVALID_VMCS_PTR: CPU%d Entered Cpu %d\n", i, pVM->aCpus[i].hwaccm.s.vmx.lasterror.idEnteredCpu));
+            LogRel(("VERR_VMX_INVALID_VMCS_PTR: CPU%d Current Cpu %d\n", i, pVM->aCpus[i].hwaccm.s.vmx.lasterror.idCurrentCpu));
             break;
 

trunk/src/VBox/VMM/HWACCMInternal.h

@@ -409 +409 @@
             uint32_t                ulInstrError;
             uint32_t                ulExitReason;
+            RTCPUID                 idEnteredCpu;
+            RTCPUID                 idCurrentCpu;
             uint32_t                padding;
         } lasterror;

trunk/src/VBox/VMM/VMMR0/HWSVMR0.cpp

@@ -861 +861 @@
              * Before we are able to execute this instruction in raw mode (iret to guest code) an external interrupt might
              * force a world switch again. Possibly allowing a guest interrupt to be dispatched in the process. This could
-             * break the guest. Sounds very unlikely, but such timing sensitive problem are not as rare as you might think.
+             * break the guest. Sounds very unlikely, but such timing sensitive problems are not as rare as you might think.
              */
             VM_FF_CLEAR(pVM, VM_FF_INHIBIT_INTERRUPTS);

trunk/src/VBox/VMM/VMMR0/HWVMXR0.cpp

@@ -1821 +1821 @@
              * Before we are able to execute this instruction in raw mode (iret to guest code) an external interrupt might
              * force a world switch again. Possibly allowing a guest interrupt to be dispatched in the process. This could
-             * break the guest. Sounds very unlikely, but such timing sensitive problem are not as rare as you might think.
+             * break the guest. Sounds very unlikely, but such timing sensitive problems are not as rare as you might think.
              */
             VM_FF_CLEAR(pVM, VM_FF_INHIBIT_INTERRUPTS);
@@ -3022 +3022 @@
         VMXGetActivateVMCS(&pVCpu->hwaccm.s.vmx.lasterror.u64VMCSPhys);
         pVCpu->hwaccm.s.vmx.lasterror.ulVMCSRevision = *(uint32_t *)pVCpu->hwaccm.s.vmx.pVMCS;
+        pVCpu->hwaccm.s.vmx.lasterror.idEnteredCpu   = pVCpu->hwaccm.s.idEnteredCpu;
+        pVCpu->hwaccm.s.vmx.lasterror.idCurrentCpu   = RTMpCpuId();
     }