CN102799480A - Method and device for closing interrupt in virtualization system - Google Patents

Abstract

The invention provides a method and device for disabling interrupts in a virtualization system, better supports guest OS on/off interrupts, and reduces the impact on system operating efficiency. The method includes: providing an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to set an interrupt flag in the interrupt flag register corresponding to the Guest OS in the shared memory; checking the interrupt flag register ; If the interrupt flag bit register indicates that the Guest OS needs to disable interrupts, then prohibit sending virtual interrupts to the Guest OS. The method provided by the present invention does not rely on the joint compilation of the Hypervisor and the Guest OS, the Hypervisor does not need to share code segments with the Guest OS, the access to the shared memory is performed through the virtual address, the speed of closing/opening the interrupt is fast, and the system operation efficiency is high.

Description

Method and device for closing interrupt in virtualization system

technical field

The invention relates to the field of computers, in particular to a method and device for disabling interrupts in a virtualization system.

Background technique

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

In a non-virtualized environment, the OS can directly disable physical hardware interrupts. However, once the real-time embedded virtualization component Hypervisor is deployed, the distribution of interrupts will be managed by the Hypervisor, and the OS cannot directly disable physical hardware interrupts. For example, in a virtualization system, multiple guest operating systems (Guest OS) will run on a single physical central processing unit (Central Processing Unit, CPU), and a single Guest OS cannot affect other Guest OSs on the same physical CPU when the interrupt is disabled. running, which requires the Hypervisor to coordinate and process the operation of disabling interrupts.

In a virtualization system in which a Hypervisor is deployed, a method for disabling interrupts provided by the prior art is: Hypervisor and Guest OS independently compile and link images, and the images of Hypervisor and Guest OS are loaded into memory through a bootloader (BootLoader), and BootLoader Start the Hypervisor, and the Hypervisor starts each Guest OS separately. Since in the virtualization system, interrupts are uniformly distributed by the Hypervisor, the Hypervisor is required to provide a communication method for interrupt notification (Hyper Call), that is, the Guest OS sends a request to the Hypervisor to disable interrupts through the Hyper Call. After the Hypervisor receives the request to disable the interrupt, it sets the prohibition of distributing interrupts to the relevant Guest OS kernel, that is, disables the interrupt.

Hyper Call is generally applied in scenarios of cross-image interface calls that do not share a code segment (for example, cross-image interface calls provided by XEN) and interface calls between different privileged modes (for example, syscall calls provided by Linux), etc. , at present, in the above application scenarios, there are many ways to implement Hyper Call, for example, through message communication, through interrupt communication, or through the interface call function between modes. Since the implementation of Hyper Call generally involves the application of general communication mechanisms such as memory and queues, if the Guest OS needs to frequently perform the operation of opening or closing interrupts, the method of closing interrupts provided by the above-mentioned prior art makes the system run less efficient.

Contents of the invention

Embodiments of the present invention provide a method and device for disabling interrupts in a virtualization system, so as to better support guest OS on/off interrupts and reduce the impact on system operating efficiency.

An embodiment of the present invention provides a method for disabling interrupts in a virtualization system, the method comprising: providing an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to correspond to the Guest OS in the shared memory The interrupt flag bit register sets the interrupt flag, and the shared memory is the 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 the different Guest OS in the shared memory are shared with the Hypervisor Check the interrupt flag bit register; if the interrupt flag bit register indicates that the Guest OS needs to close the interrupt, it is forbidden to send a virtual interrupt to the Guest OS.

An embodiment of the present invention provides a device for disabling interrupts in a virtualization system. The device includes: an interface providing module for providing 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, and the shared memory is the real-time embedded virtualization component Hypervisor shares with at least one Guest OS and is used to record the physical memory of the interrupt flag, and the different Guest in the shared memory The memory space shared by the OS and the Hypervisor is isolated from each other; the flag bit checking module is used to check the interrupt flag bit register; the interrupt cut-off sending module is used to indicate that the interrupt flag bit register is checked if the flag bit checking module checks the interrupt flag bit register If the Guest OS needs to disable interrupts, it is prohibited to send virtual interrupts to the Guest OS.

As can be seen from the above-mentioned embodiments of the present invention, since the real-time embedded virtualization component Hypervisor provides an interface to the virtualized operating system Guest OS, the Guest OS can share the Hypervisor with at least one Guest OS and be used to record the physical memory of the interrupt flag, that is, the shared memory The interrupt flag bit register corresponding to the Guest OS in the set interrupt flag. Compared with the prior art method of disabling interruption by providing a communication mode of interruption notification, the method provided by the embodiment of the present invention does not rely on Hypervisor and Guest OS to compile together, and Hypervisor does not need to share code segments with Guest OS; since the virtualization layer and Guest OS The image is separated, and the access to the shared memory is performed through the virtual address, so the speed is fast when the interrupt is turned off/on, and the system operation efficiency is high.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the prior art or the accompanying drawings that need to be used in the description of the embodiments. Obviously, the accompanying drawings in the following description are only some of the present invention. Embodiment, for those skilled in the art, can also obtain its

his drawings.

FIG. 1 is a schematic flowchart of a method for disabling interrupts in a virtualization system provided by an embodiment of the present invention;

FIG. 2 is a schematic diagram of a scenario in which multiple Guest OSs run on a single physical CPU and a single Guest OS runs on multiple physical CPUs according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a device for disabling interrupts in a virtualization system provided by an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a device for disabling interrupts in a virtualization system according to another embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a device for disabling interrupts in a virtualization system according to another embodiment of the present invention;

Fig. 6a is a schematic structural diagram of a device for disabling interrupts in a virtualization system according to another embodiment of the present invention;

Fig. 6b is a schematic structural diagram of a device for disabling interrupts in a virtualization system according to another embodiment of the present invention;

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

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention belong to the protection scope of the present invention.

Please refer to accompanying drawing 1, which is a schematic flowchart of a method for disabling interrupts in a virtualization system provided by an embodiment of the present invention, mainly including steps S101, S102 and S103:

S101, providing an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to set an interrupt flag in the interrupt flag bit register corresponding to the Guest OS in the shared memory, the shared memory is real-time embedded virtualization The physical memory that the component Hypervisor shares with at least one Guest OS and is used to record interrupt flags.

In the embodiment of the present invention, the Guest OS is a virtualized operating system. The difference between this type of operating system and the general operating system is that not only one such virtualized operating system or one such virtualized operating system 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 runs on the real-time embedded virtualization component Hypervisor on the hardware layer. As shown in Figure 2, it is a single physical CPU Schematic diagram of a scenario where multiple Guest OSs run on a CPU and a single Guest OS runs on multiple physical CPUs. For example, Guest OS ₀ and Guest OS ₁ run on physical CPU ₀ (Core ₀ ) through the hypervisor, while Guest OS _n runs on physical CPU ₁ (Core ₁ ), physical CPU ₂ (Core ₂ ) and physical CPU _n ( Core _n ).

Unlike the prior art that disables interrupts through the communication method of interrupt notification (Hyper Call), in the embodiment of the present invention, the real-time embedded virtualization component Hypervisor provides a layer of intermediate addresses, and this intermediate address is managed by a shadow page table; The Guest OS establishes the mapping from the Guest OS to the intermediate address and the Hypervisor establishes the mapping from the intermediate address to the physical memory address. 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 Layer 2 address mapping. The role of the first layer of address mapping is that the real-time embedded virtualization component Hypervisor can perceive the physical memory requirements of all Guest OSs on the real-time embedded virtualization component Hypervisor and manage them uniformly. The role of the second layer of address mapping is that the real-time embedded The component hypervisor can divide physical memory resources in a planned way according to the physical memory requirements of the Guest OS.

After the first layer address mapping and the second layer address mapping are established, the physical memory shared by the real-time embedded virtualization component Hypervisor and at least one Guest OS and used for recording interrupt flags can be established. In the following description, for the convenience of description, the physical memory shared by the real-time embedded virtualization component Hypervisor and at least one Guest OS and used to record interrupt flags is referred to as "shared memory". Obviously, the shared memory is a part of the physical memory. As shown in FIG. 3 , it is a schematic diagram of establishing a shared memory in the physical memory in the method provided by the embodiment of the present invention. The shared memory can be jointly accessed by the Hypervisor and at least one Guest OS, and the memory spaces shared by different Guest OSs and the Hypervisor in the shared memory are isolated from each other, that is, the memory space shared by any Guest OS and the Hypervisor in the shared memory and The memory space shared by another Guest OS and Hypervisor is isolated from each other. For example, in accompanying drawing 3, the physical memory that Guest OS ₀ shares with Hypervisor and is used for recording interrupt flag is " VM ₀ interrupt flag bit space " in the shared memory, Guest OS ₁ shares with Hypervisor and is used for recording the physical memory of interrupt flag That is, the "VM ₁ interrupt flag space" in the shared memory and the physical memory shared by the Guest OS ₂ and the Hypervisor for recording interrupt flags, that is, the "VM ₂ interrupt flag space" in the shared memory, are isolated from each other.

As an embodiment of the present invention, providing an interface to the virtualized operating system Guest OS so that the Guest OS calls the interface will set the interrupt flag in the shared memory corresponding to the Guest OS interrupt flag bit register can be: real-time embedded The virtualization component Hypervisor provides an interface to the Guest OS so that the Guest OS calls the interface, accesses the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and accesses the intermediate address through the second layer according to the intermediate address. The address mapping accesses the shared memory, and the interrupt flag bit register corresponding to the Guest OS is set with an interrupt flag, for example, using a logic "0" to indicate that the interrupt is turned off, and using a logic "1" to indicate that the interrupt is turned on. It should be noted that since the real-time embedded virtualization component Hypervisor establishes the first-level address mapping and the second-level address mapping, when the Guest OS sets the interrupt flag, although the aforementioned first-level address mapping and real-time embedded The interface provided by the virtualization component Hypervisor accesses the intermediate address, and then finally accesses the shared memory through the second-layer address mapping. However, during the operation of the system, for the Guest OS, it is no different from directly accessing the shared memory, that is, the Guest OS It is considered to directly access the shared memory, and the interrupt flag register corresponding to the Guest OS is set to the interrupt flag.

S102. Check the interrupt flag bit register.

As an embodiment of the present invention, when checking the interrupt flag register, an exception handling function specified by an exception vector may be executed to check the interrupt flag register. Specifically, physical interrupts generated by hardware, such as general-purpose physical interrupts or fast physical interrupts, are first routed to the physical core through the GIC, and the Hypervisor program runs on the physical core, then enters the hypervisor's exception vector table, and jumps to the hypervisor's exception The exception handling function specified by the vector checks the contents of the interrupt flag bit register during the Hypervisor's interrupt handling process.

In the above embodiment of checking the interrupt flag register, the interrupt flag register may be periodically polled according to the clock provided by the real-time embedded virtualization component Hypervisor, that is, the interrupt flag register is actively checked, or The interrupt flag bit register is checked under the trigger of a physical interrupt generated by the hardware, that is, the interrupt flag bit register is passively checked.

S103. If the interrupt flag bit register indicates that the Guest OS needs to disable interrupts, prohibit sending virtual interrupts to the Guest OS.

For example, if a logic "0" is used to indicate that the interrupt is turned off, and a logic "1" is used to indicate that the interrupt is turned on, then it is checked that the content of the interrupt flag bit register is a logic "0", and the physical interruption generated by the hardware is prohibited from being sent to the Guest OS.

It can be seen from the method for disabling interrupts in the virtualization system provided by the above-mentioned embodiments of the present invention that since the real-time embedded virtualization component Hypervisor provides an interface to the virtualization operating system Guest OS, the GuestOS can share the Hypervisor with at least one Guest OS and use it for The physical memory that records the interrupt flag is the interrupt flag bit register corresponding to the Guest OS in the shared memory to set the interrupt flag. Compared with the prior art method of closing the interrupt by providing the communication mode of the interrupt notification, the method provided by the embodiment of the present invention does not rely on the Hypervisor and the Guest OS to compile together, and the Hypervisor does not need to share code segments with the Guest OS; since the virtualization layer and the Guest OS The OS image is separated, and the access to the shared memory is performed through the virtual address. Therefore, the speed of closing/opening the interrupt is fast, and the system operation efficiency is high.

Please refer to FIG. 4 , which is a schematic structural diagram of a device for disabling interrupts in a virtualization system provided by an embodiment of the present invention. For ease of description, only parts related to the embodiments of the present invention are shown. The device for disabling interrupts in the virtualization system illustrated in Figure 4 includes an interface providing module 401, a flag bit checking module 402, and an interrupt cut-off sending module 403, wherein:

The interface providing module 401 is used to provide an interface to the virtualized operating system Guest OS so that the Guest OS calls the interface to set an interrupt flag in the interrupt flag bit register corresponding to the Guest OS in the shared memory, and the shared memory is The real-time embedded virtualization component Hypervisor shares physical memory with at least one Guest OS and is used for recording interrupt flags, wherein different Guest OSs in the shared memory are isolated from memory spaces shared by the Hypervisor.

The flag checking module 402 is used to check the interrupt flag register.

The interrupt cut-off sending module 403 is configured to prohibit sending virtual interrupts to the Guest OS if the flag bit checking module 402 checks the interrupt flag bit register and indicates that the Guest OS needs to disable interrupts.

It should be noted that, in the implementation of the device for disabling interrupts in the above virtualization system, the division of each functional module is only an example. In actual applications, it can be considered according to the needs, such as the configuration requirements of the corresponding hardware or the convenience of software implementation. The above-mentioned function allocation is completed by different functional modules, that is, the internal structure of the cable modem on-line device is divided into different functional modules, so as 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 completed by corresponding software executed by corresponding hardware. For example, the aforementioned interface providing module may be capable of executing the aforementioned virtual The optimized operating system Guest OS provides an interface so that the Guest OS calls the interface and sets the interrupt flag bit register corresponding to the Guest OS in the shared memory. The program thus completes the general processor or other hardware equipment of the aforementioned functions; again, the aforementioned flag bit checking module can be hardware with the function of performing the aforementioned check of the interrupt flag bit register, such as a flag bit checker, and can also be capable of executing A general processor or other hardware device with a corresponding computer program to complete the foregoing functions (the foregoing description principles can be applied to each of the embodiments provided in this specification).

The interface providing module 401 illustrated in FIG. 4 may include an interface calling unit 501 and an interrupt flag setting unit 502. As shown in FIG. 5, another embodiment of the present invention provides an apparatus for disabling interrupts in a virtualization system, wherein:

An interface calling unit 501, configured to provide an interface to the virtualized operating system Guest OS so that the Guest OS calls the interface;

The interrupt flag setting unit 502 is used for accessing the intermediate address through the first layer address mapping according to the intermediate address information provided by the interface, and interrupting the corresponding interrupt of the Guest OS according to the intermediate address and through the second layer address mapping The flag bit register sets the interrupt flag, the first layer of address mapping is the mapping of the Guest OS to the intermediate address, and the second layer of address mapping is the mapping of the intermediate address to the physical memory address, and the physical memory includes all described shared memory.

The device for disabling interrupts in the virtualization system illustrated in Fig. 4 or Fig. 5 may also include a mapping establishment module 601 and a shared memory establishment module 602, as shown in Fig. 6a or Fig. 6b, the virtualization system provided by another embodiment of the present invention A device for disabling interrupts in the system, where:

A mapping establishment module 601, configured to establish a mapping from the Guest OS to an intermediate address and a mapping from the intermediate address to a physical memory address.

A shared memory establishment module 602, configured to establish the shared memory, in which different Guest OSs and the memory space shared by the Hypervisor are isolated from each other.

The flag checking module 402 shown in Figure 4 can periodically poll the interrupt flag register according to the clock provided by the real-time embedded virtualization component Hypervisor, or check the interrupt flag register triggered by a physical interrupt generated by the hardware. Interrupt flag bit register. The flag bit checking module 402 may include a first execution unit 701, as shown in FIG. 7, an apparatus for disabling interrupts in a virtualization system provided by another embodiment of the present invention,

The execution unit 701 is configured to execute the exception handling function specified by the exception vector to check the interrupt flag bit register. Specifically, physical interrupts generated by hardware, such as general-purpose physical interrupts or fast physical interrupts, are first routed to the physical core through the GIC, and the Hypervisor program runs on the physical core, then enters the hypervisor's exception vector table, and jumps to the hypervisor's exception The exception handling function specified by the vector, during the interrupt handling process of the Hypervisor, the execution unit 701 executes the exception handling function specified by the exception vector in the exception vector table to check the content of the interrupt flag bit register.

It should be noted that the information interaction and execution process between the modules/units of the above-mentioned device are based on the same idea as the method embodiment of the present invention, and the technical effect it brings is the same as that of the method embodiment of the present invention. The specific content can be Refer to the descriptions in the method embodiments of the present invention, and details are not repeated here.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, such as one or more or all of the following various methods:

Provide an interface to the virtualization operating system Guest OS so that the Guest OS calls the interface to set an interrupt flag in the interrupt flag bit register corresponding to the Guest OS in the shared memory, and 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;

Check the interrupt flag bit register;

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

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the storage medium can include: Read Only Memory (ROM, Read Only Memory), Random Access Memory (RAM, Random Access Memory), disk or CD, etc.

The method and device for disabling interrupts in the virtualization system provided by the embodiments of the present invention are described above in detail. In this paper, specific examples are used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only used to help understanding The method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be construed as a limitation of the invention.

Claims (10)

1. close the method for interruption in the virtualization system, it is characterized in that said method comprises:

To virtualizing operating systems Guest OS interface is provided so that said Guest OS call said interface with shared drive in the interrupt identification bit register corresponding with said Guest OS interrupt identification is set; Said shared drive is the physical memory that real-time embedded virtual member Hypervisor and at least one Guest OS share and be used to write down interrupt identification, and different Guest OS and the shared memory headrooms of said Hypervisor isolated mutually in the said shared drive;

Check said interrupt identification bit register;

If said interrupt flag bit register shows that said Guest OS need close interruption, then forbid sending virtual interruption to said Guest OS.

2. the method for claim 1; It is characterized in that; Said to virtualizing operating systems Guest OS interface is provided so that said Guest OS call said interface with shared drive in the interrupt identification bit register corresponding with said Guest OS interrupt identification is set, comprising:

Interface is provided so that said Guest OS calls said interface to virtualizing operating systems Guest OS;

The intermediate address information that provides according to said interface; Through ground floor map addresses visit intermediate address; Visit said shared drive according to said intermediate address and through second layer map addresses, the interrupt identification bit register corresponding with said Guest OS is provided with interrupt identification.

3. method as claimed in claim 2 is characterized in that, said to virtualizing operating systems Guest OS interface is provided so that said Guest OS with shared drive in the interrupt identification bit register corresponding with said Guest OS be provided with and also comprise before the interrupt identification:

Set up Guest OS to the mapping of intermediate address and the mapping of said intermediate address to physical memory addresses;

Set up said shared drive.

4. the method for claim 1 is characterized in that, the said interrupt identification bit register of said inspection comprises:

The clock that provides according to said Hypervisor, the periodically said interrupt identification bit register of poll; Perhaps

Under the triggering of the physical discontinuity that hardware produces, check said interrupt identification bit register.

5. method as claimed in claim 4 is characterized in that, the said interrupt identification bit register of said inspection comprises:

The abnormality processing function of execute exception vector appointment is to check said interrupt identification bit register.

6. close the device of interruption in the virtualization system, it is characterized in that said device comprises:

Interface provides module; Be used for interface being provided and interrupt identification be set so that said Guest OS calls the said interface interrupt identification bit register that shared drive is corresponding with said Guest OS to virtualizing operating systems Guest OS; Said shared drive is the physical memory that real-time embedded virtual member Hypervisor and at least one Guest OS share and be used to write down interrupt identification, and Guest OS and the shared memory headrooms of said Hypervisor different in the said shared drive are isolated mutually;

Zone bit inspection module is used to check said interrupt identification bit register;

The interrupt holdoff sending module is used for then forbidding sending virtual interruption to said Guest OS if the said interrupt flag bit register of said zone bit inspection module check shows that said Guest OS need close interruption.

7. device as claimed in claim 6 is characterized in that, said interface provides module to comprise:

The interface interchange unit is used for interface being provided so that said Guest OS calls said interface to virtualizing operating systems Guest OS;

Interrupt identification is provided with the unit; Be used for the intermediate address information that provides according to said interface; Through ground floor map addresses visit intermediate address; Visit said shared drive according to said intermediate address and through second layer map addresses, the interrupt identification bit register corresponding with said Guest OS is provided with interrupt identification.

8. like claim 6 or 7 described devices, it is characterized in that said device also comprises:

Module is set up in mapping, is used to set up Guest OS to the mapping of intermediate address and the mapping of said intermediate address to physical memory addresses;

Shared drive is set up module, is used to set up said shared drive.

9. device as claimed in claim 6 is characterized in that, the clock that said zone bit inspection module provides according to said Hypervisor, the periodically said interrupt identification bit register of poll; Perhaps

Zone bit inspection module is checked said interrupt identification bit register under the triggering of the physical discontinuity that hardware produces.

10. device as claimed in claim 9 is characterized in that, said zone bit inspection module comprises:

Performance element, the abnormality processing function that is used for the appointment of execute exception vector is to check said interrupt identification bit register.

Images