resource name identification	Number and size of	System for use
			CPU core	2	GPOS：1，RTOS：1
Display card	2	GPOS：1，RTOS：1
			Memory device	1024MB	GPOS：300MB，RTOS：100MB
Sound card	2	GPOS：1，RTOS：0
			……	……	……

S220: in the operation process, a user can call an Intewell user mode program such as Intewell developer and the like to allocate corresponding hardware resources to the RTOS through a hardware resource application release interface module, and then output a resource release file API _ freetable.

The user can call the following instructions to realize corresponding functions through the hardware resource application release interface module, such as:

select _ resource () -query the current state of a particular hardware resource.

free _ resource () -releasing the specified hardware resource, which is in an unallocated state.

alloc _ resource () -allocating hardware resources.

S230: according to IDE _ ConfigTable.cfg output by the hardware resource configuration service module and API _ ConfigTable.cfg output by the hardware resource application release interface module, the release and application of the hardware resources are ensured to have no conflict through the processing of the hardware resource mutual exclusion processing module. The IDE _ ConfigTable.cfg is generated through the ConfigTable.cfg, and the recorded hardware resource allocation conditions are the same.

The resource mutex processing module firstly queries the API _ configtable.cfg and the IDE _ configtable.cfg to determine whether the hardware resources are allocated or not. In step S210, the hardware resource allocated to the RTOS cannot be allocated any more, so that when the resource mutual exclusion processing module determines that the resource is not allocated, that is, the application of the hardware does not conflict, the RTOS will execute the application for allocating the corresponding hardware resource.

Then, the hardware resource mutual exclusion processing module also queries a hardware resource usage Record table (rtosw _ Record _ table.cfg), determines whether the applied resource has been applied by the RTOS according to the table, and when the applied resource has been applied by the RTOS, it indicates that a hardware resource conflict exists in the application (that is, the same hardware resource is repeatedly called by the RTOS). When a conflict occurs, corresponding prompt information can be returned so that the program re-requests other hardware resources or terminates the hardware resource calling; and when the applied resource is not applied by the RTOS, continuing to the next step.

Cfg records allocated resources and released resources of the RTOS, and an example of the table is shown as follows, wherein, when a resource is allocated by the RTOS, the corresponding flag is 1, and when the resource is not allocated or released, the resource is regarded as idle, the corresponding flag is 0.

Resource name identification	Idle or not mark
		CPU1	1
CPU2	0
		Memory addresses A1-A2	1
Memory addresses A2-A3	1
		Sound card	0
……	……

S240: and taking the applied hardware resource off the GPOS.

In this step, the rmmod command (the mmod command is used to remove a specified kernel module from a currently running kernel in the Linux operating system), and the driver module of the requested hardware device is removed in each module manner, so that the hardware resource can be offline in the GPOS.

S250: and operating the hardware resource according to the address of the hardware resource by the RTOS.

This step is the process of transitioning hardware resources from GPOS to RTOS usage. The hardware address is derived from a hardware manual and is written in the user code according to the hardware manual. The hardware resources can be directly operated by using a script program when the RTOS is on line.

S260: and updating the RTOSHW _ Record _ Table.cfg table, and identifying the resource corresponding to the applied hardware resource as 1.

S270: after the application in the RTOS is finished running, an operation interface provided by the hardware resource application release interface module is called, for example, by free _ resource (), to request to release the specified hardware resource, and a resource release file API _ freetable. Specifically, refer to step S220, which is not described in detail.

S280: and (3) judging whether the hardware resources conflict (mainly preventing RTOS from being released repeatedly) according to API _ FreeTable.cfg and RTOSHW _ Record _ Table.cfg by a hardware resource mutual exclusion processing module.

The hardware resource mutual exclusion processing module maintains the above-mentioned hardware resource usage Record table rtosw _ Record _ table.cfg, which records the resources allocated by RTOS and the resources released, when Intewell allocates or releases the resources through a hardware resource dynamic allocator, the hardware resource mutual exclusion processing module needs to be called to query the rtosw _ Record _ table.cfg table first, and then the allocation and release of the resources are performed, so as to prevent the conflict. When the specified hardware resource is released and the resource release file API _ free table.cfg is generated, the Record of the released resource included in the API _ free table.cfg in the rtosw _ Record _ table.cfg table needs to be queried first, and if the identifier recorded in the rtosw _ Record _ table.cfg table is 1 (i.e., not released), it is determined that the hardware resource is not in conflict (repeatedly released), and the resource can be released.

S290: and the resource released by the RTOS is brought on line to the GPOS.

The hardware resources are reinitialized on the GPOS (mainly using the insmod command to reload the driver module of the specific hardware device), and at this time, the hardware resources can return to the GPOS to be used by the GPOS again.

S300: and updating the RTOSHW _ Record _ Table.cfg table, and identifying the corresponding resource of the applied hardware resource as 0.

According to the embodiment, based on the hardware resource configuration request of the user, the target hardware resource is scanned through the real-time running environment software, the service program and the like, the target hardware resource is applied or released and marked as idle, and finally the hardware resource in the idle state is allocated according to the hardware resource configuration request of the user, so that the dynamic allocation of the hardware resources of a real-time operating system and a non-real-time operating system is realized, the operating efficiency is improved, and the problem that the hardware resource can only be allocated statically once before the operation is started in the prior art is solved. In addition, after the real-time operating system completes the operation, the non-real-time operating system of the resource allocation can be reused, and the high-efficiency multiplexing of hardware resources is realized.

Based on an inventive concept, the present application further provides an apparatus 200 for dynamically allocating hardware resources to a system, which can be disposed in the Intewell RTRE of fig. 1. As shown in fig. 4, fig. 4 is a schematic structural diagram of a device 200 for dynamically allocating hardware resources to a system according to an embodiment of the present invention. The apparatus 200 for dynamically allocating hardware resources to a system according to this embodiment is specifically configured to perform the above-mentioned step S101 to step S103 and any optional example thereof. Reference may be made in detail to the method examples, which are briefly described herein as follows:

the apparatus 200 for dynamically allocating hardware resources of a system includes:

a communication module 210 configured to receive a configuration request for a target hardware resource, where the module is specifically configured to execute the step S101 and any optional example thereof.

An information obtaining module 220, configured to obtain occupation information of hardware resources by the non-real-time operating system and the real-time operating system, where the module is specifically configured to execute step S102 and any optional example thereof.

A hardwareresource allocation module 230, configured to dynamically allocate the target hardware resource between the non-real-time operating system and the real-time operating system based on the configuration request when the configuration request does not conflict with the occupancy information, where the module is specifically configured to execute step S103 and any optional example thereof.

In some embodiments, the configuration request received by the communication module 210 includes allocating a target hardware resource for the real-time operating system, and this module is specifically configured to execute the step S101 and any optional example thereof.

The occupation information acquired by the information acquiring module 220 includes information that the target hardware resource is occupied by the non-real-time operating system, and the module is specifically configured to execute the step S102 and any optional example thereof.

The hardwareresource allocating module 230 is configured to, when the configuration request does not conflict with the occupation information, perform allocation of the target hardware resource based on the configuration request, including: when the target hardware resource of the configuration request is occupied by the non-real-time operating system and is not allocated to the real-time operating system, the target hardware resource is released from the non-real-time operating system based on the configuration request to be allocated to the real-time operating system, and the module is specifically configured to execute the step S103 and any optional example thereof.

In some embodiments, the configuration request received by the communication module 210 includes releasing the target hardware resource already occupied by the real-time operating system, and the module is specifically configured to execute step S101 and any optional example thereof.

The occupation information acquired by the information acquiring module 220 includes information that the target hardware resource is occupied by the real-time operating system, and the module is specifically configured to execute the step S102 and any optional example thereof.

The hardwareresource allocation module 230 is configured to, when the configuration request does not conflict with the occupancy information, perform allocation of the target hardware resource based on the configuration request, including: when the target hardware resource of the configuration request is occupied by the real-time operating system, based on the configuration request, the target hardware resource is released from the real-time operating system to be allocated to the non-real-time operating system, and this module is specifically configured to execute step S103 and any optional example thereof.

In some embodiments, the information obtaining module 220 obtains the occupancy information, including: and acquiring the occupancy information by reading at least one configuration table.

The device for dynamically allocating hardware resources of a system provided in the foregoing embodiment allocates a target hardware resource pointed in a hardware resource configuration request by acquiring occupation information of resources occupied by a real-time operating system and a non-real-time operating system based on a received hardware resource configuration request; meanwhile, by calling and reading the hardware resource occupation information and the related hardware resource list, the conflicts of repeated allocation, repeated release and the like are avoided, and the dynamic allocation of the hardware resources between the real-time operating system and the non-real-time operating system is realized.

Based on an inventive concept, the present application further provides an apparatus 300 for dynamically allocating hardware resources to a system, which can be disposed in the Intewell RTRE of fig. 1. Fig. 5 is a schematic structural diagram of an apparatus 300 for dynamically allocating hardware resources to a system according to this embodiment, and fig. 5 is a specific implementation example of the embodiment of fig. 4. The apparatus 300 for dynamically allocating hardware resources to a system according to this embodiment is specifically configured to perform the above-mentioned step S101 to step S103 and any optional example thereof. Reference may be made in detail to the method examples, which are briefly summarized here as follows:

the apparatus 300 for dynamically allocating hardware resources to a system includes:

a hardware resource application release interface unit 310, configured to receive a configuration request for a target hardware resource through the interface; or, the hardware resource configuration service unit 320 is configured to receive the configuration file of the target hardware resource and parse the configuration request. The hardware resource application release interface unit 310 can provide Intewell user mode programs, and call the corresponding API operation interface provided by the hardware resource application release interface unit 310 to provide an externally provided interface for dynamically applying and releasing the hardware resources, so as to dynamically allocate the hardware resources to the real-time operating system. The hardware resource application release interface module unit 310 and the hardware resource configuration service unit 320 may be an embodiment of the communication module 210 in the apparatus 200 for dynamically allocating hardware resources to a system.

A hardware resource mutual exclusion processing unit 330, configured to obtain hardware resource occupation information of the non-real-time operating system and the real-time operating system, and determine whether the configuration request conflicts with the occupation information. The main function of the hardware resource mutex processing unit 330 is to maintain and manage a hardware resource usage Record table (e.g., rtosw _ Record _ table. Cfg), where the hardware resource usage Record table records allocated resources and released resources of the real-time operating system, and when a hardware resource is dynamically allocated, the hardware resource mutex processing unit 330 first queries the rtosw _ Record _ table. Cfg table, and then allocates and releases the resources, so as to prevent conflicts of repeated allocation or release of the resources by the real-time operating system. The hardware resource mutual exclusion processing unit 330 may be an embodiment of the information obtaining module 220 in the apparatus 200 for dynamically allocating hardware resources of a system.

A hardwareresource allocation unit 340, configured to release the target hardware resource from the non-real-time operating system to allocate to the real-time operating system when the configuration request does not conflict with the occupancy information; or, the hardware resource application releasing unit 350 is configured to release the target hardware resource from the real-time operating system to allocate to the non-real-time operating system when the configuration request does not conflict with the occupation information. The hardwareresource allocation unit 340 and the hardware resource application release unit 350 may be an embodiment of a hardware resource allocation module in the apparatus 200 for dynamically allocating hardware resources to a system.

For example, a user mode program or device accesses through the hardware resource application release interface unit 310, receives a configuration request for a target hardware resource, calls a select _ resource () service to query a current state of the target hardware resource, obtains occupation information of the hardware resource on the real-time operating system and the non-real-time operating system at that time by the hardware resource exclusive processing unit pair 330, when it is determined that the configuration request does not conflict with the occupation information of the hardware resource, calls a free _ resource () service through the hardwareresource allocation unit 340 to release the target hardware resource, and finally calls an alloc _ resource () service through the hardwareresource allocation unit 340 to allocate the hardware resource if the target hardware resource is in an unallocated state at that time.

In some other embodiments of the present application, the apparatus 300 for dynamically allocating hardware resources of a system further includes: and the strategy configuration module is configured to process and obtain the target hardware resource allocation strategy for different operating systems to allocate and use according to the configuration request of the user.

After the strategy configuration module receives a configuration request of a user for hardware resources, hardware resources required by the real-time operating system and the non-real-time operating system are evaluated, target hardware resource allocation strategies of the resource sizes required by the real-time operating system and the non-real-time operating system are given, and the hardware resources are reallocated according to the target hardware resource allocation strategies. In this embodiment, when the policy configuration module makes a new target hardware resource allocation policy, a certain amount of idle hardware resources may be reserved, so as to facilitate an emergency online task, or avoid a system jam caused by a full hardware resource such as a CPU.

With regard to the apparatus 300 for dynamically allocating hardware resources of a system in the above-described embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment related to the method, and will not be described in detail here.

The technical scheme provided by the application can dynamically allocate hardware resources of each system in Intewell, namely, the dynamic allocation of the hardware resources is realized, the high-efficiency multiplexing of the resources can be realized, and the smooth operation of services can be ensured on the operating system level.

Fig. 6 is a schematic structural diagram of a computing device 900 provided in an embodiment of the present application. The computing device may execute each optional implementation manner in the above method for dynamically allocating hardware resources, and the computing device may be a terminal, and may also be a chip or a chip system inside the terminal. As shown in fig. 6, the computing device 900 includes: a processor 910, a memory 920, and a communication interface 930.

It is to be appreciated that the communication interface 930 in the computing device 900 shown in fig. 6 may be used for communicating with other devices, and may in particular comprise one or more transceiver circuits or interface circuits.

The processor 910 may be connected to the memory 920. The memory 920 may be used to store the program codes and data. Therefore, the memory 920 may be a storage unit inside the processor 910, an external storage unit independent of the processor 910, or a component including a storage unit inside the processor 910 and an external storage unit independent of the processor 910.

Optionally, computing device 900 may also include a bus. The memory 920 and the communication interface 930 may be connected to the processor 910 through a bus. The bus may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, a line without arrows is used in FIG. 6, but does not indicate that there is only one bus or one type of bus.

It should be understood that, in the embodiment of the present application, the processor 910 may employ a Central Processing Unit (CPU). The processor may also be other general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. Or the processor 910 may employ one or more integrated circuits for executing related programs to implement the technical solutions provided in the embodiments of the present application.

The memory 920 may include a read-only memory and a random access memory, and provides instructions and data to the processor 910. A portion of the processor 910 may also include non-volatile random access memory. For example, the processor 910 may also store information of the device type.

When the computing device 900 is running, the processor 910 executes the computer-executable instructions in the memory 920 to perform any of the operational steps of the methods described above and any optional implementation thereof.

It should be understood that the computing device 900 according to the embodiments of the present application may correspond to a corresponding main body for executing the method according to the embodiments of the present application, and the above and other operations and/or functions of the respective modules in the computing device 900 are respectively for implementing the corresponding flows of the methods according to the embodiments, and are not described herein again for brevity.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is merely a logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.

The present embodiments also provide a computer-readable storage medium, on which a computer program is stored, the computer program being used for executing the method described above when executed by a processor, and the method including at least one of the aspects described in the above embodiments.

The computer storage media of the embodiments of the present application may take any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "for example" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). Additionally, the terms first, second, third and the like in the description and in the claims, or module a, module B, module C and the like are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order, it being understood that specific orders or sequences may be interchanged where permissible to effect embodiments of the application described herein in other than the order illustrated or described herein.

In the above description, reference to reference numerals indicating steps, such as the description of S110, S120, etc., does not necessarily indicate that the steps are performed, and the order of the steps before and after may be interchanged or performed simultaneously, where permitted.

The term "comprising" as used in the specification and claims should not be construed as being limited to the contents listed thereafter; it does not exclude other elements or steps. It should therefore be interpreted as specifying the presence of the stated features, integers, steps or components as referred to, but does not preclude the presence or addition of one or more other features, integers, steps or components, and groups thereof. Thus, the expression "an apparatus comprising the devices a and B" should not be limited to an apparatus consisting of only the components a and B.

Reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments, as would be apparent to one of ordinary skill in the art from this disclosure.

It should be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and all such equivalent embodiments are within the scope of the present application.

Claims

1. A method for dynamically allocating hardware resources of a system on which a non-real-time operating system and a real-time operating system run, the method comprising:

receiving a configuration request for a target hardware resource;

2. The method of claim 1,

the configuration request comprises allocation of target hardware resources for the real-time operating system;

3. The method of claim 1,

the configuration request comprises the target hardware resources occupied by the real-time operating system;

4. The method of claim 1, wherein the obtaining the occupancy information comprises: and acquiring the occupation information by reading at least one configuration file.

5. The method of any of claims 1 to 4, wherein receiving the configuration request for the target hardware resource comprises one of:

receiving configuration operation executed by a user; the configuration operation comprises a configuration request for target hardware resources;

6. An apparatus for dynamically allocating hardware resources of a system on which a non-real-time operating system and a real-time operating system run, the apparatus comprising:

and the hardware resource allocation module is used for dynamically allocating the target hardware resource between the non-real-time operating system and the real-time operating system based on the configuration request when the configuration request does not conflict with the occupation information.

7. The apparatus of claim 6,

the configuration request received by the communication module includes allocating a target hardware resource for the real-time operating system;

the hardware resource allocation module is further configured to, when the configuration request does not conflict with the occupation information, perform allocation of the target hardware resource based on the configuration request, including: and when the target hardware resource of the configuration request is occupied by the non-real-time operating system and is not allocated to the real-time operating system, releasing the target hardware resource from the non-real-time operating system based on the configuration request so as to be allocated to the real-time operating system.

8. The apparatus according to claim 6 or 7,

the configuration request received by the communication module includes: releasing the target hardware resources occupied by the real-time operating system;

9. The apparatus according to claim 6 or 7, wherein the information obtaining module obtains the occupancy information, and comprises: and acquiring the occupation information by reading at least one configuration file.

10. A computing device, comprising:

a processor, and

a memory having stored thereon program instructions that, when executed by the processor, cause the processor to perform the method of dynamically allocating hardware resources of a system as claimed in any one of claims 1 to 5.