Information scheduling method from secure container operating system to virtual machine monitor

Abstract

The invention discloses an information scheduling method from a secure container operating system to a virtual machine monitor. The invention provides a scheduling method from a security container toa virtual machine monitor. The scheduling method comprises the steps: providing the virtual machine monitor and a security container kernel share a memory space; constructing a shared memory-based message queue between the two security container kernels and the virtual machine monitor, wherein a memory pointer of the Hyper Call of the security container kernel is placed in the message queue; enabling the virtual machine monitor to process the Hyper Call in the shared memory; and putting the processed Hyper Call thread ID into a message queue, and obtaining the processed Hyper Call thread ID bythe scheduler. Through the information exchange mode of the queue, when the virtual CPU (vCPU) of the security container needs to call the Hyper Call, the context switching between the kernel of thesecurity container and the monitor of the virtual machine is not needed, so that the execution efficiency of the super call can be greatly improved.

Description

technical field [0001] The invention relates to the computer field, to a virtual machine, and in particular to a method for dispatching a message queue-based safe container operating system to a virtual machine monitor. Background technique [0002] Host OS is an operating system installed on a physical host, and then virtual machine monitor software is run on the Host OS operating system, so that several partitions can be virtualized on the physical host, and different operating systems can be installed separately. The corresponding operating system installed on the virtual partition is called Guest OS. [0003] Virtual machine monitor (English: virtual machine monitor, abbreviated as VMM), VMM provides a virtual operating environment for the Guest OS by invoking HostOS resources. VMM needs to communicate with GuestOS through a system software called Hypervisor. [0004] Virtual machine (KVM, Kernel-based Virtual Machine) is a virtual machine software widely used in the m...

AI Technical Summary

Problems solved by technology

The performance of "KVM Hyper Call" is relatively poor. This is because a "KVM Hyper Call" requires two context switches: a. Secure container to host operating system switching; b. Host operating system to virtual machine monitor process switching; these up and down The cost of switching is very high. In the scenario of high throughput (Request Per Second, RPS), "KVM Hyper Call" becomes the bottleneck of the system

Images