A lightweight virtualization implementation method and device

Abstract

The present invention provides a lightweight virtualization implementation method and device, which belongs to the field of virtualization technology. The solution reduces dependence on hardware resources by reusing existing operating systems, simplifies the complexity of virtualization, and directly uses the hardware isolated by hardware for virtual machines, ensuring the high real-time performance of each virtual machine. From the user's perspective, the solution treats the entire virtualization process as an application of the current operating system. After starting virtualization, no resource consumption is increased, thereby achieving sufficient lightweight and reducing performance requirements. At the same time, the solution directly uses hardware resources for clients through hardware isolation, thereby ensuring the real-time requirements of clients and being able to directly run various real-time operating systems.

Description

Technical Field

[0001] The present invention belongs to the technical field of virtualization, and in particular relates to a lightweight virtualization implementation method and device. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] Traditional virtualization solutions were born from Intel's x86 architecture and can be divided into two architecture types: Type I (bare metal architecture) and Type II (host architecture). They are mainly used in high-performance computing fields such as personal computers and servers with high computing performance.

[0004] Traditional virtualization solutions have the following drawbacks: They have high requirements for device performance, making them difficult to apply to resource-limited embedded environments, and even making it impossible to fully implement traditional virtualization architecture solutions in limited resource environments. Because the client system (i.e., the operating system running inside the virtual machine) cannot directly use hardware resources, it must communicate with the hardware through the VMM (Virtual Machine Monitor). In particular, the Type II architecture requires the host client to communicate with the hardware on the basis of the VMM. Therefore, the real-time performance of each virtual machine cannot be guaranteed, making it difficult to apply to environments with real-time requirements. It is usually difficult for the client to directly run various real-time operating systems or bare-metal programs. Summary of the Invention

[0005] The embodiments of the present invention provide a lightweight virtualization implementation method and device to solve the problems that existing virtualization solutions cannot be applied in resource-constrained environments, the real-time performance of virtual machines cannot be guaranteed, and real-time operating systems or bare metal programs cannot be directly run.

[0006] According to a first aspect of an embodiment of the present invention, a lightweight virtualization implementation method is provided, which is applied to a device deployed with a pre-built user interaction tool, a system driver, and a virtual machine management firmware, including:

[0007] In response to enabling the virtualization function, loading a client configuration file through a pre-built user interaction tool; wherein the user interaction tool runs on a primary client operating system; the client configuration file includes hardware resources allocated to the primary client and a plurality of sub-clients, and shared memory declarations for communication between the clients;

[0008] Based on configuration information in the client configuration file, the virtual machine management firmware is controlled by system calls to isolate physical hardware resources of each client and provide each client with shared memory for inter-client communication, thereby enabling creation of clients and communication between clients; wherein the virtual machine management firmware runs in memory;

[0009] When the virtualization function is enabled, the main client and the sub-client are both virtual machines; when the virtualization function is disabled, the main client is an independent operating system.

[0010] Furthermore, the method directly provides hardware resources used by the client through hardware isolation.

[0011] Furthermore, the virtual machine management firmware is controlled through system calls to isolate the physical hardware resources of each client. Specifically, a system call is made through a user interaction tool, the system call generates a hyper call through the system driver, the virtual machine management firmware is loaded into the memory through the hyper call to run, and the physical hardware is isolated to different clients through the loaded virtual machine management firmware.

[0012] Furthermore, the shared memory adopts a one-to-one model, and communication between any two clients is achieved by jointly declaring an independent shared memory.

[0013] Furthermore, the virtual machine management firmware operates at a specific processor privilege level. For the x86 architecture, the virtual machine management firmware operates at the kernel state privilege level of the root mode; for the ARM architecture, the virtual machine management firmware operates at the virtualization mode privilege level; for the RISC-V architecture, the virtual machine management firmware operates at the virtual machine monitor mode privilege level.

[0014] Furthermore, the virtual machine management firmware specifically performs the following processing: receiving configuration information and commands from the driver, and then processing them according to the command type, wherein:

[0015] For enable and create commands, the corresponding CPU state is initialized according to the received configuration information, and the corresponding memory page table is created to implement memory and CPU resource allocation and hardware isolation for different clients, and the configuration information of each client is managed through a linked list;

[0016] For disable, delete, modify and query commands, corresponding processing is performed by querying the configuration information of the corresponding client and the processing results are returned.

[0017] Furthermore, the user interaction tool specifically performs the following processing:

[0018] Receive user command input;

[0019] When the command input is an enable or create command, read and parse the preset configuration file, and send the parsing result and the corresponding command to the system driver to perform corresponding processing, and receive the processing result and display it;

[0020] When the command input is a disable, delete or view command, the command is directly sent to the system driver to perform corresponding processing, and the processing result is received and displayed.

[0021] Furthermore, the system driver specifically performs the following processing: receiving configuration information and commands from the user interaction tool; for enable and create commands, copying the content of the configuration information from the user space to the system space, and after verification, sending the verified configuration information and corresponding commands to the virtual machine management firmware for processing and returning the results; and, after successfully isolating the hardware resources, creating a corresponding maintenance node in the pre-built management linked list, and mapping the maintenance node back to the main client, so that the main client can maintain other clients; for query commands, finding the corresponding client information by directly traversing the existing management linked list, and then returning it to the user interaction tool.

[0022] Furthermore, the client runs an operating system including Linux, Android, Windows, a real-time operating system, and a bare-metal program.

[0023] According to a second aspect of an embodiment of the present invention, a lightweight virtualization device is provided, comprising a hardware module and a software module, wherein the hardware module comprises a CPU, memory, and IO devices; the software module comprises a host-client operating system, a user interaction tool, a system driver, and a virtual machine management firmware, and a lightweight virtualization implementation method as described above is executed based on the software module.

[0024] One or more of the above technical solutions have the following beneficial effects:

[0025] The present invention provides a lightweight virtualization implementation method and device. The solution reduces dependence on hardware resources by reusing existing operating systems (i.e., host-client operating systems), simplifies the complexity of virtualization, and directly uses the hardware isolated by hardware for virtual machines, ensuring high real-time performance of each client (i.e., virtual machine). From the user's perspective, the solution of the present invention treats the entire virtualization process as an application of the current operating system. After starting virtualization, no additional resource consumption is added, thereby achieving sufficient lightweightness and reducing performance requirements. The solution of the present invention directly provides hardware resources for the client through hardware isolation, thereby ensuring the real-time requirements of the client and being able to directly run various real-time operating systems. The advantages of the additional aspects of the present invention will be partially given in the description below, and partially will become apparent from the description below, or will be understood through the practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0027] Figure 1 Schematic diagram of the overall framework of a lightweight virtualization implementation method described in an embodiment of the present invention;

[0028] Figure 2 A basic flow chart of a lightweight virtualization implementation method described in an embodiment of the present invention;

[0029] Figure 3 This is a schematic diagram of an example of running the virtualization method described in an embodiment of the present invention;

[0030] Figure 4 These are the privilege levels corresponding to the virtual machine management firmware of different hardware platforms described in the embodiments of the present invention. DETAILED DESCRIPTION

[0031] It should be noted that the following detailed descriptions are exemplary and intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which the present invention belongs.

[0032] It should be noted that the terms used herein are for describing particular embodiments only and are not intended to limit the exemplary embodiments according to the present invention.

[0033] In the absence of conflict, the embodiments of the present invention and the features thereof may be combined with each other.

[0034] like Figure 1 and Figure 2As shown, the purpose of this embodiment is to provide a lightweight virtualization implementation method. The implementation of the method is based on a pre-built user interaction tool, a system driver, and a virtual management firmware, and specifically includes the following processing procedures:

[0035] Step 1: In response to enabling the virtualization function, a client configuration file is loaded through a pre-built user interaction tool; wherein the user interaction tool runs on a primary client operating system; the client configuration file includes hardware resources allocated to the primary client and a plurality of sub-clients, and shared memory declarations for communication between the clients;

[0036] The user interaction tool serves as a human-computer interaction interface for users to manage virtual machines (ie, clients). The user interaction tool enables users to view the status of existing virtual machines, create new virtual machines, delete existing virtual machines, and other functions.

[0037] The user interaction tool is essentially an ordinary application in the main client operating system, which is used to load the client configuration file provided by the user. Considering the permission restrictions of the operating system, most of its commands need to be sent to the system driver through system calls to implement.

[0038] In specific implementation, Figure 3 As shown, the user enables or disables the virtualization function by executing specific commands using a user interaction tool in the main guest operating system. After the user enables the virtualization function, the virtual machine management firmware automatically isolates the current system into a virtualized environment; after the user turns off the virtualization function, the user can restore to the original system.

[0039] In the virtualization result of the solution described in this embodiment, the virtual machine includes a main client and several sub-clients, wherein the main client serves as the virtualization management center, and its overall architecture is as follows: Figure 1 When virtualization is not enabled, only the main client is running, and the main client becomes an independent operating system, as shown in Figure 3 When virtualization needs to be enabled, the following needs to be executed in the host client: Figure 2 Related operations shown.

[0040] Compared with Type II, in the solution described in this embodiment, the main client is essentially also a virtual machine, while the Host OS main client of Type II is not a virtual machine; compared with Type I, the main client and sub-client of the solution described in this embodiment can directly access hardware resources, while the client of Type I needs to go through the VMM to access the hardware.

[0041] User interaction tools, system drivers, and virtual machine management firmware are all independently usable executable programs. Due to the design of modern CPU instruction set architectures, various operations are divided into different permission levels. Therefore, operations with different permissions are handled separately by these executable programs.

[0042] In the specific implementation, the main client is used for the entire virtualization management. Therefore, it is necessary to install the user interaction tool, system driver, and virtual machine management firmware on the main client to manage the virtual machine. Figure 2 shown.

[0043] It should be noted that virtualization management can be performed on any client, but to reduce complexity, the solution described in this embodiment limits management operations to sub-clients. It is understandable that in more implementations, virtualization management can also be performed on sub-clients other than the main client, which will not be described in detail here.

[0044] In one or more implementations, the virtualization implementation scheme described in this embodiment supports three mainstream chip instruction set architectures: x86, ARM, and RISC-V. FIG4 illustrates the operational locations of the user interaction tool, system driver, and virtual machine management firmware in these three chip instruction set architectures. It should be noted that in each of these three chip instruction set architectures, the user interaction tool, system driver, and virtual machine management firmware only have permission to perform corresponding operations when running at the corresponding privilege level.

[0045] This virtualization method can be deployed directly on a hardware device and also supports the reuse of the device's existing operating system.

[0046] After virtualization is started, the user can use the corresponding commands of the user interaction tool in the main client operating system to perform operations such as creating a new client, viewing the status of existing clients, or deleting unnecessary clients, such as Figure 4 As shown, a specific instance after creating a new client is shown.

[0047] In the solution described in this embodiment, the entire virtualization implementation solution is based on the existing operating system of the device, and the management of all client machines is performed entirely in the master client.

[0048] In a specific implementation, the user interaction tool specifically performs the following processing:

[0049] Receive user command input;

[0050] When the command input is an enable or create command, read and parse the preset configuration file, and send the parsing result and the corresponding command to the system driver to perform corresponding processing, and receive the processing result and display it;

[0051] When the command input is a disable, delete or view command, the command is directly sent to the system driver to perform corresponding processing, and the processing result is received and displayed.

[0052] Specifically, the user interaction tool is an executable program in the user space for human-computer interaction, which provides commands such as enable, disable, create, delete, and view for virtualization management.

[0053] For enabling and creating commands, the system reads and parses the contents of the configuration file, performs preliminary verification on the format of the parsed content and the legitimacy of the configuration items, then sends the verified content to the system driver, receives the return result from the system driver, and displays the return result to the user. The configuration file is essentially a user-readable and writable text file that records the hardware resources required by the virtual machine, such as memory, CPU, various peripherals, and shared memory declarations for communication between different virtual machines.

[0054] For sub-commands such as disable, delete, and view, it directly sends the corresponding command to the driver, waits for the driver to return the corresponding result, and then displays the returned result to the user;

[0055] It should be noted here that since virtualization operations are privileged operations, and user interaction tools are essentially user-mode tools, they do not have virtualization permissions (the permission levels of different architectures are as follows Figure 4 As shown in Figure 2), all its operations must be handled by the system driver through system calls. The above reason is that the chip instruction set architecture design does not allow the user space privilege level to directly switch to the virtual machine management privilege level, such as Figure 4 As shown, the user interaction tool, system driver, and virtual machine management firmware in the solution described in this embodiment correspond to three different privilege levels: user privilege level, system privilege level, and virtual machine privilege level, respectively.

[0056] Step 2: Based on the configuration information in the client configuration file, the virtual machine management firmware is controlled through system calls to isolate the physical hardware resources of each client and provide each client with a shared memory for inter-client communication, thereby enabling client creation and communication between clients; wherein the virtual machine management firmware runs in the memory;

[0057] When the virtualization function is enabled, the main client and the sub-client are both virtual machines; when the virtualization function is disabled, the main client is an independent operating system.

[0058] In a specific implementation, the physical hardware resources of different clients are isolated by controlling the virtual machine management firmware through system calls, specifically: a system call is made through a user interaction tool, the system call generates a hyper call through the system driver, the virtual machine management firmware is loaded into the memory through the hyper call and runs, and the physical hardware is isolated to different clients through the loaded virtual machine management firmware.

[0059] Among them, the system driver is used to load the virtual machine management firmware and respond to interactive commands from user interaction tools. It also manages and maintains the basic information of each client. The system driver is the kernel module of the operating system and is loaded into the operating system kernel by the user. For virtualization-related processing, it requires a special privilege level. Therefore, some commands need to be sent to the virtual machine management firmware through hypercalls to implement.

[0060] Furthermore, the system driver specifically performs the following processing:

[0061] Receive configuration information and commands from the user interaction tool;

[0062] For enable and create commands, the content of the configuration information is copied from the user space to the system space. After verification, the verified configuration information and corresponding commands are sent to the virtual machine management firmware.

[0063] Specifically, the configuration information or command received from the user interaction tool is verified;

[0064] After verification is completed, for enable and create commands, the configuration information content is copied from user space to system space, and then the configuration information version, identifier, and availability of description resources are further verified. After the verification passes, the configuration information of each client is managed in the form of a linked list;

[0065] The verified configuration information is then sent to the virtual machine management firmware, which allocates hardware resources to each client and performs hardware isolation operations based on the configuration information. It should be noted that for the create, enable, and disable commands, the corresponding operations require higher permissions (see the permission levels for different architectures). Figure 4 ), therefore, the driver will load the virtual machine management firmware into memory for execution, and then send certain privileged operations to the virtual machine management firmware through hypercalls for processing and return the results.

[0066] After successfully isolating the hardware resources, the system driver also needs to create a corresponding maintenance node and map the maintenance node back to the primary client so that the primary client can maintain other clients.

[0067] For query commands, the existing management linked list can be directly traversed to find the corresponding client information, and then returned to the user interaction tool.

[0068] In specific implementations, the virtual machine management firmware is used to isolate physical hardware resources to different clients, ensuring that different clients only use their own visible hardware resources. The virtual machine management firmware is essentially a special binary code that is loaded into memory and run by the system driver.

[0069] In the specific implementation, the hardware isolation function of the virtual machine management firmware is the core of the entire virtualization solution. It implements the hardware isolation function by using the hardware virtualization features provided by the processor. Therefore, the implementation method varies for different hardware platforms. Figure 4 As shown, the virtual machine management firmware operates at a specific processor privilege level. For the x86 architecture, the virtual machine management firmware operates at the kernel state Ring0 privilege level in the root mode; for the ARM architecture, the virtual machine management firmware operates at the virtualization mode EL2 privilege level; for the RISC-V architecture, the virtual machine management firmware operates at the hypervisor mode privilege level.

[0070] In a specific implementation, the virtual machine management firmware is used to receive configuration information and commands from the system driver; for enable and create commands, it allocates hardware resources to different clients and isolates hardware based on the configuration information; wherein, the configuration information of each client is managed in the form of a linked list; for disable, delete, modify, and query commands, it traverses the linked list to determine the client to be operated, and performs corresponding processing on the corresponding client;

[0071] Specifically, the virtual machine management firmware is essentially an executable program that receives configuration information and commands from the driver and then processes them according to the command type.

[0072] For enable and create commands, the corresponding CPU state is initialized according to the received configuration information, and the corresponding memory page table is created to implement memory and CPU resource allocation and hardware isolation for different clients, and the configuration information of each client is managed through a linked list;

[0073] For example, taking memory isolation as an example, through the extended page table or nested page table technology supported by the processor's hardware virtualization features, the virtual machine management firmware can directly set the memory mapping of the virtual machine to ensure that each virtual machine can only access its own memory space without going through the system driver.

[0074] It is understandable that the allocation of hardware resources and hardware isolation, in addition to memory and CPU, can also include other hardware devices such as I / O devices, storage devices, graphics cards, etc.

[0075] It should be noted that when a new guest is created or deleted, the virtual machine management firmware will synchronize updates across all existing virtual machines. This is because when performing hardware isolation, the virtual machine management firmware needs to suspend all other guests to ensure security and reliability.

[0076] For commands such as disable, delete, modify, and query, the virtual machine management firmware traverses the linked list to query the configuration information of the corresponding client, performs corresponding processing, and returns the processing results.

[0077] In further embodiments, the virtual machine management firmware is further configured to manage shared memory between the clients for communication between the clients, wherein the shared memory is defined in a configuration file of each client.

[0078] Furthermore, when creating a client, the virtual machine management firmware only initializes the resources that the client can use according to the configuration information in the configuration file. When the client accesses non-isolated resources, an exception will be generated.

[0079] In a specific implementation, the virtual machine management firmware also provides shared memory for communication between different clients. The shared memory adopts a one-to-one model, that is, when any two clients communicate, they need to jointly declare a shared memory for communication.

[0080] Specifically, the shared memory in the solution described in this embodiment is defined by the configuration files corresponding to the respective clients. When two clients define the same shared memory in the configuration files, the two clients can communicate via the shared memory.

[0081] It should be noted here that although Type I and Type II architectures also have shared memory, their shared memory is directly defined by the VMM, and users need to configure the VMM to implement shared memory.

[0082] The shared memory configuration described in this embodiment can meet the following application requirements:

[0083] The master client typically runs a non-real-time operating system, while the other clients run real-time operating systems. In such applications, the master client serves as the user interface and handles most tasks, while real-time tasks are handled by the clients running real-time operating systems. In this case, configuration information and processing results are communicated between the clients. For example, in industrial control, the master client provides the user interface, while the clients running real-time operating systems handle various real-time industrial control tasks. Control parameters and results need to be shared with the master client for easy user viewing.

[0084] Furthermore, the shared memory configuration described in this embodiment also allows different clients to share the same device.

[0085] In one or more implementations, the system running on the client can be a traditional Linux, Android or other system, or various real-time operating systems. At the same time, since the solution described in this embodiment is a direct physical resource isolation, bare metal programs can also be run directly.

[0086] In one or more embodiments, a lightweight virtualization device is provided, comprising a hardware module and a software module, wherein the hardware module comprises a CPU, memory, and IO devices; the software module comprises a host-client operating system, a user interaction tool, a system driver, and a virtual machine management firmware, and a lightweight virtualization implementation method as described above is executed based on the software module.

[0087] In a specific implementation, when an operating system already exists on a device, the existing operating system can be directly reused as the main client, and the user interaction tools, drivers and virtual machine management firmware can be installed as a toolkit into the existing operating system for use.

[0088] When there is no operating system on the device, pre-built user interaction tools, drivers, virtual machine management firmware and client configuration files can be packaged into the device, and then the current virtualization solution can be directly deployed through the system installation tool. After deployment, a structure of a main client and multiple client systems is formed.

[0089] In this embodiment, whether directly deploying or reusing an existing operating system, the user needs to manage all clients (including adding, deleting, modifying, and checking) and enable or disable the virtualization function in the main client.

[0090] Those skilled in the art will appreciate that the units, i.e., algorithm steps, of the various examples described in conjunction with this embodiment can be implemented using electronic hardware or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0091] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A lightweight virtualization implementation method, characterized in that: It is applied to devices that are deployed with pre-built user interaction tools, system drivers, and virtual machine management firmware, including: In response to enabling the virtualization function, loading a client configuration file through a pre-built user interaction tool; wherein the user interaction tool runs on a primary client operating system; the client configuration file includes hardware resources allocated to the primary client and a plurality of sub-clients, and shared memory declarations for communication between the clients; Based on configuration information in the client configuration file, the virtual machine management firmware is controlled by system calls to isolate physical hardware resources of each client and provide each client with shared memory for inter-client communication, thereby enabling creation of clients and communication between clients; wherein the virtual machine management firmware runs in memory; When the virtualization function is enabled, the main client and the sub-client are both virtual machines; when the virtualization function is disabled, the main client is an independent operating system.

2. A lightweight virtualization implementation method according to claim 1, characterized in that: The method directly provides hardware resources used by the client through hardware isolation.

3. A lightweight virtualization implementation method according to claim 1, characterized in that: The method of isolating the physical hardware resources of each client by controlling the virtual machine management firmware through system calls is specifically as follows: a system call is made through a user interaction tool, the system call generates a hyper call through a system driver, the virtual machine management firmware is loaded into the memory through the hyper call and runs, and the physical hardware is isolated to different clients through the loaded virtual machine management firmware.

4. A lightweight virtualization implementation method according to claim 1, characterized in that: The shared memory adopts a one-to-one model, and communication between any two clients is achieved by jointly declaring an independent shared memory.

5. A lightweight virtualization implementation method according to claim 1, characterized in that: The virtual machine management firmware operates at a specific processor privilege level. For the x86 architecture, the virtual machine management firmware operates at the kernel state privilege level of the root mode; for the ARM architecture, the virtual machine management firmware operates at the virtualization mode privilege level; for the RISC-V architecture, the virtual machine management firmware operates at the virtual machine monitor mode privilege level.

6. A lightweight virtualization implementation method according to claim 1, characterized in that: The virtual machine management firmware specifically performs the following processing: receiving configuration information and commands from the driver, and then processing them according to the command type, wherein: For enable and create commands, the corresponding CPU state is initialized according to the received configuration information, and the corresponding memory page table is created to implement memory and CPU resource allocation and hardware isolation for different clients, and the configuration information of each client is managed through a linked list; For disable, delete, modify and query commands, corresponding processing is performed by querying the configuration information of the corresponding client and the processing results are returned.

7. A lightweight virtualization implementation method according to claim 1, characterized in that: The user interaction tool specifically performs the following processing: Receive user command input; When the command input is an enable or create command, read and parse the preset configuration file, and send the parsing result and the corresponding command to the system driver to perform corresponding processing, and receive the processing result and display it; When the command input is a disable, delete or view command, the command is directly sent to the system driver to perform corresponding processing, and the processing result is received and displayed.

8. The lightweight virtualization implementation method according to claim 1, wherein: The system driver specifically performs the following processing: receiving configuration information and commands from the user interaction tool; for enable and create commands, copying the content of the configuration information from the user space to the system space, and after verification, sending the verified configuration information and corresponding commands to the virtual machine management firmware for processing and returning the results; And, after the hardware resources are successfully isolated, a corresponding maintenance node is created in the pre-built management chain table, and the maintenance node is mapped back to the main client, so that the main client can maintain other clients; For query commands, the corresponding client information is found by directly traversing the existing management linked list and then returned to the user interaction tool.

9. The lightweight virtualization implementation method according to claim 1, wherein: The client operating system types include Linux, Android, Windows, real-time operating systems, and bare metal programs.

10. A lightweight virtualization device, characterized in that: The invention comprises a hardware module and a software module, wherein the hardware module comprises a CPU, memory and IO devices; the software module comprises a host-client operating system, a user interaction tool, a system driver and a virtual machine management firmware; and a lightweight virtualization implementation method as described in any one of claims 1 to 9 is executed based on the software module.

Images