Changeset 69653 in vbox for trunk/src/VBox/VMM/tools

Timestamp:

Nov 10, 2017 6:42:55 PM (7 years ago)

Author:

vboxsync

Message:

VMM: scm cleanups

Location:

trunk/src/VBox/VMM/tools

Files:

• MsrLinux.cpp (modified) (1 diff)
• VBoxCpuReport.cpp (modified) (3 diffs)
• VBoxCpuReport.h (modified) (1 diff)

trunk/src/VBox/VMM/tools/MsrLinux.cpp

@@ -33 +33 @@
 #define MSR_DEV_NAME    "/dev/cpu/0/msr"
 
+
 /*********************************************************************************************************************************
 *   Structures and Typedefs                                                                                                      *
 *********************************************************************************************************************************/
+
 
 /*********************************************************************************************************************************

trunk/src/VBox/VMM/tools/VBoxCpuReport.cpp

@@ -41 +41 @@
 
 #include "VBoxCpuReport.h"
+
 
 /*********************************************************************************************************************************
@@ -2551 +2552 @@
             return VBCPUREPBADNESS_BOND_VILLAIN;
 
-        /* 
-         * The TSC is tricky -- writing it isn't a problem, but if we put back the original 
-         * value, we'll throw it out of whack. If we're on an SMP OS that uses the TSC for timing, 
+        /*
+         * The TSC is tricky -- writing it isn't a problem, but if we put back the original
+         * value, we'll throw it out of whack. If we're on an SMP OS that uses the TSC for timing,
          * we'll likely kill it, especially if we can't do the modification very quickly.
          */
@@ -2561 +2562 @@
             break;
 
-        /* 
-         * The following MSRs are not safe to modify in a typical OS if we can't do it atomically, 
-         * i.e. read/modify/restore without allowing any other code to execute. Everything related 
+        /*
+         * The following MSRs are not safe to modify in a typical OS if we can't do it atomically,
+         * i.e. read/modify/restore without allowing any other code to execute. Everything related
          * to syscalls will blow up in our face if we go back to userland with modified MSRs.
-         */ 
+         */
 //        case 0x0000001b: /* IA32_APIC_BASE */
         case 0xc0000081: /* MSR_K6_STAR */

trunk/src/VBox/VMM/tools/VBoxCpuReport.h

@@ -28 +28 @@
 extern int PlatformMsrProberInit(VBMSRFNS *fnsMsr, bool *pfAtomicMsrMod);
 
-