Changeset 13691 in vbox

Timestamp:

Oct 30, 2008 9:16:40 PM (16 years ago)

Author:

vboxsync

Message:

pg_vmm update.

File:

• trunk/src/VBox/VMM/VMM.cpp (modified) (1 diff)

trunk/src/VBox/VMM/VMM.cpp

@@ -22 +22 @@
 //#define NO_SUPCALLR0VMM
 
-/** @page   pg_vmm              VMM - The Virtual Machine Monitor
- *
- * !Revise this! It's already incorrect!
- *
- * The Virtual Machine Monitor (VMM) is the core of the virtual machine. It
- * manages the alternate reality; controlling the virtualization, managing
- * resources, tracking CPU state, it's resources and so on...
- *
- * We will split the VMM into smaller entities:
- *
- *      - Virtual Machine Core Monitor (VMCM), which purpose it is to
- *        provide ring and world switching, that including routing
- *        interrupts to the host OS and traps to the appropriate trap
- *        handlers. It will implement an external interface for
- *        managing trap handlers.
- *
- *      - CPU Monitor (CM), tracking the state of the CPU (in the alternate
- *        reality) and implementing external interfaces to read and change
- *        the state.
- *
- *      - Memory Monitor (MM), which purpose it is to virtualize physical
- *        pages, segment descriptor tables, interrupt descriptor tables, task
- *        segments, and keep track of all memory providing external interfaces
- *        to access content and map pages. (Internally splitt into smaller entities!)
- *
- *      - IO Monitor (IOM), which virtualizes in and out I/O operations. It
- *        interacts with the MM to implement memory mapped I/O. External
- *        interfaces for adding and removing I/O ranges are implemented.
- *
- *      - External Interrupt Monitor (EIM), which purpose it is to manage
- *        interrupts generated by virtual devices. This monitor provides
- *        an interfaces for raising interrupts which is accessible at any
- *        time and from all thread.
- *        <p>
- *        A subentity of the EIM is the vitual Programmable Interrupt
- *        Controller Device (VPICD), and perhaps a virtual I/O Advanced
- *        Programmable Interrupt Controller Device (VAPICD).
- *
- *      - Direct Memory Access Monitor (DMAM), which purpose it is to support
- *        virtual device using the DMA controller. Interfaces must be as the
- *        EIM interfaces independent and threadable.
- *        <p>
- *        A subentity of the DMAM is a virtual DMA Controller Device (VDMACD).
- *
- *
- * Entities working on a higher level:
- *
- *      - Device Manager (DM), which is a support facility for virtualized
- *        hardware. This provides generic facilities for efficient device
- *        virtualization. It will manage device attaching and detaching
- *        conversing with EIM and IOM.
- *
- *      - Debugger Facility (DBGF) provides the basic features for
- *        debugging the alternate reality execution.
- *
+/** @page pg_vmm        VMM - The Virtual Machine Monitor
+ *
+ * The VMM component is two things at the moment, it's a component doing a few
+ * management and routing tasks, and it's the whole virtual machine monitor
+ * thing.  For hysterical reasons, it is not doing all the management that one
+ * would expect, this is instead done by @ref pg_vm.  We'll address this
+ * misdesign eventually.
  *
  * @see grp_vmm, grp_vm
  *
  *
- * @section pg_vmm_s_use_cases          Use Cases
- *
- * @subsection  pg_vmm_s_use_case_boot  Bootstrap
- *
- *  - Basic Init:
- *      - Init SUPDRV.
- *
- *  - Init Virtual Machine Instance:
- *      - Load settings.
- *      - Check resource requirements (memory, com, stuff).
- *
- *  - Init Host Ring 3 part:
- *      - Init Core code.
- *      - Load Pluggable Components.
- *      - Init Pluggable Components.
- *
- *  - Init Host Ring 0 part:
- *      - Load Core (core = core components like VMM, RMI, CA, and so on) code.
- *      - Init Core code.
- *      - Load Pluggable Component code.
- *      - Init Pluggable Component code.
- *
- *  - Allocate first chunk of memory and pin it down. This block of memory
- *    will fit the following pieces:
- *      - Virtual Machine Instance data. (Config, CPU state, VMM state, ++)
- *        (This is available from everywhere (at different addresses though)).
- *      - VMM Guest Context code.
- *      - Pluggable devices Guest Context code.
- *      - Page tables (directory and everything) for the VMM Guest
- *
- *  - Setup Guest (Ring 0) part:
- *      - Setup initial page tables (i.e. directory all the stuff).
- *      - Load Core Guest Context code.
- *      - Load Pluggable Devices Guest Context code.
- *
- *
- */
-
+ * @section sec_vmmstate        VMM State
+ *
+ * To be written.
+ *
+ * Lets see which of these links that works...
+ * @image "VM Statechart Diagram.gif"
+ * @image VM\ Statechart\ Diagram.gif
+ *
+ * @subsection  subsec_vmm_init     VMM Initialization
+ *
+ * To be written.
+ *
+ *
+ * @subsection  subsec_vmm_term     VMM Termination
+ *
+ * To be written.
+ *
+ */
 
 /*******************************************************************************