Changeset 57260 in vbox for trunk/src/VBox/HostDrivers

Timestamp:

Aug 10, 2015 11:42:12 AM (9 years ago)

Author:

vboxsync

Message:

SUPDrvGip: comment typo nits.

File:

• trunk/src/VBox/HostDrivers/Support/SUPDrvGip.cpp (modified) (7 diffs)

trunk/src/VBox/HostDrivers/Support/SUPDrvGip.cpp

@@ -706 +706 @@
  *
  * @param   pGip                The GIP.
- * @param   nsElapsed           The number of nano seconds elapsed.
+ * @param   nsElapsed           The number of nanoseconds elapsed.
  * @param   cElapsedTscTicks    The corresponding number of TSC ticks.
  * @param   iTick               The tick number for debugging.
@@ -1020 +1020 @@
  * @param   fRough          Set if we're doing the rough calculation that the
  *                          TSC measuring code needs, where accuracy isn't all
- *                          that important (too high is better than to low).
+ *                          that important (too high is better than too low).
  *                          When clear we try for best accuracy that we can
  *                          achieve in reasonably short time.
@@ -1099 +1099 @@
 
         /*
-         * If the CPU changes things get a bit complicated and what we
-         * can get away with depends on the GIP mode / TSC reliablity.
+         * If the CPU changes, things get a bit complicated and what we
+         * can get away with depends on the GIP mode / TSC reliability.
          */
         if (idCpuStop != idCpuStart)
@@ -1166 +1166 @@
                      * No valid deltas.  We retry, if we're on our last retry
                      * we do the cross call instead just to get a result.  The
-                     * frequency will be refined in a few seconds anyways.
+                     * frequency will be refined in a few seconds anyway.
                      */
                     else if (cTriesLeft > 0)
@@ -1175 +1175 @@
             }
             /*
-             * Asynchronous TSC mode: This is bad as the reason we usually
+             * Asynchronous TSC mode: This is bad, as the reason we usually
              * use this mode is to deal with variable TSC frequencies and
              * deltas.  So, we need to get the TSC from the same CPU as
@@ -1666 +1666 @@
  *
  * @param   pGip        Pointer to the GIP.
- * @param   pCpu        Pointer to which GIP CPU to initalize.
+ * @param   pCpu        Pointer to which GIP CPU to initialize.
  * @param   u64NanoTS   The current nanosecond timestamp.
  * @param   uCpuHz      The CPU frequency to set, 0 if the caller doesn't know.
@@ -2121 +2121 @@
      * Determine if we need to update the CPU (TSC) frequency calculation.
      *
-     * We don't need to keep realculating the frequency when it's invariant,
+     * We don't need to keep recalculating the frequency when it's invariant,
      * unless the special tstGIP-2 testing mode is enabled.
      */