Changeset 33540 in vbox for trunk/src/VBox/VMM/IOM.cpp

Timestamp:

Oct 28, 2010 9:27:05 AM (14 years ago)

Author:

vboxsync

Message:

*: spelling fixes, thanks Timeless!

File:

• trunk/src/VBox/VMM/IOM.cpp (modified) (3 diffs)

trunk/src/VBox/VMM/IOM.cpp

@@ -31 +31 @@
  * In raw-mode I/O port access is trapped (\#GP(0)) by ensuring that the actual
  * IOPL is 0 regardless of what the guest IOPL is. The \#GP handler use the
- * dissassembler (DIS) to figure which instruction caused it (there are a number
+ * disassembler (DIS) to figure which instruction caused it (there are a number
  * of instructions in addition to the I/O ones) and if it's an I/O port access
  * it will hand it to IOMGCIOPortHandler (via EMInterpretPortIO).
@@ -38 +38 @@
  * taken. (Default action is to write into the void and read all set bits.)
  *
- * Memory Mapped I/O (MMIO) is implemented as a sligtly special case of PGM
+ * Memory Mapped I/O (MMIO) is implemented as a slightly special case of PGM
  * access handlers. An MMIO range is registered with IOM which then registers it
  * with the PGM access handler sub-system. The access handler catches all
  * access and will be called in the context of a \#PF handler. In RC and R0 this
- * handler is IOMMMIOHandler while in ring-3 it's IOMR3MMIOHandler (althought in
+ * handler is IOMMMIOHandler while in ring-3 it's IOMR3MMIOHandler (although in
  * ring-3 there can be alternative ways). IOMMMIOHandler will attempt to emulate
  * the instruction that is doing the access and pass the corresponding reads /
  * writes to the device.
  *
- * Emulating I/O port access is less complex and should be sligtly faster than
+ * Emulating I/O port access is less complex and should be slightly faster than
  * emulating MMIO, so in most cases we should encourage the OS to use port I/O.
- * Devices which are freqently accessed should register GC handlers to speed up
+ * Devices which are frequently accessed should register GC handlers to speed up
  * execution.
  *
@@ -488 +488 @@
  *
  * This API is called by PDM on behalf of a device. Devices must first register
- * ring-3 ranges before any GC and R0 ranges can be registerd using IOMR3IOPortRegisterRC()
+ * ring-3 ranges before any GC and R0 ranges can be registered using IOMR3IOPortRegisterRC()
  * and IOMR3IOPortRegisterR0().
  *