WO2017114061A1

WO2017114061A1 - Asymmetric multiprocessing system and method for managing hardware resource thereof

Info

Publication number: WO2017114061A1
Application number: PCT/CN2016/107744
Authority: WO
Inventors: 廖通; 廖俊锋; 钟小武
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-12-28
Filing date: 2016-11-29
Publication date: 2017-07-06
Also published as: CN106919452B; CN106919452A

Abstract

Provided are an asymmetric multiprocessing system and a method for managing a hardware resource thereof. The method for managing a hardware resource of the asymmetric multiprocessing system comprises: registering, by a master core, a common hardware resource required for an operation of each mode (S10); reading and managing the common hardware resource (S12); and receiving, from a slave core corresponding to one mode, information associated with a hardware resource required for an operation of the mode, and allocating, according to registration information corresponding to the mode, to the slave core a common hardware resource required for the operation of the mode (S14). The method for managing a hardware resource of the asymmetric multiprocessing system can dynamically allocate common hardware resources required by respective modes according to resource allocation requirements of the respective modes, thereby ensuring flexible use of the common hardware resources of the asymmetric multiprocessing system, and preventing waste of the common hardware resources.

Description

Multi-core heterogeneous system and management method of its hardware resources

Technical field

This paper refers to, but is not limited to, the field of wireless communication technology, and relates to a multi-core heterogeneous system and a method for managing its hardware resources.

Background technique

At present, multi-core processing systems mainly have two structures: one is SMP (Symmetric Multi-Processing), and the other is AMP (Asymmetric Multi-Processing).

In the field of wireless communication, heterogeneous multi-core processing systems are common. For example, baseband chips need to process baseband signals. The processing of baseband signals includes L1 (physical layer), L2 (MAC (Medium Access Control), and RLC. (Radio Link Control, Radio Link Layer Control Protocol), PDCP (Packet Data Convergence Protocol) and other protocol layer, such as RRC (Radio Resource Control) Usually the baseband chip should use a special processor or accelerator, and also have a universal core for the management of the base station and the functions of the L2 and L3 of the wireless communication protocol. Therefore, the baseband chip can adopt the AMP architecture chip, and some cores complete the L1 (physical The function of the layer), part of the core completes the management of the base station and the L2 and L3 functions of the wireless communication protocol.

As a common communication device in the field of wireless communication, a wireless base station includes a single-system base station and a multi-standard base station (the common system of the base station includes GSM, UMTS, CDMA, LTE-FDD, LTE_TDD, etc.) base stations. However, in the related art, the wireless base station In order to expand its capacity, baseband chips use heterogeneous multi-core processing systems, and the baseband chips of related wireless base stations have fixed hardware resources for each system (hardware resources include but are not limited to network port queues, counters, and shares. Memory, inter-core interrupts, etc.), hardware resources can not be shared, thus causing a waste of hardware resources.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a hardware resource management method for a multi-core heterogeneous system, which can dynamically allocate resources required by each system according to the requirements of the standard resource configuration, and reduce waste of hardware resources.

The embodiment of the invention provides a method for managing hardware resources of a multi-core heterogeneous system, including:

The main core registers the common hardware resources required for the operation of each standard;

The main core performs read management on common hardware resources;

After receiving the hardware resource requirement information sent by the core corresponding to any standard, the primary core allocates the common hardware resources required for the operation of the system to the slave core corresponding to the standard according to the registration information corresponding to the standard.

Optionally, the multi-core heterogeneous system is a multi-core heterogeneous system of a base station.

Optionally, the method further includes: the primary core receives the hardware resource requirement information sent by the core from any system, and allocates the common hardware resources required for the operation of the system according to the registration information corresponding to the standard After the step of the slave core corresponding to the standard, the operating state of each system is monitored;

If an abnormality occurs in the operation of any of the standards, the common hardware resources corresponding to the system are recovered.

Optionally, the master core performs read management on the common hardware resources, including:

The primary core reserves a common hardware resource required for transferring data between the primary core and the secondary core;

The common hardware resources of the common hardware resources except the reserved common hardware resources are arranged through a mapping relationship table, where the mapping relationship table includes location information of the common hardware resources.

Optionally, after the primary core receives the hardware resource requirement information sent by the core of any standard, according to the registration information corresponding to the standard, the common hardware resource required for the operation of the standard is allocated to the standard corresponding The slave core includes:

After receiving the hardware resource requirement information sent by the core from any core, the primary core queries the location information corresponding to the common hardware resource required for the operation according to the mapping relationship table;

The location information corresponding to the common hardware resource required for the operation of the system is sent to the slave core corresponding to the standard.

The embodiment of the present invention further provides a multi-core heterogeneous system, including a primary core, a secondary core, and a common hardware resource, where the primary core includes:

a hardware resource registration module configured to register a common hardware resource required for the operation of each standard;

a hardware resource management module configured to read and manage common hardware resources;

The hardware resource allocation module is configured to: after receiving the hardware resource requirement information sent by the core of any standard, and according to the registration information corresponding to the standard, allocate the common hardware resources required for the operation of the standard to the corresponding system From the nuclear.

Optionally, the primary core further includes:

The system operation monitoring module is set to monitor the operating status of each system;

The hardware resource recovery module is configured to recover all common hardware resources of the system if an abnormality is detected in any of the systems.

Optionally, the hardware resource management module includes:

a hardware resource reservation unit, configured to reserve a common hardware resource required for transferring data between the primary core and the secondary core;

a hardware resource list unit, configured to: arrange, by the mapping relationship table, the remaining common hardware resources except the reserved common hardware resource in the common hardware resource, where the mapping relationship table includes a location of the common hardware resource. information.

Optionally, the hardware resource allocation module includes:

The hardware resource query unit is configured to: after receiving the hardware resource requirement information sent by the core of any standard, query the location information corresponding to the common hardware resource required for the operation according to the mapping relationship table;

The hardware resource delivery unit is configured to send the location information corresponding to the common hardware resource required for the standard operation to the slave core corresponding to the standard.

The embodiment of the invention further provides a computer readable storage medium, wherein the computer readable storage medium stores computer executable instructions, and when the computer executable instructions are executed, a method for managing hardware resources of a multi-core heterogeneous system is implemented.

Embodiments of the present invention provide a multi-core heterogeneous system and a hardware resource management method thereof. The management method of the hardware resources of the nuclear heterogeneous system includes: the main core registers the common hardware resources required for the operation of each system; reads and manages the common hardware resources; and receives the hardware resources sent by the core from any standard. The demand information, and according to the registration information corresponding to the standard, allocates the common hardware resources required for the operation of the system to the corresponding slave core. The hardware resource management method of the multi-core heterogeneous system provided by the embodiment of the present invention can dynamically allocate the common hardware resources required by each system according to the requirements of the standard resource configuration, so as to ensure that the common hardware resources of the multi-core heterogeneous system can be more flexibly utilized. Avoid wasting hardware resources.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

DRAWINGS

1 is a schematic flowchart of a method for managing hardware resources of a multi-core heterogeneous system according to Embodiment 1 of the present invention;

2 is a schematic flow chart of step S12 in FIG. 1;

3 is a schematic flow chart of step S14 in FIG. 1;

4 is another schematic flowchart of a method for managing hardware resources of a multi-core heterogeneous system according to Embodiment 1 of the present invention;

5 is a schematic structural diagram of a main core of a multi-core heterogeneous system according to Embodiment 2 of the present invention;

6 is a schematic structural diagram of a hardware resource management module of the primary core in FIG. 5;

7 is a schematic structural diagram of a hardware resource allocation module of the primary core in FIG. 5;

8 is another schematic structural diagram of a main core of a multi-core heterogeneous system according to Embodiment 2 of the present invention;

9 is a schematic structural diagram of applying a multi-core heterogeneous system to a base station system according to Embodiment 2 of the present invention;

FIG. 10 is a schematic structural view of the multi-core heterogeneous system of FIG. 9 further refined.

detailed description

The technical solutions in the embodiments of the present invention will be clearly and completely described in the following with reference to the accompanying drawings.

Embodiment 1

The embodiment of the present invention provides a method for managing hardware resources of a multi-core heterogeneous system. FIG. 1 is a schematic flowchart of a method for managing hardware resources of a multi-core heterogeneous system according to an embodiment of the present invention. The management methods of the hardware resources of the system include:

Step S10: The main core registers the public hardware resources required for the operation of each standard;

Multi-core heterogeneous systems, as the name implies, include a primary core and at least one secondary core. The number of cores is not limited. The specific quantity depends on the requirements of the system, and usually the primary core and the operating system from the core are different. The main core runs an operating system that supports multi-process scheduling, which facilitates the registration and registration of hardware resource requirements for each standard. It runs a lightweight operating system from the core or does not run the operating system, which is convenient for high performance and low performance of each system. Delay requirement.

The main core is created with the main process, and the corresponding slave processes are respectively created according to the system configuration system. The system standard is single-system or multi-standard. Accordingly, the number of slave processes of the master core is also one or more, from the process. The function is to perform protocol processing between the core and the main core corresponding to each standard, and to register and register the hardware resources required for each system.

Step S12: Perform reading management on common hardware resources;

The main process reads and manages the common hardware resources according to certain rules. The main process retains a part of the hardware resources for the normal data (including request messages and response messages) between the primary core and the secondary core to maintain the primary core. The need for normal communication with the core, and the need to retain a portion of the operation of the slave core for each system.

Step S14: Receive hardware resource requirement information sent by the core according to any standard, and allocate hardware resources required for the operation of the system to the corresponding slave core according to the registration information corresponding to the standard.

In this embodiment, the main process waits for the hardware resource requirement message sent by the core of each system, and the hardware resource requirement information sent by the core from any system to the main core, and the main core receives the hardware sent by the core of the system. After the resource demand information, the main core passes the slave process of the standard in the main core, and the hardware resource The source demand information is processed by the protocol, and the processed hardware resource requirement information is sent to the main process, and the main process obtains the hardware resource of the standard requirement according to the corresponding registration information in the slave process of the standard, and runs the system. The required hardware resources are allocated to the corresponding slave cores.

Optionally, the multi-core heterogeneous system may be a multi-core heterogeneous system of the base station, for example, a multi-core heterogeneous baseband chip of the wireless base station, or a multi-core heterogeneous radio frequency chip of the wireless base station, etc., of course, The multi-core heterogeneous system is not limited thereto, and may be a multi-core heterogeneous chip of other communication devices.

Optionally, please refer to FIG. 2. FIG. 2 is a schematic flowchart of step S12 in FIG. 1. Step S12 includes:

Step S120: The main core reserves a common hardware resource required for transferring data between the primary core and the secondary core;

Step S122: The remaining common hardware resources are arranged in the form of a mapping relationship table, where the mapping relationship table includes location information of the common hardware resources.

Common hardware resources include, but are not limited to, network port queues, counters, shared memory, and inter-core interrupts. Each system has different requirements for hardware resource usage. The primary core reserves the need for fixed hardware resources to be transmitted between the primary core and the secondary core. Data (including request information, response information, etc.) to maintain the normal communication between the primary core and the secondary core. In view of this, it is necessary to reserve the common hardware resources needed to transfer data between the primary core and the secondary core. The public hardware resources except the reserved main core and the common hardware resources required to transfer data between the cores are arranged through the mapping relationship table, as the common hardware resources of the slave core corresponding to each system. , that is, the resource pool, the mapping relationship table should include the location of the hardware resources (including the index or address), and may also include the type and size of the hardware resources.

Optionally, please refer to FIG. 3. FIG. 3 is a schematic flowchart of step S14 in FIG. 1. Step S14 includes:

Step S140: Receive hardware resource requirement information sent by the core from any standard, and query location information corresponding to hardware resources required for the operation according to the mapping relationship table;

Step S142, sending location information corresponding to the hardware resources required for the operation of the system to the standard Corresponding from the core.

In this embodiment, the slave core sends hardware resource requirement information to the master core, and the master core passes the corresponding slave process in the master core to perform protocol processing on the hardware resource requirement information, and the processed hardware is processed. The resource requirement information is sent to the main process, and the main process obtains the hardware resources required by the standard according to the registration information corresponding to the standard in the corresponding process of the corresponding system, and further, the corresponding hardware resource can be found through the mapping relationship table. Location information (including an index or an address), and then the location information is processed by the protocol of the process and sent to the corresponding slave core, and the slave core can call the common hardware resource according to the location information.

FIG. 4 is still another schematic flowchart of a method for managing hardware resources of a multi-core heterogeneous system according to an embodiment of the present invention. Referring to FIG. 4, after step S14, the method further includes:

Step S16: monitoring the operating status of each system;

Each system has a corresponding slave process in the slave core of the master core and the system. The slave process established in the master core is the protocol processing corresponding to the standard (for example, the L3 part of the corresponding baseband chip). The slave process in the slave core mainly lies in the specific operation of the system (for example, the L1 and L2 parts of the corresponding baseband chip). For this reason, monitoring the operating state of each system requires monitoring the corresponding slave processes in the master core and correspondingly. From the nuclear process.

Step S18: If an abnormality occurs in the operation of any of the standards, all common hardware resources of the system are recovered.

If the corresponding slave process in the master core and the slave process of the corresponding slave core are abnormal, then all the slave processes of the slave core and the master core under the slave core-associated system are suspended, and all hardware resources of the system are recovered. Go to the resource pool and then reinitialize the hardware resources needed for the system and redistribution.

Embodiment 2

The embodiment of the present invention further provides a multi-core heterogeneous system, including a primary core 100, a secondary core (not shown), and a common hardware resource (not shown, including but not limited to a network port queue, a counter, a shared memory, and an inter-core interrupt. And FIG. 5 is a structural diagram of a main core of a multi-core heterogeneous system according to an embodiment of the present invention. For example, referring to FIG. 5, the main core 100 includes a hardware resource registration module 10, a hardware resource management module 12, and a hardware resource allocation module 14.

The hardware resource registration module 10 is configured to register a common hardware resource required for the operation of each standard;

Multi-core heterogeneous systems, as the name implies, include a primary core and at least one secondary core. The number of cores is not limited. The specific quantity depends on the requirements of the system, and usually the primary core and the operating system from the core are different. The main core runs an operating system that supports multi-process scheduling, which facilitates registration and registration of hardware resource requirements of various standards. It runs a lightweight operating system from the core or does not run an operating system, which is convenient for high performance and low operation of each system. Delay requirement.

The hardware resource management module 12 is configured to perform read management on common hardware resources;

The main process reads and manages the common hardware resources according to certain rules. The main process retains a part of the hardware resources for the normal data (including request messages and response messages) between the primary core and the secondary core to maintain the primary core. The need for normal communication between the core and the core, and the need to retain a portion of the slave core for each type of operation.

The hardware resource allocation module 14 is configured to allocate the common hardware resources required for the operation of the system to the corresponding slave core according to the registration information corresponding to the standard after receiving the hardware resource requirement information sent by the core of any standard. .

The main process waits for the hardware resource requirement message sent by the core in each mode, and the hardware resource requirement information sent by the core from any system to the main core, and the main core passes the corresponding standard slave process in the main core, and the hardware resource requirement The information is processed by the protocol, and the processed hardware resource requirement information is sent to the main process, and the main process obtains the hardware resources required by the standard according to the registration information corresponding to the standard in the process according to the corresponding standard, and the The hardware resources required for the operation of the system are allocated to the corresponding slave cores.

Optionally, refer to FIG. 6. FIG. 6 is a structure of a hardware resource management module of the primary core in FIG. The hardware resource management module 12 includes a hardware resource reservation unit 120 and a hardware resource list unit 122:

The hardware resource reservation unit 120 is configured to reserve a common hardware resource required for transferring data between the primary core and the secondary core;

The hardware resource list unit 122 is configured to arrange the common hardware resources except the reserved common hardware resources in the common hardware resource by using a mapping relationship table, where the mapping relationship table includes location information of the common hardware resources. .

Common hardware resources include, but are not limited to, network port queues, counters, shared memory, and inter-core interrupts. Each system has different requirements for hardware resource usage. The primary core reserves the need for fixed hardware resources to be transmitted between the primary core and the secondary core. Data (including request information, response information, etc.) to maintain the normal communication between the primary core and the secondary core. In view of this, it is necessary to reserve the common hardware resources needed to transfer data between the primary core and the secondary core. The remaining common hardware resources are arranged in the form of a mapping relationship table, which is a common hardware resource corresponding to the core operation time, that is, a resource pool corresponding to each system, and the mapping relationship table should include the location of the hardware resource (including an index or an address), and It can include the type and size of hardware resources.

Optionally, referring to FIG. 7, FIG. 7 is a schematic structural diagram of a hardware resource allocation module of the primary core in FIG. 5, where the hardware resource allocation module includes a hardware resource query unit 140 and a hardware resource delivery unit 142:

The hardware resource query unit 140 is configured to: after receiving the hardware resource requirement information sent by the core of any standard, query the location information corresponding to the hardware resource required for the operation according to the mapping relationship table;

The hardware resource delivery unit 142 is configured to send the location information corresponding to the hardware resources required for the standard operation to the slave core corresponding to the standard.

In this embodiment, the slave core sends hardware resource requirement information to the master core, and the master core passes the corresponding slave process in the master core to perform protocol processing on the hardware resource requirement information, and the processed hardware is processed. The resource requirement information is sent to the main process, and the main process obtains the hardware resource of the system operation requirement according to the corresponding registration information in the slave process of the system, and further, through the above mapping The relationship table can find the location information (including the index or address) of the corresponding public hardware resource, and then the location information is sent to the slave core through the protocol of the process, and the slave core can use the location information to the common hardware. The resource is called.

FIG. 8 is another schematic structural diagram of a main core of a multi-core heterogeneous system according to an embodiment of the present invention. Referring to FIG. 8 , on the basis of the foregoing embodiment, the main core further includes a standard operation monitoring module 16 and hardware resource recovery. Module 18:

The system operation monitoring module 16 is configured to monitor the operating status of each system;

In this embodiment, each system corresponds to a master process, and a slave process corresponding to the master core has a corresponding slave process. The slave process established in the master core is a protocol process corresponding to the standard (for example, a corresponding baseband). The L3 portion of the chip), the slave process in the slave core, is primarily used for the specific operation of the system (eg, the L1 and L2 portions of the corresponding baseband chip). To this end, to monitor the operating status of each system, it is necessary to simultaneously monitor the corresponding slave processes in the master core and the slave processes corresponding to the slave cores.

The hardware resource recovery module 18 is configured to recover all hardware resources of the system if an abnormality occurs in any of the systems monitored.

If an exception occurs in the corresponding slave process in the master core of any system, or an exception occurs in the slave slave process corresponding to the standard, then all the slave and master core slave processes under the slave core-associated system are suspended. And reclaim all the hardware resources of the system into the resource pool, and then re-initialize the hardware resources required by the system and redistribution system.

In this embodiment, the multi-core heterogeneous system may be a multi-core heterogeneous system of the base station, for example, a multi-core heterogeneous baseband chip of the wireless base station, or a multi-core heterogeneous radio frequency chip of the wireless base station, etc., of course, The multi-core heterogeneous system is not limited thereto, and may also be a multi-core heterogeneous chip of other communication devices.

The multi-core heterogeneous system in the embodiment of the present invention is further described below by taking a baseband chip of a base station as an example:

9 is a schematic structural diagram of a multi-core heterogeneous system applied to a base station system according to an embodiment of the present invention, and FIG. 10 is a schematic structural diagram of further refinement of the multi-core heterogeneous system of FIG. 9. Referring to FIG. 9 and FIG. 10, the multi-core The heterogeneous system uses the main core of the multi-core heterogeneous system in the embodiment of Figure 8:

AMP-based SoC (System-on-a-Chip) new-generation baseband chip with strong processing capability, each with N cores, including UMTS (Universal Mobile Telecommunications System), GSM (Global System for In the multi-standard site of Mobile communication (Global System for Mobile Communications), in some scenarios, a new generation of baseband chips can support two UMTS and GSM standards at the same time. In order to fully utilize the hardware capabilities, plan each piece. The baseband chip runs UMTS and GSM simultaneously.

As shown in Figure 9, the main core runs on the Linux multi-process operating system and creates three processes, one main process, one slave process corresponding to the UMTS system (mainly responsible for UMTS standard protocol processing), and one GSM standard corresponding slave. Process 2 (mainly responsible for GSM standard protocol processing); running a lightweight LWOS operating system from the core, running a lightweight task from the core, and deploying UMTS services from core 1 to core M according to resource requirements, The cores M+1 to N are used to deploy GSM services, where M and N are positive integers greater than 1, and M is less than N.

As shown in FIG. 10, the main core main process is split into a hardware resource allocation module (abbreviated as an allocation module in FIG. 10) and a standard operation monitoring module (referred to as a monitoring module in FIG. 10), and the main core is removed from the process 1. The hardware resource registration module (referred to as registration in FIG. 10) divided into UMTS base station service (L3) and UMTS standard requirements, and is divided into GSM base station service (L3) and hardware resource registration module required by UMTS system from process 2 (in In FIG. 10, it is simply referred to as registration), and is divided into a UMTS base station service (L1\L2) module from the core 1 to the core M, and is split into a UMTS base station service (L1\L2) module from the core M+1 to the core N.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions. This application is not limited to any specific combination of hardware and software. A person skilled in the art should understand that the technical solutions of the present application can be modified or equivalent, without departing from the spirit and scope of the technical solutions of the present application, and should be included in the scope of the claims of the present application.

Industrial applicability

The above technical solution can dynamically allocate the common hardware resources required by each system, and ensure that the common hardware resources of the multi-core heterogeneous system can be more flexibly utilized to avoid waste of hardware resources.

Claims

A method for managing hardware resources of a multi-core heterogeneous system, comprising:

The main core registers the common hardware resources required for the operation of each standard;

The main core performs read management on common hardware resources;

After receiving the hardware resource requirement information sent by the core corresponding to any standard, the primary core allocates the common hardware resources required for the operation of the system to the slave core corresponding to the standard according to the registration information corresponding to the standard.
The method of claim 1 wherein: said multi-core heterogeneous system is a multi-core heterogeneous system of a base station.
The method for managing hardware resources of a multi-core heterogeneous system according to claim 1, further comprising: the main core receiving hardware resource requirement information sent by a core of any standard, and registering according to the standard corresponding to the system Information, after the step of assigning the common hardware resources required for the operation of the system to the slave core corresponding to the standard, monitoring the running status of each system;

If an abnormality occurs in the operation of any of the standards, the common hardware resources corresponding to the system are recovered.
The method for managing hardware resources of a multi-core heterogeneous system according to claim 2, wherein: the master core performs read management on the common hardware resources, including:

The primary core reserves a common hardware resource required for transferring data between the primary core and the secondary core;

The common hardware resources of the common hardware resources except the reserved common hardware resources are arranged through a mapping relationship table, where the mapping relationship table includes location information of the common hardware resources.
The method for managing hardware resources of a multi-core heterogeneous system according to claim 4, wherein: after receiving the hardware resource requirement information sent by the core of any standard, the primary core, according to the registration information corresponding to the standard, The common hardware resources required for the operation of the system are assigned to the slave cores corresponding to the standard:

After receiving the hardware resource requirement information sent by the core from any core, the primary core queries the location information corresponding to the common hardware resource required for the operation according to the mapping relationship table;

Sending location information corresponding to the common hardware resource required for the operation of the system to the corresponding system From the nuclear.
A multi-core heterogeneous system comprising a primary core, a secondary core, and a common hardware resource, the primary core including:

a hardware resource registration module configured to register a common hardware resource required for the operation of each standard;

a hardware resource management module configured to read and manage common hardware resources;

The hardware resource allocation module is configured to: after receiving the hardware resource requirement information sent by the core of any standard, and according to the registration information corresponding to the standard, allocate the common hardware resources required for the operation of the standard to the corresponding system From the nuclear.
The multi-core heterogeneous system of claim 6 wherein: said multi-core heterogeneous system is a multi-core heterogeneous system of a base station.
The multi-core heterogeneous system according to claim 6, wherein the main core further comprises:

The system operation monitoring module is set to monitor the operating status of each system;

The hardware resource recovery module is configured to recover all common hardware resources of the system if an abnormality is detected in any of the systems.
The system for managing hardware resources of a multi-core heterogeneous system according to claim 6, wherein the hardware resource management module comprises:

a hardware resource reservation unit, configured to reserve a common hardware resource required for transferring data between the primary core and the secondary core;

a hardware resource list unit, configured to: arrange, by the mapping relationship table, the remaining common hardware resources except the reserved common hardware resource in the common hardware resource, where the mapping relationship table includes a location of the common hardware resource. information.
The system for managing hardware resources of a multi-core heterogeneous system according to claim 9, wherein the hardware resource allocation module comprises:

The hardware resource query unit is configured to: after receiving the hardware resource requirement information sent by the core of any standard, query the location information corresponding to the common hardware resource required for the operation according to the mapping relationship table;

The hardware resource delivery unit is configured to send the location information corresponding to the common hardware resource required for the standard operation to the slave core corresponding to the standard.