KR102199509B1 - Memory sharing system, method, and program for performing for sharing memory in virtualization system - Google Patents

Abstract

Provided is a memory sharing method. The memory sharing method comprises: a step of receiving an access request to a virtual device from an application; a step of checking the access right of the application; a step of converting virtual address information into intermediate address information according to page table information; a step of converting the intermediate address information into physical address information; and a step that the application accesses the memory. Therefore, the memory can be shared by generating the virtual device with a shared memory.

Description

Memory sharing system and method for sharing memory in a virtualization system, and a recording medium recording a program to perform it {MEMORY SHARING SYSTEM, METHOD, AND PROGRAM FOR PERFORMING FOR SHARING MEMORY IN VIRTUALIZATION SYSTEM}

The present invention relates to a memory sharing system and method for sharing memory in a virtualization system, and to a recording medium recording a program for performing the same, and more particularly, to a system for sharing memory by creating a virtual device having a shared memory , A method, and a recording medium recording a program for performing the same.

Virtualization technology is applied and used in various fields such as server devices, desktop computers, and cloud computing. In this virtualization technology, a host in which an operating system is directly installed in hardware and a guest installed in the host through virtualization technology exist. In this case, a hypervisor for executing the guest is required.

For example, Linux realizes virtualization in the KVM (Kernel-based Virtual Machine) method, and in the KVM method, the guest operates in the same form as the host module.

Meanwhile, in such a virtualization system, in general, a host and a guest operate independently, and a guest's authority to hardware is operated at a lower level than that of the host.

Accordingly, it is difficult for the guest to secure a memory space that can be shared with the host.

The technical problem to be solved by the present invention is to provide a system, a method for sharing a memory by creating a virtual device having a shared memory, and a recording medium in which a program for performing the same is recorded.

One aspect of the present invention is a memory sharing method using a memory sharing system including a host unit and a guest unit installed as a virtual operating system on the host unit, receiving a request for access to a virtual device from an application installed in the guest unit step; Checking access rights of the application to the virtual device; Converting virtual address information for the virtual device into individual address information according to page table information previously stored in the guest unit when access of the application to the virtual device is permitted; Converting the respective address information into physical address information used in a host unit; And accessing, by the application, a memory according to the physical address information.

In addition, the virtual device may include a shared memory in which an application executed in at least one element of the host unit and the guest unit can be accessed.

In addition, the shared memory may be allocated a memory capacity of a preset size from a memory of hardware running the host unit.

In addition, when a virtual device for an access request received from the application does not exist, generating a virtual device according to the access request; It may further include the step of granting the access right of the application to the virtual device.

In addition, the access right may be changed by the host unit according to a request of an application that has access right to the virtual device.

In addition, the access right may be set differently for a plurality of different applications executed in at least one element of the host unit and the guest unit.

Another aspect of the present invention is a computer-readable recording medium having a computer program recorded thereon for performing the memory sharing method according to any one of claims 1 to 6.

Another aspect of the present invention is a host unit installed in hardware; A guest unit installed as a virtual operating system on the host unit; And receiving an access request for a virtual device from an application installed in the guest unit, checking access rights of the application to the virtual device, and when access to the virtual device is permitted, the application is It may include a kernel unit that transmits the access path to the virtual device.

In addition, when the virtual device for the access request received from the application does not exist, the kernel unit may request the host unit to generate a virtual device according to the access request.

In addition, the guest unit may convert virtual address information on the virtual device into each address information according to page table information previously stored in the guest unit.

In addition, the kernel unit may convert the respective address information into physical address information for hardware on which the host unit is installed according to address data information stored in advance in the kernel unit.

According to one aspect of the present invention described above, by providing a memory sharing system and a method for sharing memory in a virtualization system, and a recording medium in which a program for performing the same is recorded, a virtual device having a shared memory is created to share the memory. can do.

1 is a schematic diagram of a memory sharing system according to an embodiment of the present invention.
Fig. 2 is a schematic diagram showing the host unit of Fig. 1;
Fig. 3 is a schematic diagram showing the guest portion of Fig. 1;
Fig. 4 is a schematic diagram showing the kernel unit of Fig. 1;
5 is a schematic diagram illustrating a memory sharing method according to an embodiment of the present invention.
6 is a flowchart of a memory sharing method according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION The detailed description of the present invention described below refers to the accompanying drawings, which illustrate specific embodiments in which the present invention may be practiced. These embodiments are described in detail sufficient to enable a person skilled in the art to practice the present invention. It is to be understood that the various embodiments of the present invention are different from each other but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the present invention in relation to one embodiment. In addition, it is to be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description to be described below is not intended to be taken in a limiting sense, and the scope of the present invention, if properly described, is limited only by the appended claims, along with all scopes equivalent to those claimed by the claims. Like reference numerals in the drawings refer to the same or similar functions over several aspects.

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the drawings.

1 is a schematic diagram of a memory sharing system according to an embodiment of the present invention.

The memory sharing system 1 may include a hardware 100, a host unit 200, a guest unit 300, a kernel unit 400, and a virtual device 500.

The hardware 100 includes at least one command of processing, control, storage, and communication for real data according to commands executed by the host unit 200, the guest unit 300, the kernel unit 400, and the virtual device 500. Can be done.

To this end, the hardware 100 may include at least one of a processing device, a storage device, a communication device, an input device, an output device, and a power device.

For example, the hardware 100 is a personal computer, such as a central processing unit (CPU), a motherboard, a RAM (Random Access Memory), a storage drive (SSD: Solid State Drive and HDD: Hard Disk Drive), a graphic card, a power supply, a keyboard, a mouse, a monitor, and the like.

Accordingly, the hardware 100 may receive information such as data and commands, and the hardware 100 may store the received information in the hardware 100.

Further, the hardware 100 may process, modify, delete, register, and store data according to a command input from the outside or stored in advance.

In addition, the hardware 100 may output data processing and processing results to the outside, and the hardware 100 may transmit or receive such data between respective elements of the hardware 100.

The host unit 200 may be understood as an operating system directly installed on the hardware 100. Accordingly, the host unit 200 may include a plurality of software that performs different operations so that the user can conveniently process data and control the hardware 100.

Here, the software is included in a specific hardware 100, and the hardware 100 includes a command required to perform an arbitrary operation, and a command required to manage and control the hardware 100 It may further include a system software (System Software) and application software (Application Software) for performing a task set in advance according to the purpose of the software.

For example, the operating system may include Windows, macOS, Ubuntu, and Linux.

The guest unit 300 may be understood as an operating system virtually installed on the host unit 200.

Here, the virtually installed operating system can be understood as dividing the hardware 100 into logical units through the host unit 200 to install an operating system independent from the host unit 200. In this case, the host unit ( 200) and the operating system installed in the guest unit 300 may be driven in an environment of the hardware 100 having the same elements.

Accordingly, the guest unit 300 may be understood as being installed on a part of the hardware 100 in which the host unit 200 is installed, and the guest unit 300 may be understood as being installed as software on the host unit 200 have.

Meanwhile, the guest unit 300 is an operating system virtually installed on the host unit 200 and includes a plurality of software that performs different operations so that the user can conveniently process data and control the hardware 100. can do.

In addition, it can be understood that the expression of software included in the operating system can be replaced by an application.

The kernel unit 400 may transmit commands such as processing and control generated from an application of the guest unit 300 that are virtually installed in the host unit 200 to the host unit 200.

Accordingly, the host unit 200 may control the hardware 100 according to a control command generated from the guest unit 300 and transmitted through the kernel unit 400.

For example, the kernel unit 400 can be understood as a hypervisor based on a Kernel-based Virtual Machine (KVM), which is a virtualization technology of Linux, and in this regard, the hypervisor transmits commands generated from an operating system installed through virtualization to hardware ( 100) is provided so as to be delivered to an operating system directly installed on the hardware 100, and accordingly, it can be understood that the operating system directly installed on the hardware 100 is provided to control the hardware 100 according to a command transmitted through the hypervisor.

On the other hand, in order to prevent a mixture of words used to describe an embodiment of the present invention, a kernel that transmits commands generated from the operating systems of the host unit 200 and the guest unit 300 to the hardware is omitted. Although it can be understood that, in the implementation of the present invention, the command generated from the operating system of the host unit 200 and the guest unit 300 performs control of the hardware 100 through the kernel of each operating system, or Of course it can be delivered.

In this regard, the hypervisor may operate by being integrated with the kernel of the operating system directly installed on the hardware 100. In this case, the kernel unit 400 is a kernel of the host unit 200 and may control the hardware 100 according to a command received from the guest unit 300.

The kernel unit 400 may request the host unit 200 to generate the virtual device 500. At this time, the host unit 200 may generate the virtual device 500 according to the request of the kernel unit 400, and the host unit 200 may use a portion of the memory space generated by the hardware 100 to be a virtual device ( 500).

The virtual device 500 may include a shared memory representing a portion of a memory space generated from a storage device of the hardware 100.

Accordingly, the guest unit 300 may access the virtual device 500 through the kernel unit 400, and the guest unit 300 may access the shared memory in the virtual device 500.

A detailed description of how the guest unit 300 accesses the virtual device 500 will be described in more detail below.

Fig. 2 is a schematic diagram showing the host unit of Fig. 1;

The host unit 200 may be understood as an operating system installed on the hardware 100, and accordingly, the host unit 200 may execute a command according to the purpose of the application 310 by installing the application 310.

In this case, the host unit 200 may represent an access path for data stored in the memory of the hardware 100 as physical address information 220.

Accordingly, the application 310 executed by the host unit 200 may control data stored in the hardware 100 according to the physical address information 220.

Meanwhile, the host unit 200 may include a management module 210.

The management module 210 may generate the virtual device 500 according to a request for creating a virtual device from the kernel unit 400, and in this case, it may be understood that the virtual device 500 is generated by the host unit 200.

In this case, the management module 210 may manage access rights of the guest unit 300 to the virtual device 500. In this regard, the management module 210 may allow or block access to the virtual device 500 of the guest unit 300, and at this time, the management module 210 is stored in the shared memory of the virtual device 500. You can set access rights for some of the data individually.

At this time, the management module 210 may receive a request for access rights to the virtual device 500 of the guest unit 300 from the kernel unit 400, and accordingly, the management module 210 is the guest unit 300 It is possible to grant access rights to the virtual device 500 of.

Here, the access right represents a qualification that can access the virtual device 500, and in this regard, granting the access right by the management module 210 grants the qualification to allow access to the virtual device 500. Can mean that.

Accordingly, the absence of the access right indicates a lack of qualification to access the virtual device 500, which may mean that the virtual device 500 cannot be accessed. In this case, the guest unit 300 requests access rights to the management module 210 through the kernel unit 400, and is granted access rights from the management module 210 to access the virtual device 500 Can be obtained.

In addition, the management module 210 may manage access rights to the virtual device 500 of an application installed in the host unit 200. In this regard, the management module 210 may allow or block the application's access to the virtual device 500, and at this time, the management module 210 may include some of the data stored in the shared memory of the virtual device 500. You can set access rights for each.

In addition, the management module 210 may set different access rights to the virtual device 500 of an arbitrary application among a plurality of applications installed in the host unit 200.

For example, the management module 210 may set the first application installed on the host unit 200 to access the virtual device 500, and at the same time, the second application installed on the host unit 200 is a virtual device. It can also be set to prevent access to (500).

Fig. 3 is a schematic diagram showing the guest portion of Fig. 1;

The guest unit 300 can be understood as an operating system that is virtually installed on the host unit 200, and accordingly, the guest unit 300 is installed with the application 310 to execute a command according to the purpose of the application 310. I can.

In this case, the guest unit 300 may indicate an access path to data stored in the memory of the hardware 100 through the host unit 200 as virtual address information 330.

Accordingly, the application 310 executed in the guest unit 300 may control data stored in the hardware 100 according to the virtual address information 330, and at this time, the hardware ( The control command for 100) is transmitted to the kernel unit 400 and may be executed by the host unit 200.

Meanwhile, the guest unit 300 may include page table information 320. The page table information 320 may include virtual address information 330 used in the guest unit 300 and intermediate address information used in the kernel unit 400.

In this regard, the page table information 320 may be understood as a data table listing each address information matched with the specific virtual address information 330, and accordingly, the page table information 320 is provided with arbitrary virtual address information 330. ) Can be converted into individual address information.

Meanwhile, the application 310 of the guest unit 300 may transmit an access request for accessing the virtual device 500 to the kernel unit 400.

Accordingly, the kernel unit 400 can transmit the access request received from the guest unit 300 to the host unit 200, and the host unit 200 is a virtual device of the application 310 installed in the guest unit 300. It is possible to manage access rights to the device 500.

In this regard, the host unit 200 may allow or block access to the virtual device 500 of the application 310 installed in the guest unit 300, and at this time, the host unit 200 ), you can set access rights to some of the data stored in the shared memory.

In addition, the host unit 200 may set different access rights for the virtual device 500 of an arbitrary application 310 among a plurality of applications 310 installed in the guest unit 300.

For example, the host unit 200 may set the first application installed in the guest unit 300 to access the virtual device 500, and at the same time, the second application installed in the guest unit 300 is a virtual device It can also be set to prevent access to (500).

Fig. 4 is a schematic diagram showing the kernel unit of Fig. 1;

The kernel unit 400 may include a control module 410 and address data information 420.

The control module 410 may receive an access request for the virtual device 500 from the application 310 of the guest unit 300.

In this case, when the virtual device 500 for the access request received from the application 310 does not exist, the control module 410 requests the host unit 200 to generate the virtual device 500 for the access request. I can.

In addition, the control module 410 may request access rights of the application 310 to the virtual device 500. In this case, the control module 410 may receive an access permission request from the application 310 and transmit it to the host unit 200.

In this regard, when the control module 410 requests the host unit 200 to generate the virtual device 500, the control module 410 may immediately request the host unit 200 for access rights of the application.

The control module 410 may check the access authority for the virtual device 500 of the application 310 installed in the guest unit 300.

To this end, the control module 410 may view the access rights of the application 310 to the virtual device 500 set by the host unit 200 from the host unit 200.

The control module 410 may request intermediate address information 430 for data stored in the virtual device 500 from the application 310 when access to the virtual device 500 of the application 310 is permitted. have.

The control module 410 receives each address information 430 from the application 310, and converts the address information 430 into physical address information according to the address data information 420 included in the kernel unit 400. I can.

At this time, the address data information 420 may be understood as a data table listing physical address information matching specific individual address information 430, and accordingly, the address data information 420 includes arbitrary intermediate address information 430. It can be converted into physical address information.

The control module 410 may transmit the converted physical address information to the host unit 200.

When the application 310 installed in the guest unit 300 owns access rights to the virtual device 500, the control module 410 may transmit an access path to the virtual device 500 to the application 310. have.

In other words, when a change occurs in the data of the virtual device 500 according to the command of the host unit 200, the control module 410 receives the physical address information 220 for the changed data from the host unit 200. The transmission may be received, and the control module 410 may convert the physical address information 220 into each address information 430 according to the address data information 420 and transmit it to the guest unit 300.

Accordingly, the guest unit 300 may convert the intermediate address information 430 received from the control module 410 into the virtual address information 330 according to the page table information 320.

Meanwhile, the kernel unit 400 may be operated by being integrated with the kernel that controls the hardware 100 by the host unit 200. In this case, the kernel unit 400 responds to the control command received from the guest unit 300. Accordingly, the hardware 100 can be controlled.

5 is a schematic diagram illustrating a memory sharing method according to an embodiment of the present invention.

Referring to FIG. 5, it can be understood that the guest unit 300 owns the address of the shared memory of the virtual device 500 in the form of virtual address information 330.

Accordingly, the guest unit 300 may compare the virtual address information 330 with information stored in the page table information 320 to convert the virtual address information 430 into each address information 430.

Meanwhile, the application 310 of the guest unit 300 may request the kernel unit 400 to access the virtual device 500.

Accordingly, the kernel unit 400 may check the access right of the application 310 to the virtual device 500 set by the host unit 200.

At this time, when the access right of the application 310 to the virtual device 500 is not permitted, the kernel unit 400 provides the host unit 200 with the access right to the virtual device 500 of the application 310. Request may be made, and the host unit 200 may change the access authority of the application 310 to the virtual device 500.

On the other hand, when it is determined that the virtual device 500 does not exist according to an access request from the application 310 of the guest unit 300, the kernel unit 400 sends the virtual device 500 to the host unit 200. You can request creation.

Accordingly, the host unit 200 may create a virtual device 500 including some of the hardware memories as shared memory.

On the other hand, when the application 310 of the guest unit 300 has access rights to the virtual device 500, the converted intermediate address information 430 using the page table information 320 is transferred to the kernel unit 400 ).

Accordingly, the kernel unit 400 may compare the respective address information 430 with information stored in the address data information 420 and convert it into physical address information 220.

The kernel unit 400 may transfer the converted physical address information 220 using the address data information 420 to the host unit 200, and the host unit 200 receives the physical address information 220, Data stored in the memory of the hardware 100 may be accessed according to the physical address information 220.

In this case, the memory of the hardware 100 accessible according to the physical address information 220 may be a memory designated as a shared memory included in the virtual device 500.

In contrast, the guest unit 300 is in the form of physical address information 220 through the kernel unit 400 and the host unit 200 in the shared memory of the virtual device 500 stored in the form of virtual address information 330. It can be understood as accessing the shared memory portion of the virtual device 500 designated in the memory of the hardware 100.

6 is a flowchart of a memory sharing method according to an embodiment of the present invention.

The memory sharing method includes steps of receiving an access request (600), checking access rights (610), converting to individual address information (620), converting to physical address information (630), and accessing the memory. Step 640 may be included.

Meanwhile, since the memory sharing method according to an embodiment of the present invention proceeds on substantially the same configuration as the memory sharing system 1 shown in FIG. 1, the same components as the memory sharing system 1 of FIG. Reference numerals are given, and repeated descriptions will be omitted.

In the step 600 of receiving the access request, an access request for the virtual device 500 may be received from the application 310 of the guest unit 300.

At this time, in the step 600 of receiving the access request, when the virtual device 500 for the access request received from the application 310 does not exist, the virtual device 500 for the access request to the host unit 200 You can request the creation of

Accordingly, the host unit 200 includes a shared memory to which a memory capacity of a preset size is allocated from the memory of the hardware 100 according to the request to create the virtual device 500 in the step 600 of receiving the access request. It is possible to create a virtual device (500).

In addition, the step 600 of receiving the access request may request access rights of the application 310 to the virtual device 500. In this case, in the step 600 of receiving the access request, the request for access permission may be transmitted from the application 310 and transmitted to the host unit 200.

In this regard, in the step 600 of receiving the access request, when the host unit 200 requests the creation of the virtual device 500, the access right of the application may be immediately requested from the host unit 200.

Accordingly, the host unit 200 may grant the access authority of the application 310 to the virtual device 500 according to the access authority request in operation 600 of receiving the access request.

In the step 610 of checking the access authority, the access authority to the virtual device 500 of the application 310 installed in the guest unit 300 may be checked.

In the step 610 of checking the access right, the access right of the application 310 to the virtual device 500 set by the host unit 200 may be checked.

In this case, in the step 610 of checking the access right, if the access right to the virtual device 500 of the application 310 is not permitted, the host unit 200 is sent to the virtual device 500 of the application 310. Access rights to the virtual device 500 may be requested, and accordingly, the host unit 200 may change the access rights of the application 310 to the virtual device 500.

In the step 620 of converting to each address information, when the access of the application 310 to the virtual device 500 is allowed, the guest unit 300 according to the page table information 320 stored in the guest unit 300 The virtual address information 330 stored in the device may be converted into each address information 430.

In the step 630 of converting to physical address information, each address information 430 may be converted into physical address information 220 used in the host unit 200.

To this end, in the step 630 of converting to physical address information, each address information 430 is received from the application 310, and according to the address data information 420 included in the kernel unit 400, each address information 430 ) Can be converted into physical address information 220.

The step 640 of accessing the memory may be a step of the application 310 accessing the memory of the hardware 100 according to the physical address information 220.

Such a memory sharing method may be implemented as an application or in the form of program instructions that can be executed through various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination.

The program instructions recorded in the computer-readable recording medium may be specially designed and constructed for the present invention, and may be known and usable to those skilled in the computer software field.

Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magnetic-optical media such as floptical disks. media), and a hardware device specially configured to store and execute program instructions such as ROM, RAM, flash memory, and the like.

Examples of the program instructions include not only machine language codes such as those produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform processing according to the present invention, and vice versa.

Although the above has been described with reference to embodiments, those skilled in the art will understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention described in the following claims. I will be able to.

1: memory sharing system
100: hardware
200: host unit
300: guest part
400: kernel part
500: virtual drive

Claims (11)

In a memory sharing method using a memory sharing system including a host unit, a guest unit installed as a virtual operating system on the host unit, and a kernel unit,
Receiving an access request for a virtual device from an application installed in the guest unit;
Checking access rights of the application to the virtual device;
Converting virtual address information for the virtual device into individual address information according to page table information stored in advance in the guest unit when access of the application to the virtual device is permitted;
Converting the respective address information into physical address information used in a host unit; And
Including the step of the application accessing the memory according to the physical address information,
The step of converting the respective address information into physical address information used in the host unit,
Converting each address information into physical address information for hardware on which the host unit is installed according to the address data information stored in advance in the kernel unit,
The page table information is a data table listing each address information matching arbitrary virtual address information,
The address data information is a data table listing physical address information matching arbitrary individual address information.
The method of claim 1, wherein the virtual device,
A memory sharing method comprising a shared memory capable of accessing an application executed in at least one element of the host unit and the guest unit.
The method of claim 2, wherein the shared memory,
A memory sharing method in which a memory capacity of a predetermined size is allocated from a memory of hardware in which the host unit is executed.
The method of claim 1,
When there is no virtual device for an access request received from the application,
Creating a virtual device according to the access request;
Further comprising the step of granting access rights of the application to the virtual device, the memory sharing method.
The method of claim 1, wherein the access right,
The method of sharing a memory, wherein the access right is changed by the host unit according to a request of an application having access right to the virtual device.
The method of claim 1, wherein the access right,
The memory sharing method, wherein access rights are set differently for a plurality of different applications executed in at least one element of the host unit and the guest unit.
A computer-readable recording medium having a computer program recorded thereon for performing the memory sharing method according to any one of claims 1 to 6.
A host unit installed in hardware;
A guest unit installed as a virtual operating system on the host unit; And
When an access request for a virtual device is received from an application installed in the guest unit, access rights for the virtual device of the application are checked, and the application access to the virtual device is permitted, Includes a kernel unit that delivers an access path to the device,
The guest unit,
Converting virtual address information for the virtual device into each address information according to page table information stored in advance in the guest unit,
The kernel unit,
Converts the respective address information into physical address information for hardware on which the host unit is installed according to address data information stored in advance in the kernel unit,
The page table information is a data table listing each address information matching arbitrary virtual address information,
The address data information is a data table listing physical address information matching arbitrary individual address information.
The method of claim 8, wherein the kernel unit,
When there is no virtual device for an access request received from the application,
A memory sharing system that requests the host unit to generate a virtual device according to the access request.
delete delete

Images