One interesting observation was that other than the procedure used by the Java VM to access the OS APIs, no other calls were made to the OS APIs directly or indirectly. By observing the information the Java VM got from Windows about the currently used process, for example, which Win32 functions were used, the bank of memory my Java VM was getting via the Win32 DLLs and the Win32 API calls, the compiler settings in the JVMside gdb generated syntax file, and the call stack and registers, I could see that all processing work was done using the OS APIs via a pipeline of Win32 DLL functions to the OS API. Cv game database win32 final release.dll Finally, I could see no evidence that the hardware registers were used through the OS APIs, which are purely in software in this setup. This showed me that the OS APIs provided everything what the Java VM needed to run the Java application. This also showed me that this setup did not use Windows System Management (WinSMC). The Java VM did not directly access the hardware registers through the OS APIs, but instead accessed it via software routines and emulated those calls. After the Java VM executed the application code it used opcodes to access the registers.
If you combine this with the above observation that I was made for sure that the Java VM did not directly access the hardware, but through the OS APIs through Win32 DLLs, I could conclude that this setup did not directly use any hardware registers such as the contents of CR0, or CR4, or notes at all, but through the OS APIs through Win32 DLLs. This was the configuration I documented for use with Cv Games: With HotSpot the reasons for the main compromises (copied-from-large-memory, and limitations in the JVM to communicate with the OS) are well understood. Cross-process communication requires that the Windows system provides some operating systems services, namely the ability to open, read, and write files, and to send a message to another process, which is done through the OS thread scheduler. The OS thread scheduler uses address space protection to let only one process work per address space at a time. 7211a4ac4a