WO2022150966A1

WO2022150966A1 - Processor memory management method for achieving process isolation

Info

Publication number: WO2022150966A1
Application number: PCT/CN2021/071272
Authority: WO
Inventors: 王志平
Original assignee: 王志平
Priority date: 2021-01-12
Filing date: 2021-01-12
Publication date: 2022-07-21

Abstract

A processor memory management method for achieving process isolation, comprising steps of: constructing an embedded file system for encapsulating, in a hardware control mode, a memory storage space into an independent unit having file characteristics (S1); establishing interconnection between a process operated by a processor core and the embedded file system by means of a processor multi-layer bus controller (S2); and opening up an embedded file corresponding to the process in the memory storage space by means of the embedded file system (S3). The method does not need intervention of an operation system, can better achieve process isolation, facilitates reduction of the load of the operation system, and guarantees security of process data.

Description

A processor memory management method for process isolation

technical field

The present invention relates to the technical field of integrated circuits and computers, in particular to a processor memory management method for realizing process isolation.

Background technique

Whether it is a microcontroller, a personal computer, a server or a mainframe computer, there are no more than two structures for the use of storage components: the von Neumann structure and the Haval structure. The von Neumann structure, also known as the Princeton structure, is a computer structure that stores process code and data at different addresses in the same memory; the Harvard structure refers to a computer structure that stores process code and data separately. But whether it is a von Neumann structure or a Haval structure, the access to "data" or "code" is directly performed by the physical address of the storage device. For a computer system with an operating system, the access of the process to the memory, that is, to the storage component, depends on the allocation of the storage space by the operating system, and the process code will convert the logical address of the required access to the target through the operating system during the actual running process into The physical address (ie, the physical address of the storage unit) is used to complete read and write access operations for code/data.

Today, with the explosion of information processing, the total number of processes running in a computer system and the total number of various service processes that need to be provided are increasing. When all the problems of memory usage are concentrated on the operating system for processing, It will inevitably cause the processing capacity of the entire operating system to become overwhelmed; and the operating system cannot achieve accurate security control of complete isolation of each process and service when dealing with a large number of processes and services. Processes are classified, so the operating system does not completely isolate all processes, which is bound to leave many uncertain security holes for the entire system. Therefore, there is a need for a processor memory management method that does not require operating system intervention and can better implement process isolation.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a processor memory management method for realizing process isolation, which does not require the intervention of the operating system, and can better realize the isolation of the process, which is beneficial to relieve the load of the operating system and ensure the security of the process data.

The technical solution provided by the present invention is as follows: the present invention provides a processor memory management method for realizing process isolation, comprising the steps of: constructing an embedded file system that realizes encapsulating memory storage space into an independent unit with file characteristics by means of hardware control ; establish interconnection between the process running by the processor core and the embedded file system through the processor multi-layer bus controller; open up an embedded file corresponding to the process in the memory storage space through the embedded file system .

This scheme realizes the encapsulation of the memory storage space into an embedded file system with file characteristics by means of hardware control, and establishes the process of the processor core running with the embedded file system through the multi-layer bus controller of the processor. Interconnection, which can open up embedded files corresponding to the process in the memory storage space through the embedded file system, so that the memory to which any process belongs can only be read or written by the process itself, and any other process, including the operating system, is not available. In the case of process permission, illegal reading or writing of the private memory space of the process will be directly rejected by the accessed memory hardware controller, thereby achieving physical isolation between processes and ensuring the security of process data. Without the intervention of the operating system, it is beneficial to relieve the load of the operating system.

Further, opening up an embedded file corresponding to the process in the memory storage space through the embedded file system specifically includes:

Receive an embedded file creation instruction sent by the process to the embedded file system; open the embedded file in the memory storage space through the embedded file system; feed back the index number of the embedded file to the process, and associate the process with the embedded file through the index number, so that the process becomes the file host of the embedded file. When creating an embedded file, the embedded file system receives the file creation instruction, opens the embedded file in the memory storage space, and then feeds back the index number of the embedded file to the process, so as to realize the one-to-one correspondence between the process and the embedded file , the process also becomes the file host for the embedded file.

Further, after the process is made to become the file host of the embedded file, it also includes the steps:

receiving the access key of the embedded file corresponding to the file host provided by the file host;

The access key corresponding to the embedded file is recorded through the embedded file system, and the host process number of the file host corresponding to the embedded file is recorded.

Further, after recording the access key corresponding to the embedded file through the embedded file system, and recording the host process number of the file host corresponding to the embedded file, it also includes the steps:

Determine whether the current access process accessing the embedded file is the file host corresponding to the embedded file;

If it is judged to be yes, then directly access; if it is judged to be no, then to judge whether the current access process has the access key; if it is judged to be yes, it can be accessed;

If it is judged to be no, access is not possible. When accessing an embedded file, the file host of the embedded file can directly access it without verification; and other processes must have the access key granted by the file host if they want to access the embedded file.

Receive the key replacement instruction sent by the file host to the embedded file system, and replace the access key corresponding to the embedded file recorded by the embedded file system with the key replacement instruction parameter 's new key;

And/or; receive the host replacement instruction sent by the file host to the embedded file system, and replace the host process number of the file host corresponding to the embedded file recorded by the embedded file system with the The process ID of the other process specified by the key replacement instruction.

receiving a deletion instruction sent by the file host to the embedded file system, and the embedded file system releases the memory space of the embedded file corresponding to the file host according to the deletion instruction;

and/or: receiving a clear instruction sent by the file host to the embedded file system, and the embedded file system resets the value of all data of the embedded file corresponding to the file host according to the clear instruction is 0.

Receive a read pointer setting instruction sent by the file host to the embedded file system, and the embedded file system resets the read operation pointer of the embedded file corresponding to the file host to the read pointer setting instruction designated address;

And/or: receiving the host read instruction sent by the process to the embedded file system, the embedded file system, when judging that the process number of the process is the host process number, uses the corresponding number of the process. The read operation pointer of the embedded file record is the base address, and the data of the specified number of bytes is continuously transmitted to the command initiation port;

and/or: receiving a non-host read instruction sent by the process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, The specified number of bytes of data are continuously transmitted to the command initiating port with the base address specified in the non-host read command.

Further, after recording the access key corresponding to the embedded file through the embedded file system, and recording the host process number of the file host corresponding to the embedded file, it also includes the steps: Receive the file host sending a write pointer setting instruction to the embedded file system, and the embedded file system resets the write operation pointer of the embedded file corresponding to the file host to the write pointer setting instruction designation the address of;

And/or: receiving the host write instruction sent by the process to the embedded file system, the embedded file system, when judging that the process number of the process is the host process number, uses the corresponding number of the process. The write operation pointer recorded in the embedded file is the base address, and the received instruction initiates the port to continuously transmit the specified number of bytes of data;

and/or: receiving a non-host write instruction sent by the process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, The specified number of bytes of data continuously transmitted by the command initiation port are received at the base address specified in the non-host write command.

Further, after the embedded file corresponding to the process is opened up in the memory storage space by the embedded file system, the step further includes:

Receive a tripartite operation host RX transfer establishment instruction and/or a tripartite operation non-host RX transfer establishment instruction sent to the embedded file system; receive tripartite data transfer between ports of the processor multi-layer bus controller operating data transmission instructions; informing the data receiving end of the embedded file system to receive the data sent by the three-party operation data transmission instructions;

Receive the three-party cancel RX transmission establishment instruction sent to the embedded file system, and cancel the data receiving end established by the three-party operation host RX transmission establishment instruction and/or the three-party operation non-host RX transmission establishment instruction.

Receive the three-party operation host TX transmission establishment instruction and/or the three-party operation non-host TX transmission establishment instruction sent to the embedded file system;

receiving a tripartite operation data transfer instruction for transferring data between ports of the processor multi-layer bus controller;

Notifying the data sending end of the embedded file system to send the specified embedded file data with the three-party operation data transmission instruction.

According to a processor memory management method for realizing process isolation provided by the present invention, this solution realizes the encapsulation of memory storage space into an embedded file system with file characteristics in a hardware-controlled manner by constructing an embedded file system, and through multiple processors The layer bus controller interconnects the process running by the processor core with the embedded file system, and can open up the embedded file corresponding to the process in the memory storage space through the embedded file system, so that the memory belonging to any process can only be read by the process itself Read or write, any other process including the operating system, without the permission of the process, illegal reading or writing of the private memory space of the process will be directly rejected by the accessed memory hardware controller, thus realizing the process The physical isolation between them ensures the security of process data. In addition, since this solution does not require the intervention of the operating system, it is beneficial to relieve the load of the operating system. .

Description of drawings

The preferred embodiments will be described below in a clear and easy-to-understand manner with reference to the accompanying drawings, and the above-mentioned characteristics, technical features, advantages and implementations of the present solution will be further described.

Fig. 1 is the overall flow schematic diagram of the embodiment of the present invention;

Fig. 2 is the overall structure schematic diagram of the embodiment of the present invention;

FIG. 3 is a schematic diagram of process access according to an embodiment of the present invention.

Detailed ways

In order to more clearly describe the embodiments of the present invention or the technical solutions in the prior art, the specific embodiments of the present invention will be described below with reference to the accompanying drawings. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative efforts, and obtain other implementations.

In order to keep the drawings concise, the drawings only schematically show the parts related to the present invention, and they do not represent its actual structure as a product. In addition, in order to make the drawings concise and easy to understand, in some drawings, only one of the components having the same structure or function is schematically shown, or only one of them is marked. As used herein, "one" not only means "only one", but also "more than one".

Example 1

An embodiment of the present invention, as shown in FIG. 1, the present invention provides a processor memory management method for implementing process isolation, including the steps:

S1. Construct an embedded file system (Embedded File System, which can be abbreviated as EFS) that encapsulates the memory storage space into an independent unit with file characteristics by means of hardware control.

Different from the way of performing memory isolation through software in the prior art, this solution implements the encapsulation of the memory storage space by means of hardware control to achieve the effect of isolation. S2. The process running by the processor core is interconnected with the embedded file system through the multi-layer bus controller of the processor.

The "multi-layer" in the processor multi-layer bus controller means that the bus controller in this example can establish the interconnection of multiple "source port" and "destination port" at a certain time, that is, at the same time. It maintains multiple non-interfering bus interconnections, so as to realize simultaneous access of multiple processes. In addition, there is also a bus controller that can only maintain one bus interconnection at a certain time in the bus interconnection technology inside the processor.

S3. Open up an embedded file (Embedded File, which can be abbreviated as EF) corresponding to the process in the memory storage space through the embedded file system. This scheme realizes the encapsulation of the memory storage space into an embedded file system with file characteristics by means of hardware control, and establishes the process of the processor core running with the embedded file system through the multi-layer bus controller of the processor. Interconnection, which can open up embedded files corresponding to the process in the memory storage space through the embedded file system, so that the memory to which any process belongs can only be read or written by the process itself, and any other process, including the operating system, is not available. In the case of process permission, illegal reading or writing of the private memory space of the process will be directly rejected by the accessed memory hardware controller, thereby achieving physical isolation between processes and ensuring the security of process data. Without the intervention of the operating system, it is beneficial to relieve the load of the operating system.

Specifically, in this embodiment, the connection between the processor core, the processor multi-layer bus controller and the embedded file system may be as shown in FIG. 2 and FIG. 3 , and the “memory” in FIG. 2 and FIG. 3 includes the processor External main memory and various caches inside the processor. This example takes the integration of 4 processor cores and 4 memory interfaces as an example (the so-called "memory interface" refers to the existence of 4 memory interfaces on the internal system bus of the processor. access to the bus port of the "memory"), there are multiple "processes" in each processor core, and the box marked by Tx identifies the process that each processor core has run in a period of time, the processor core is running Multiple processes are usually performed in a time-sharing manner, that is, a certain time period is divided into equal small time segments, which can be called kernel time slices. T0 to Tn in the figure represent the time slice from 0 to the nth time slice, and the corresponding processes are run in the kernel (for example, in "processor kernel 1", corresponding to "process 0", "process 1" respectively "Up to "process n", they are not running in "processor core 1" at the same time, but they mean that they run in "processor core 1" sequentially from 0 to n according to the time slice).

Example 2

In an embodiment of the present invention, on the basis of Embodiment 1, an embedded file corresponding to a process is opened up in a memory storage space through an embedded file system, which specifically includes:

S31, receiving the embedded file creation instruction sent by the process to the embedded file system, the character "EFSNEW" may be used as the instruction symbol.

S32, developing an embedded file in the memory storage space through the embedded file system.

EFS executes the EFSNEW instruction, which means that the process sending the instruction opens up a memory space of the required size and encapsulates it in the way of EF.

In addition, if EFS cannot create an EF as required by the instruction due to insufficient "memory" space, then EFS needs to feed back an error code to the instruction sending process.

S33. Feed back the index number of the embedded file to the process, and associate the process with the embedded file through the index number, so that the process becomes the file host of the embedded file.

When creating an embedded file, the embedded file system receives the file creation instruction, opens the embedded file in the memory storage space, and then feeds back the index number of the embedded file to the process, so as to realize the one-to-one correspondence between the process and the embedded file , the process also becomes the file host for the embedded file.

Preferably, after the process becomes the file host of the embedded file, the step further includes: S34 , receiving the access key of the embedded file corresponding to the file host provided by the file host. S35, record the access key corresponding to the embedded file through the embedded file system, and record the host process number of the file host corresponding to the embedded file.

Specifically, EFSNEW must carry the following necessary parameters: "EF Host Process ID", "Space Size", "EF Access Key". The host process number indicates the process number of the process that sends the embedded file creation instruction. When the EF is successfully created, the instruction sending process becomes the "EF host" of the currently created EF. EFS needs to use the process number of the "EF host" as the corresponding The only standard for "EF host" identification; the space size indicates the memory space required by the embedded file creation instruction to create EF; the access key is used by the "EF host" to authorize other "non-EF hosts" to access the EF. It is provided by the command sending process, and the read and write permissions are encrypted into the key, that is, the "non-EF host" cannot modify the access rights possessed by the key after obtaining the corresponding EF key. In addition, the "EF key" provided by the command-initiating process in this command must be a key with full read and write access rights. This parameter will be recorded by EFS and associated with the EF index number to become a "non-EFS host" access. The only standard for EFs created by directives.

Example 3

An embodiment of the present invention, on the basis of Embodiment 2, after recording the access key corresponding to the embedded file through the embedded file system, and recording the host process number of the file host corresponding to the embedded file, further comprises the steps: Determine whether the current access process accessing the embedded file is the file host corresponding to the embedded file; if it is determined to be yes, then access it directly; if it is determined to be no, then determine whether the current access process has an access key; if it is determined to be yes, Access can be performed; if it is judged to be no, access cannot be performed.

When accessing an embedded file, the file host of the embedded file can directly access it without verification; and other processes must have the access key granted by the file host if they want to access the embedded file.

Preferably, after recording the access key corresponding to the embedded file through the embedded file system, and recording the host process number of the file host corresponding to the embedded file, it also includes the steps:

Receive the key replacement instruction sent by the file host to the embedded file system, and replace the access key corresponding to the embedded file recorded in the embedded file system with the new key in the key replacement instruction parameter; and/or; receive the file host The host replacement instruction sent to the embedded file system replaces the host process number of the file host corresponding to the embedded file recorded in the embedded file system with the process number of other processes specified by the key replacement instruction.

In this embodiment, the key replacement command uses the character "EFSKEY" as the command symbol, and executing EFSKEY by the EFS will change the "EF key" of the formulated EF to the new "EF key" in the parameters of this command. After the execution of EFSKEY is completed, it means that the previous "EF key" has become invalid, which is equivalent to the "EF host" canceling the access rights of other "non-EF hosts" previously authorized to the specified EF.

EFSKEY is only authorized by the "EF host" of the target EF, that is, EFSKEY needs to carry the process ID of the process that initiated the instruction, and EFS will use the process ID as the only criterion for whether the instruction has execution authority. EFSKEY must carry the following necessary parameters: "EF host process number", "target EF index number", "new EF secret key".

The host replacement instruction uses the character "EFSOWN" as the instruction symbol. EFS executing the EFSOWN instruction will change the "EF host" of the EF specified in the instruction parameter to another process specified in the instruction parameter. The intent of this instruction is that when there is a large amount of data transfer between processes, all permissions of the data can be directly handed over to the other party without the need for the other party to copy the data, and there is no need to consider when the data that should be passed can be released. The memory space occupied by the data (after changing the "EF host", the new host can delete the data directly after using the data, and the original host can release the memory space occupied by the related data after handing over the permissions).

In addition to handing over data to other processes, the EFSOWN instruction can also be applied to hand over some state files in the process of initializing the child process in the parent process to ensure that the parent process and the child process also have physical isolation properties.

EFSOWN only has the authority of the "EF host" of the target EF, that is, EFSOWN needs to carry the process ID of the process that initiated the instruction, and EFS will use the process ID as the only criterion for whether the instruction has execution authority. EFSOWN must carry the following necessary parameters: "EF original host process number", "target EF index number", "EF new host process number".

Example 4

An embodiment of the present invention, on the basis of Embodiment 2 or Embodiment 3, after the process becomes the file host of the embedded file, further includes the steps:

Receive the deletion instruction sent by the file host to the embedded file system, and the embedded file system releases the memory space of the embedded file corresponding to the file host according to the deletion instruction; and/or; The type file system resets the value of all data of the embedded file corresponding to the file host to 0 according to the clear instruction.

In this embodiment, the delete instruction takes the character "EFSDEL" as the instruction symbol, and the execution of the EFSDEL instruction by EFS means that the memory space occupied by the EF specified in the instruction parameter will be released, and at the same time, the "EF" of the EF specified in the instruction parameter will be recovered. The index number".

EFSDEL only has the authority of the "EF host" of the target EF, that is, EFSDEL needs to carry the process ID of the process that initiated the instruction, and EFS will use the process ID as the only criterion for whether the instruction has execution authority. EFSDEL must carry the following necessary parameters: "EF host process number", "target EF index number".

The clear command uses the character "EFSCLR" as the command symbol. EFS executes EFSCLR to reset the value of all data in the EF specified in the command parameter to 0, and does not do any other operations. The intent of this directive is primarily to provide a process with a quick way to reset a batch of variables.

EFSCLR only has the authority of the "EF host" of the target EF, that is, EFSCLR needs to carry the process ID of the process that initiated the instruction, and EFS will use the process ID as the only criterion for whether the instruction has execution authority. EFSCLR must carry the following necessary parameters: "EF host process number", "target EF index number".

Example 5

In an embodiment of the present invention, on the basis of any one of Embodiments 2 to 4, the access key corresponding to the embedded file is recorded through the embedded file system, and after the host process number of the file host corresponding to the embedded file is recorded , which also includes the steps:

Receive the read pointer setting instruction sent by the file host to the embedded file system, and the embedded file system resets the read operation pointer of the embedded file corresponding to the file host to the address specified by the read pointer setting instruction; and/or; the receiving process sends the embedded file to the embedded file system. When the embedded file system determines that the process ID of the process is the host process ID, the embedded file system uses the read operation pointer recorded in the embedded file corresponding to the process as the base address, and continuously transmits the specified bytes to the command initiation port. and/or; the non-host read command sent by the receiving process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, it will use the non-host read command specified in the non-host read command. The base address continuously transmits the specified number of bytes of data to the command-initiating port.

In this embodiment, the read pointer setting instruction uses the character "EFSSKR" as the instruction symbol, and EFS executes EFSSKR to reset the read operation pointer of the target EF to the address specified in the instruction parameter. EFS will maintain the read and write operation pointers of each EF, but only for the operations of the "EF host" on the EF. That is, only the read or write command that uses the "EF host" process ID to access security authentication (the EFS is required to maintain the read or write pointer. This command allows the "EF host" process to reset the EF read operation pointer, that is, the read operation. EFSRD must carry the following necessary parameters: "EF host process number", "target EF index number", "EF read operation pointer".

The host read command uses the character "EFSRD" as the command symbol, and EFSRD refers to reading the data in the target EF. The word "host" in the so-called "host read instruction" indicates that the current instruction can only use the host process ID of the file host of the EF as the only criterion for EF access security authentication. When EFS executes this command, it will use the read pointer recorded by EF as the base address, and continuously transmit the specified number of bytes of data to the command initiation port. The "specified number of bytes" is the command parameter "Maximum read offset address" plus 1. EFSRD must carry the following necessary parameters: "EF host process number", "target EF index number", "maximum read offset address".

The non-host read instruction uses the character "EFSFR" as the instruction symbol, and EFSFR refers to reading the data in the target EF. The "non-host" in the so-called "non-host read command" means that the current command can only use the "EF key" as the only standard for EF access security authentication.

When executing this instruction, EFS cannot use the read pointer recorded by EF as the base address, but can only use the base address specified by the parameter "read base address" in the instruction to continuously transmit the specified number of bytes of data to the instruction initiation port. "Number of bytes" is the instruction parameter "Maximum read offset address" plus 1. The main purpose of this directive is that the "EF host" authorizes the "non-EF host" to directly access the target EF. The host" obtains the relevant permissions to directly access the target EF. EFSRD must carry the following necessary parameters: "EF key", "target EF index number", "read base address", "maximum read offset address".

Example 6

In an embodiment of the present invention, on the basis of any one of Embodiments 2 to 5, the access key corresponding to the embedded file is recorded through the embedded file system, and after the host process number of the file host corresponding to the embedded file is recorded , which also includes the steps:

The receiving file host sends a write pointer setting instruction to the embedded file system, and the embedded file system resets the write operation pointer of the embedded file corresponding to the file host to the address specified by the write pointer setting instruction; and/or; the receiving process sends the embedded file to the embedded file system. The host write command sent by the file system. When the embedded file system determines that the process ID of the process is the host process ID, the embedded file system uses the write operation pointer recorded in the embedded file corresponding to the process as the base address, and receives the command to initiate the specified bytes of the port continuous transmission. and/or; the non-host write instruction sent by the receiving process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, it will use the non-host write instruction specified in the non-host write instruction. The base address receives the specified number of bytes of data that the command initiates the port to transmit continuously.

Specifically, in this embodiment, the write pointer setting instruction uses the character "EFSSKW" as the instruction symbol, and EFS executes EFSSKW to reset the write operation pointer of the target EF to the address specified in the instruction parameter.

EFS will maintain the read and write operation pointers of each EF, but only for the operations of the "EF host" on the EF. That is, only read or write instructions that use the "EF host" process ID for access security authentication require EFS to maintain the read or write pointer. This instruction allows the "EF host" process to reset the EF's write operation pointer, that is, the base address of the write operation. EFSRW must carry the following necessary parameters: "EF host process number", "target EF index number", "EF write pointer". The host write command uses the character "EFSWR" as the command symbol, and EFSRD points to the write data in the target EF. The word "host" in the so-called "host write instruction" means that the current instruction can only use the "EF host" process ID as the only criterion for EF access security authentication.

When EFS executes this command, it will use the write pointer recorded by EF as the base address to receive the specified number of bytes of data continuously transmitted by the command initiation port. The "specified number of bytes" is the command parameter "maximum read offset address" plus 1. EFSWR must carry the following necessary parameters: "EF host process number", "target EF index number", "maximum write offset address".

The non-host write instruction uses the character "EFSFR" as the instruction symbol, and EFSFR refers to reading the data in the target EF. The "non-host" in the so-called "non-host read command" means that the current command can only use the "EF key" as the only standard for EF access security authentication.

Embodiment 7 An embodiment of the present invention, on the basis of any of the above-mentioned embodiments, after the embedded file corresponding to the process is opened in the memory storage space by the embedded file system, further includes the step of: receiving and sending the embedded file system to the embedded file system. The three-party operation host RX transfer setup command and/or the three-party operation non-host RX transfer setup command. A tripartite operation data transfer instruction for transferring data between ports of the processor's multilayer bus controller is received.

Notify the data receiving end of the embedded file system to receive the data sent by the three-party operation data transmission instruction.

Receive the three-party cancel RX transfer establishment command sent to the embedded file system, and cancel the data receiver established by the three-party operation host RX transfer establishment command and/or the three-party operation non-host RX transfer establishment command.

Specifically, in this embodiment, the three-party operation host RX transmission establishment command uses the character "EFSRX" as the command symbol, and EFSRX establishes a data receiving end for "three-way operation and transmission", that is, notifies the data receiving end that EFS is ready to receive the EFSX command. data sent.

The so-called "three-way operation transmission" means that the EF data of port A is transmitted to the EF of port B, but the process of port C or other hardware modules of port C initiates the transmission. EFSRX is "Three-party operation host RX transmission establishment", which means that this command is sent by the C port to the B port in the "three-party operation and transmission". The "host" in "Three-party operation host RX transmission establishment" means that C must be the host of the EF of the data destination B port, and it also means that the EFS uses the "EF host" process number as the only standard for access security authentication when executing this command. After the EFS of port B executes this command, the port will be temporarily locked to wait for the EFSX command from port A. After port B enters the locked state, if the EFSX command from port A is successfully received, after completing the data transmission, port B will enter the unlocked state. The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF. EFSRX must carry the following necessary parameters: "target EF index number", "EF host process number", "base address", "maximum offset address", "data sender port number".

The three-way operation host RX transmission establishment command uses the character "EFSFRX" as the command symbol. EFSFRX establishes a data receiving end for "three-way operation and transmission", that is, it informs the data receiving end that EFS is ready to receive the data sent by the EFSX command (refer to EFS command 16). Data (this instruction can only be transferred between ports of the "processor multi-layer bus controller" as shown in Figure 1, so it essentially has the parameter of "port").

The so-called "three-way operation transmission" means that the EF data of port A is transmitted to the EF of port B, but the process of port C or other hardware modules of port C initiates the transmission.

EFSFRX is "Three-party operation non-host RX transmission establishment", which means that this command is sent by the C port to the B port in the "three-party operation and transmission". "Non-host" in "Three-party operation non-host RX transmission establishment" means that C is not the host of the EF of the data destination B port, and also means that EFS must use the "EF key" as the only standard for access security authentication when executing this command . After the EFS of port B executes this command, the port will be temporarily locked to wait for the EFSX command from port A. After port B enters the locked state, if the EFSX command from port A is successfully received, after completing the data transmission, port B will enter the unlocked state. The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF. EFSFRX must carry the following necessary parameters: "target EF index number", "EF key", "base address", "maximum offset address", "data sender port number".

The three-way operation data transmission command takes the character "EFSX" as the command symbol. EFSX is the command to actually send the data for the "three-way operation transmission" data sender. EF, but it is the process of port C or other hardware module of port C that initiates the transfer. Therefore, EFSX is an instruction issued by port A after port C completes "RX transfer establishment" and "TX transfer establishment" of "three-way operation transfer". The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF.

The three-party operation cancel RX transmission establishment command uses the character "EFSCNS" as the command symbol. EFSCNS is the data receiving end that cancels the "three-party operation transmission" that has been established by EFSRX or EFSFRX, that is, releases the "lock" of the relevant port. state.

"Three-way operation transmission" means that the EF data of port A is transmitted to the EF of port B, but the process of port C or other hardware modules of port C initiates the transmission. The EFSCNS command may only be issued by port C, the initiator of the "three-way operation transfer". EFSCNS is rejected by port A when port C tries to send EFSTX or EFSFTX to port A (possibly because the port is in a busy state or the EF access security authentication fails). At this time, port C can cancel the established port B in time ( That is, the receiving state of the data receiving end of the "three-party operation transmission", so that port B can release the "locked" state in time. EFSFTX must carry the following necessary parameters: "data sender port number".

Embodiment 8 An embodiment of the present invention, on the basis of any of the above-mentioned embodiments, after the embedded file corresponding to the process is opened in the memory storage space through the embedded file system, further includes the step of: receiving and sending the embedded file system to the embedded file system. The three-way operation host TX transmission setup command and/or the three-way operation non-host TX transmission setup command. A tripartite operation data transfer instruction for transferring data between ports of the processor's multilayer bus controller is received.

Notify the data sending end of the embedded file system to send the specified embedded file data with a three-party operation data transmission instruction.

In this embodiment, the three-party operation host TX transmission establishment command uses the character "EFSTX" as the command symbol, and EFSTX establishes a data sending end for the "three-party operation and transmission".

"Three-way operation transmission" means that the EF data of port A is transmitted to the EF of port B, but the process of port C or other hardware modules of port C initiates the transmission. EFSTX is "Three-party operation host TX transmission establishment", which means that this command is sent by the C port to the A port in the "three-party operation and transmission". "Host" in "Three-party operation host TX transmission establishment" means that C must be the host of EF of port A of the data sender, and it also means that EFS uses the "EF host" process number as the only standard for access security authentication when executing this command. After the EFS of port A executes this command, the port will either refuse to execute or leave to send the corresponding EF data to port B through the EFSX command. The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF. EFSTX must carry the following necessary parameters: "source EF index number", "EF host process number", "base address", "maximum offset address", "data receiver port number".

The three-way operation data transmission command uses the character "EFSX" as the command symbol. EFSX is the command to actually send data for the "three-way operation and transmission" data sender. , but it is a process on port C or another hardware module on port C that initiates the transfer. Therefore, EFSX is an instruction issued by port A after port C completes "RX transfer establishment" and "TX transfer establishment" of "three-way operation transfer". The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF.

The three-party operation non-host TX transmission establishment command uses the character "EFSFTX" as the command symbol. EFSFTX establishes a data sender for "three-party operation and transmission", that is, notifies the data sender EFS to prepare to send the specified EF data with the EFSX command.

EFSFTX is "Three-party operation non-host TX transmission establishment", which means that this command is sent by the C port to the A port in the "three-party operation and transmission". "Non-host" in "Three-party operation non-host TX transmission establishment" means that C is not the host of the EF of port A of the data sender, and also means that EFS must use the "EF key" as the only standard for access security authentication when executing this command . After the EFS of port A executes this command, the port will either refuse to execute or leave to send the corresponding EF data to port B through the EFSX command. The intent of this instruction is to allow processes in the processor core to quickly and easily complete copy and cut operations on EF. EFSFTX must carry the following necessary parameters: "source EF index number", "EF key", "base address", "maximum offset address", "data sink port number".

It should be noted that the above embodiments can be freely combined as required. The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims

A processor memory management method for realizing process isolation, comprising the steps of:

Build an embedded file system that encapsulates the memory storage space into an independent unit with file characteristics by means of hardware control; establishes interconnection between the process running by the processor core and the embedded file system through the processor multi-layer bus controller ; Open up an embedded file corresponding to the process in the memory storage space through the embedded file system.
The processor memory management method for implementing process isolation according to claim 1, wherein the embedded file corresponding to the process is opened in the memory storage space by the embedded file system, Specifically include:

Receive an embedded file creation instruction sent by the process to the embedded file system; open the embedded file in the memory storage space through the embedded file system; feed back the index number of the embedded file to the process, and associate the process with the embedded file through the index number, so that the process becomes the file host of the embedded file.
The processor memory management method for implementing process isolation according to claim 2, characterized in that, after the process becomes the file host of the embedded file, the method further comprises the steps of:

receiving the access key of the embedded file corresponding to the file host provided by the file host;

The access key corresponding to the embedded file is recorded through the embedded file system, and the host process number of the file host corresponding to the embedded file is recorded.
The processor memory management method for implementing process isolation according to claim 3, wherein the access key corresponding to the embedded file is recorded by the embedded file system, and the access key corresponding to the embedded file is recorded by the embedded file system. After the host process number of the file host corresponding to the embedded file, it also includes the steps:

Determine whether the current access process accessing the embedded file is the file host corresponding to the embedded file;

If it is judged to be yes, then directly access; if it is judged to be no, then to judge whether the current access process has the access key; if it is judged to be yes, it can be accessed;

If it is judged to be no, access is not possible.
The processor memory management method for implementing process isolation according to claim 3, wherein the access key corresponding to the embedded file is recorded by the embedded file system, and the access key corresponding to the embedded file is recorded by the embedded file system. After the host process number of the file host corresponding to the embedded file, it also includes the steps:

Receive the key replacement instruction sent by the file host to the embedded file system, and replace the access key corresponding to the embedded file recorded by the embedded file system with the key replacement instruction parameter 's new key;

And/or; receive the host replacement instruction sent by the file host to the embedded file system, and replace the host process number of the file host corresponding to the embedded file recorded by the embedded file system with the The process ID of the other process specified by the key replacement instruction.
A kind of processor memory management method for realizing process isolation according to claim 2, is characterized in that, after described making described process become the file host of described embedded file, also comprises step:

receiving a deletion instruction sent by the file host to the embedded file system, and the embedded file system releases the memory space of the embedded file corresponding to the file host according to the deletion instruction;

and/or: receiving a clear instruction sent by the file host to the embedded file system, and the embedded file system resets the value of all data of the embedded file corresponding to the file host according to the clear instruction is 0.
The processor memory management method for implementing process isolation according to claim 3, wherein the access key corresponding to the embedded file is recorded by the embedded file system, and the access key corresponding to the embedded file is recorded by the embedded file system. After the host process number of the file host corresponding to the embedded file, it also includes the steps:

Receive a read pointer setting instruction sent by the file host to the embedded file system, and the embedded file system resets the read operation pointer of the embedded file corresponding to the file host to the read pointer setting instruction designated address;

And/or; receiving the host read instruction sent by the process to the embedded file system, the embedded file system, when judging that the process number of the process is the host process number, uses the corresponding number of the process. The read operation pointer of the embedded file record is the base address, and the data of the specified number of bytes is continuously transmitted to the command initiation port;

and/or: receiving a non-host read instruction sent by the process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, Continuously transmit the specified number of bytes of data to the command initiating port with the base address specified in the non-host read command.
The processor memory management method for implementing process isolation according to claim 3, wherein the access key corresponding to the embedded file is recorded by the embedded file system, and the access key corresponding to the embedded file is recorded by the embedded file system. After the host process number of the file host corresponding to the embedded file, it also includes the steps:

Receive the file host sending a write pointer setting instruction to the embedded file system, and the embedded file system resets the write operation pointer of the embedded file corresponding to the file host to the write pointer setting instruction designation the address of;

And/or: receiving the host write instruction sent by the process to the embedded file system, the embedded file system, when judging that the process number of the process is the host process number, uses the corresponding number of the process. The write operation pointer recorded in the embedded file is the base address, and the received instruction initiates the port to continuously transmit the specified number of bytes of data;

and/or: receiving a non-host write instruction sent by the process to the embedded file system, when the embedded file system judges that the process carries the access key corresponding to the embedded file, The specified number of bytes of data continuously transmitted by the command initiation port are received at the base address specified in the non-host write command.
The processor memory management method for implementing process isolation according to any one of claims 1 to 8, wherein the embedded file system is used to open up a memory storage space corresponding to the process in the memory storage space. After the embedded file, there are also steps:

Receive the three-party operation host RX transmission establishment instruction and/or the three-party operation non-host RX transmission establishment instruction sent to the embedded file system;

receiving a tripartite operation data transfer instruction for transferring data between ports of the processor multi-layer bus controller;

Notifying the data receiving end of the embedded file system to receive the data sent by the three-party operation data transmission instruction;

Receive the three-party cancel RX transmission establishment instruction sent to the embedded file system, and cancel the data receiving end established by the three-party operation host RX transmission establishment instruction and/or the three-party operation non-host RX transmission establishment instruction.
The processor memory management method for implementing process isolation according to any one of claims 1 to 8, wherein the embedded file system is used to open up a memory storage space corresponding to the process in the memory storage space. After the embedded file, there are also steps:

Receive the three-party operation host TX transmission establishment instruction and/or the three-party operation non-host TX transmission establishment instruction sent to the embedded file system;

receiving a tripartite operation data transfer instruction for transferring data between ports of the processor multi-layer bus controller;

Notifying the data sending end of the embedded file system to send the specified embedded file data with the three-party operation data transmission instruction.