WO2013189180A1

WO2013189180A1 - Method and device for disabling interruption in virtualization system

Info

Publication number: WO2013189180A1
Application number: PCT/CN2013/070810
Authority: WO
Inventors: 马彬; 郑章孝; 白云鹏
Original assignee: 华为技术有限公司
Priority date: 2012-06-21
Filing date: 2013-01-22
Publication date: 2013-12-27
Also published as: CN102799480B; CN102799480A

Abstract

Provided are a method and device for disabling an interruption in a virtualization system, which supports the interruption enabling/disabling of a Guest OS much better, and reduces the influence on the system running efficiency. The method includes: providing an interface to a virtualization operating system Guest OS so that the Guest OS calls the interface to set an interruption flag for an interruption flag bit register corresponding to the Guest OS in a shared memory; inspecting the interruption flag bit register; and if the interruption flag bit register shows that the Guest OS needs to disable an interruption, prohibiting the transmission of a virtual interruption to the Guest OS. The method provided in the present invention does not rely on the common compilation of a Hypervisor and a Guest OS, the Hypervisor need not share a code segment with the Guest OS, the access to a shared memory is carried out via a virtual address, the speed is high at the time of disabling/enabling an interruption, and the system running efficiency is high.

Description

Method and apparatus for shutting down an interrupt in a virtualized system. The present application claims to be filed on June 21, 2012 by the Chinese Patent Office, Application No. 201210207137.5, entitled "Method and Apparatus for Shutdown Interruption in Virtualization System" The present invention relates to the field of computers, and more particularly to a method and apparatus for shutting down an interrupt in a virtualized system. Background technique

In order to prevent important system program code from being interrupted or to ensure data consistency, the operating system (OS) needs to perform the shutdown operation.

In a non-virtualized environment, the OS can directly shut down physical hardware interrupts. However, once the real-time embedded virtualization component, the Hypervisor, is deployed, the distribution of the interrupt is managed by the Hypervisor, and the OS does not directly shut down the physical hardware interrupt. For example, in a virtualization system, multiple guest operating systems ( Guest OSs) run on a single Central Processing Unit (CPU). A single Guest OS can not affect other Guest OSs on the same physical CPU when performing shutdown interrupts. The operation, which requires the Hypervisor to coordinate the processing of the shutdown interrupt.

In the virtualization system in which the hypervisor is deployed, a method for shutting down the interrupt provided by the prior art is: Hypervisor and Guest OS independently compile, link the image, and load the image into the memory through the bootloader (Hotvisor) and the image of the Guest OS. The BootLoader starts the hypervisor, and the Hypervisor starts each guest OS separately. Because in the virtualized system, the interrupt is uniformly distributed by the Hypervisor, the Hypervisor needs to provide the communication method of the Hyper Call. That is, the Guest OS sends a request to close the interrupt to the Hypervisor through Hyper Call. After the Hypervisor receives the request to close the interrupt, it sets the prohibition of distributing the interrupt to the relevant Guest OS kernel, that is, the interrupt is closed.

Hyper Call-like applications that are invoked across a cross-image interface that does not share a code segment (for example,

XEN provides a cross-image interface call) and a scenario called by an interface between different privilege-level modes (for example, a syscall call provided by Linux). Currently, in the above application scenario, Hyper Call exists. Multiple implementations, for example, via message communication, by interrupt communication, or by implementing inter-mode interface calls. Since the implementation of Hyper Call generally involves the application of a general communication mechanism such as memory and queues, if the Guest OS needs to frequently perform the operation of turning on or off the interrupt, the above-mentioned prior art provides a shutdown interrupt method to make the system run. Less efficient.

Summary of the invention

Embodiments of the present invention provide a method and apparatus for shutting down an interrupt in a virtualization system to better support Guest OS on/off interrupts while reducing the impact on system operation efficiency.

An embodiment of the present invention provides a method for shutting down an interrupt in a virtualization system, where the method includes: providing an interface to a guest operating system Guest OS to enable the guest OS to invoke the interface to correspond to the guest OS in a shared memory. The interrupt flag bit register sets an interrupt flag, and the shared memory is a physical memory shared by the real-time embedded virtualization component Hypervisor with at least one guest OS and used for recording an interrupt flag, wherein different guest OS in the shared memory is shared with the hypervisor The memory space is isolated from each other; the interrupt flag bit register is checked; if the interrupt flag bit register indicates that the guest OS needs to close the interrupt, then the virtual interrupt is prohibited from being sent to the guest OS.

An embodiment of the present invention provides an apparatus for shutting down an interrupt in a virtualization system, where the apparatus includes: an interface providing module, configured to provide an interface to a virtualized operating system Guest OS to enable the guest OS to invoke the interface to share in a memory An interrupt flag register corresponding to the guest OS is configured to set an interrupt flag, where the shared memory is a physical memory shared by the real-time embedded virtualization component Hypervisor and configured by at least one guest OS for recording an interrupt flag, and different guest in the shared memory The memory space shared by the OS and the hypervisor is isolated from each other; a flag check module is configured to check the interrupt flag bit register; and an interrupt cutoff sending module is configured to: if the flag bit check module checks the interrupt flag bit register, indicate If the Guest OS needs to close the interrupt, it is forbidden to send a virtual interrupt to the Guest OS.

As can be seen from the foregoing embodiments of the present invention, the real-time embedded virtualization component Hypervisor provides an interface to the virtualized operating system Guest OS, and the guest OS can share the hypervisor with at least one guest OS and use the physical memory that is used to record the interrupt flag, that is, the shared memory. The interrupt flag bit register corresponding to the Guest OS sets an interrupt flag. The method provided by the embodiment of the present invention does not depend on the hypervisor and the guest, compared with the prior art method of turning off the interrupt by providing a communication manner of the interrupt notification. The OS compiles together, and the Hypervisor does not need to share the code segment with the Guest OS. Because the virtualization layer is separated from the Guest OS image, the access to the shared memory is performed through the virtual address. Therefore, the shutdown/open interrupt is fast and the system runs efficiently.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the prior art or the embodiments will be briefly described below. Obviously, the drawings in the following description are only the present invention. For some embodiments, other figures may also be obtained as those skilled in the art from these figures.

1 is a schematic flowchart of a method for shutting down an interrupt in a virtualization system according to an embodiment of the present invention; FIG. 2 is a schematic diagram of running a plurality of guest OSs and a single entity on a single physical CPU according to an embodiment of the present invention;

A scenario diagram of a guest OS running on multiple physical CPUs;

3 is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to another embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to another embodiment of the present invention; FIG.

6b is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to another embodiment of the present invention;

FIG. 7 is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to another embodiment of the present invention.

detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention are within the scope of the present invention.

Referring to FIG. 1 , it is a flow chart of a method for shutting down an interrupt in a virtualization system according to an embodiment of the present invention. The schematic diagram mainly includes step S101, step S102, and step S103:

S101. The interface is provided to the virtualization operating system Guest OS, so that the guest OS invokes the interface to set an interrupt flag in an interrupt flag register corresponding to the guest OS in the shared memory, where the shared memory is real-time embedded virtualization. The component Hypervisor is shared with at least one Guest OS and is used to record the physical memory of the interrupt flag.

In the embodiment of the present invention, the Guest OS is a virtualized operating system, and the operating system is different from the general operating system in that not only one such virtualized operating system or one such virtualization is run on a single physical CPU. The operating system only runs on a single physical CPU, that is, it does not run directly on the hardware layer (Hardware), but a real-time embedded virtualization component Hypervisor running on the hardware layer, as shown in Figure 2, is a single physics. A scenario diagram of running multiple Guest OSs and a single Guest OS running on multiple physical CPUs on the CPU. For example, Guest OS0 and Guest OS7 run on physical CPU0 (CoreO) via Hypervisor, while Guest OS« runs on physical CPU7 (Core7), physical CPU2 (Core2) and physical CPU« (Corew) via Hypervisor.

In the embodiment of the present invention, the real-time embedded virtualization component Hypervisor provides a layer of intermediate addresses, which are managed by a shadow page table, in contrast to the prior art in which the interrupt is closed by a communication method of a Hyper Call. The guest OS establishes the mapping between the guest OS and the intermediate address and the mapping of the intermediate address to the physical memory address by the hypervisor. Here, the mapping from the guest OS to the intermediate address is called the first layer address mapping, and the mapping from the intermediate address to the physical memory address is called a mapping. The second layer knows the physical memory requirements of all Guest OSs on the Hypervisor of the real-time embedded virtualization component and systematically divides the physical memory resources according to the requirements of the Guest OS for physical memory.

After the first layer address mapping and the second layer address mapping are established, a real-time embedded virtualization component Hypervisor can be established to share the physical memory of the interrupt flag with at least one Guest OS. In the following description, for the convenience of description, the physical memory cartridge that shares the real-time embedded virtualization component Hypervisor with at least one Guest OS and is used to record the interrupt flag is called "shared memory". Obviously, the shared memory is part of physical memory. . As shown in FIG. 3, it is a schematic diagram of establishing shared memory in physical memory in the method provided by the embodiment of the present invention. Shared memory can be accessed by the hypervisor and One guest OS is accessed in common, and the different guest OS in the shared memory is isolated from the memory space shared by the hypervisor, that is, the memory space shared by any Guest OS and the Hypervisor in the shared memory and another Guest OS and Hypervisor. The shared memory space is isolated from each other. For example, in Figure 3, Guest OS0 is shared with the Hypervisor and used to record the physical memory of the interrupt flag, that is, the interrupt flag bit space in the shared memory. The shared memory that Guest OS1 shares with the Hypervisor and is used to record the interrupt flag is shared memory. The "VM7 interrupt flag bit space" and the "VM2 interrupt flag bit space" in the shared memory shared by the Guest OS2 and the Hypervisor and used to record the interrupt flag are isolated from each other.

As an embodiment of the present invention, an interface is provided to the virtualization operating system Guest OS to enable the guest OS to invoke the interface to set an interrupt flag set interrupt flag corresponding to the guest OS in the shared memory: The virtualization component Hypervisor provides an interface to the guest OS to enable the guest OS to invoke the interface, access the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and pass the second layer according to the intermediate address. The address mapping accesses the shared memory, and sets an interrupt flag to an interrupt flag bit register corresponding to the Guest OS. For example, a logic "0" indicates that the interrupt is turned off, and a logic "Γ indicates that the interrupt is turned on. It should be noted that due to real time The embedded virtualization component Hypervisor establishes the first layer address mapping and the second layer address mapping. Therefore, when the guest OS sets the interrupt flag, it is the interface provided by the aforementioned first layer address mapping and real-time embedded virtualization component Hypervisor. Access the intermediate address, then, through the second layer The address mapping finally accesses the shared memory, but during the running of the system, there is no difference between the guest OS and the direct access shared memory, that is, the guest OS considers that it directly accesses the shared memory, and the interrupt flag corresponding to the guest OS is The register sets the interrupt flag.

S102. Check the interrupt flag bit register.

As an embodiment of the present invention, when the interrupt flag bit register is checked, an exception handling function specified by the exception vector may be executed to check the interrupt flag bit register. Specifically, the physical interrupt generated by the hardware, for example, a general physical interrupt or a fast physical interrupt, is first routed to the physical core through the GIC, the Hypervisor program is run on the physical core, and then the exception vector table of the Hypervisor is entered, and the exception is jumped to the Hypervisor. The vector-specified exception handler checks the contents of the interrupt flag bit register during the interrupt processing of the Hypervisor. In the above embodiment of the check interrupt flag bit register, the interrupt flag bit register may be periodically polled according to a clock provided by the real-time embedded virtualization component Hypervisor, that is, the interrupt flag bit register may be actively checked, or The interrupt flag bit register is checked under the trigger of a hardware-generated physical interrupt, that is, the interrupt flag bit register is passively checked.

S103. If the interrupt flag bit register indicates that the guest OS needs to close the interrupt, then prohibiting sending a virtual interrupt to the guest OS.

For example, if the logic "0" is used to turn off the interrupt and the logic "1" is used to indicate that the interrupt is turned on, it is checked that the contents of the interrupt flag bit register are logic "0", and the physical interrupt generated by the hardware is prohibited from being sent to the guest OS.

According to the method for shutting down the interrupt in the virtualization system provided by the embodiment of the present invention, the real-time embedded virtualization component Hypervisor provides an interface to the virtualized operating system Guest OS, and the guest OS can share the hypervisor with at least one guest OS. The interrupt flag is set in the physical memory of the interrupt flag, that is, the interrupt flag bit register corresponding to the Guest OS in the shared memory. The method provided by the embodiment of the present invention does not depend on the Hypervisor to compile with the Guest OS, and the Hypervisor does not need to share the code segment with the Guest OS. The virtualization layer and the guest are compared with the prior art. The OS image is separated, and the access to the shared memory is performed by the virtual address. Therefore, the speed is fast when the interrupt is turned off/on, and the system operates efficiently.

Referring to FIG. 4, it is a schematic structural diagram of an apparatus for shutting down an interrupt in a virtualization system according to an embodiment of the present invention. For the convenience of description, only parts related to the embodiment of the present invention are shown. The apparatus for shutting down an interrupt in the virtualization system of the example of FIG. 4 includes an interface providing module 401, a flag check module 402, and an interrupt cutoff transmitting module 403, where:

The interface providing module 401 is configured to provide an interface to the virtualized operating system Guest OS, so that the guest OS invokes the interface to set an interrupt flag of an interrupt flag bit register corresponding to the guest OS in the shared memory, where the shared memory is The real-time embedded virtualization component Hypervisor is shared with at least one Guest OS and used to record the physical memory of the interrupt flag, wherein different Guest OSs in the shared memory are isolated from each other by the memory space shared by the Hypervisor.

The flag check module 402 checks the interrupt flag bit register. The interrupt cutoff sending module 403 is configured to disable sending a virtual interrupt to the guest OS if the flag check module 402 checks that the interrupt flag bit register indicates that the guest OS needs to close the interrupt.

It should be noted that, in the implementation of the apparatus for shutting down the interrupt in the above virtualization system, the division of each functional module is merely an example, and the actual application may be considered according to requirements, such as configuration requirements of the corresponding hardware or convenience of implementation of the software. The above function distribution is completed by different functional modules, that is, the internal structure of the cable modem online device is divided into different functional modules to complete all or part of the functions described above. Moreover, in practical applications, the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be implemented by corresponding hardware to execute corresponding software. For example, the foregoing interface providing module may be configured to perform the foregoing virtual The operating system Guest OS provides an interface for the guest OS to invoke the interface to set the hardware of the interrupt flag register corresponding to the Guest OS in the shared memory, such as an interface provider, or can execute the corresponding computer. The general processor or other hardware device that completes the foregoing functions; and the flag check module as described above may be hardware having the function of performing the foregoing checking of the interrupt flag bit register, such as a flag checker, or may be executable. A general processor or other hardware device that performs the aforementioned functions in the corresponding computer program (the various described embodiments of the present specification may apply the above described principles).

The interface providing module 401 of the exemplary embodiment of FIG. 4 may include an interface invoking unit 501 and an interrupt flag setting unit 502. As shown in FIG. 5, a device for shutting down an interrupt in a virtualization system according to another embodiment of the present invention is shown in FIG.

An interface calling unit 501, configured to provide an interface to the virtualized operating system Guest OS to enable the guest OS to invoke the interface;

The interrupt flag setting unit 502 is configured to access the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and according to the intermediate address and through the second layer address mapping, corresponding to the guest OS The interrupt flag bit register sets an interrupt flag, the first layer address mapping is a mapping of the guest OS to an intermediate address, and the second layer address mapping is a mapping of the intermediate address to a physical memory address, the physical memory The shared memory is included.

The apparatus for shutting down the interrupt in the virtualization system illustrated in FIG. 4 or FIG. 5 may further include mapping establishment. The module 601 and the shared memory establishing module 602, as shown in FIG. 6a or FIG. 6b, the device for shutting down the interrupt in the virtualization system according to another embodiment of the present invention, wherein:

The mapping establishment module 601 is configured to establish a mapping of the guest OS to the intermediate address and the mapping of the intermediate address to the physical memory address.

a shared memory establishing module 602, configured to establish the shared memory, where the shared memory is different

The memory space shared by the Guest OS and the Hypervisor is isolated from each other.

The flag check module 402 of the example of FIG. 4 may periodically poll the interrupt flag bit register according to the clock provided by the real-time embedded virtualization component Hypervisor, or may be checked under the trigger of a hardware-generated physical interrupt. Interrupt flag bit register. The flag check module 402 can include a first execution unit 701, such as the device for shutting down the interrupt in the virtualization system provided by another embodiment of the present invention, as shown in FIG.

The execution unit 701 is configured to execute an exception handling function specified by the exception vector to check the interrupt flag bit register. Specifically, the physical interrupt generated by the hardware, for example, a general physical interrupt or a fast physical interrupt, is first routed to the physical core through the GIC, the Hypervisor program is run on the physical core, and then the exception vector table of the Hypervisor is entered, and the exception is jumped to the Hypervisor. The vector-specified exception handling function executes the unit 701 to execute the exception handling function specified by the exception vector in the exception vector table during the interrupt processing of the Hypervisor to check the contents of the interrupt flag bit register.

It should be noted that the information interaction, the execution process, and the like between the modules/units of the foregoing device are the same as the embodiment of the method of the present invention. Reference is made to the description in the method embodiment of the present invention, and details are not described herein again.

One of ordinary skill in the art will appreciate that all or a portion of the various methods of the above-described embodiments can be performed by a program to instruct the associated hardware, such as one or more or all of the following various methods:

Providing an interface to the virtualized operating system Guest OS to enable the guest OS to invoke the interface to set an interrupt flag of an interrupt flag bit register corresponding to the guest OS in the shared memory, where the shared memory is a real-time embedded virtualization component Hypervisor Physical memory shared with at least one Guest OS and used to record interrupt flags;

Checking the interrupt flag bit register; If the interrupt flag bit register indicates that the guest OS needs to close the interrupt, then the virtual interrupt is prohibited from being sent to the guest OS.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.

The foregoing description of the method and apparatus for shutting down the interrupt in the virtualization system provided by the embodiment of the present invention is only for assisting in understanding the method and core idea of the present invention. Meanwhile, for those skilled in the art, according to the present invention, The present invention is not limited by the scope of the present invention.

Claims

Rights request

1. A method for turning off interrupts in a virtualization system, characterized in that the method includes: providing an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to transfer the shared memory to the Guest OS The corresponding interrupt flag bit register sets the interrupt flag, the shared memory is a physical memory shared by the real-time embedded virtualization component Hypervisor and at least one Guest OS and used to record the interrupt flag, and different Guest OSs in the shared memory are different from the The memory spaces shared by the Hypervisor are isolated from each other;

Check the interrupt flag register;

If the interrupt flag bit register indicates that the Guest OS needs to turn off interrupts, it is prohibited to send virtual interrupts to the Guest OS.

2. The method of claim 1, wherein the interface is provided to the virtualization operating system Guest OS so that the Guest OS calls the interface to set the interrupt flag bit corresponding to the Guest OS in the shared memory. Registers set interrupt flags, including:

Provide an interface to the virtualized operating system Guest OS so that the Guest OS calls the interface; access the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and access the intermediate address according to the intermediate address and through the second layer The address mapping accesses the shared memory and sets the interrupt flag in the interrupt flag bit register corresponding to the Guest OS.

3. The method of claim 2, wherein the interface is provided to the virtualization operating system Guest OS so that the Guest OS sets an interrupt flag in an interrupt flag bit register corresponding to the Guest OS in the shared memory. Also included before: Establishing the shared memory.

4. The method of claim 1, wherein the checking of the interrupt flag register includes:

Periodically poll the interrupt flag register according to the clock provided by the hypervisor; or

When triggered by a physical interrupt generated by hardware, the interrupt flag register is checked.

5. The method of claim 4, wherein: checking the interrupt flag register Devices include:

Execute the exception handling function specified by the exception vector to check the interrupt flag register.

6. A device for turning off interrupts in a virtualization system, characterized in that the device includes: an interface providing module, configured to provide an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to share the memory The interrupt flag bit register corresponding to the Guest OS sets the interrupt flag. The shared memory is a physical memory shared by the real-time embedded virtualization component Hypervisor and at least one Guest OS and used to record the interrupt flag. Different in the shared memory The memory space shared by the Guest OS and the hypervisor is isolated from each other;

A flag bit check module, used to check the interrupt flag bit register;

An interrupt cutoff sending module is configured to prohibit sending virtual interrupts to the Guest OS if the flag bit checking module checks the interrupt flag bit register and indicates that the Guest OS needs to turn off interrupts.

7. The device according to claim 6, wherein the interface providing module includes: an interface calling unit, configured to provide an interface to the virtualized operating system Guest OS so that the Guest OS calls the interface;

An interrupt flag setting unit, configured to access the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and then access the shared memory according to the intermediate address and through the second layer address mapping. The interrupt flag bit register corresponding to the Guest OS sets the interrupt flag.

8. The device according to claim 6 or 7, characterized in that the device further includes: mapping of physical memory addresses;

A shared memory creation module, used to create the shared memory.

9. The device according to claim 6, wherein the flag checking module periodically polls the interrupt flag register according to the clock provided by the hypervisor; or

The flag bit checking module checks the interrupt flag bit register when triggered by a physical interrupt generated by the hardware.

10. The device according to claim 9, wherein the flag bit checking module includes: an execution unit, configured to execute the exception handling function specified by the exception vector to check the interrupt flag bit register.