Method, device and storage medium for cloud computing on cloud system

Abstract

The present application provides a method for performing cloud computing on a cloud system. The method comprises: receiving a first task and a second task; determining a first hardware resource associated with the first task and a second hardware resource associated with the second task in the hardware resources of the cloud system; obtaining available hardware resources of the cloud system; determining a main time period for executing the first task and a fragment time period for executing the second task within a given time period according to the available hardware resources, the first hardware resources and the second hardware resources; and executing the first task in the main time period and executing the second task in the fragment time period.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method, device, and storage medium for performing cloud computing on a cloud system. Background Art

[0002] With the development of cloud computing technology, computing the verification process of logic system design on cloud systems has become a research hotspot. In the process of moving the computing power of logic system design verification tools to the cloud, hardware simulation tools can provide verification capabilities to users via cloud computing. Hardware simulation tools can be connected with peripherals to form a complete hardware system to test logic system designs.

[0003] During the execution of the verification task, it is usually necessary to call various hardware simulation tools of the cloud system to execute the verification task.

[0004] How to improve the efficiency of using hardware simulation tools in cloud systems is an urgent problem to be solved. Summary of the invention

[0005] In view of this, the present application proposes a method, device, and storage medium for performing cloud computing on a cloud system.

[0006] In a first aspect of the present application, a method for performing cloud computing on a cloud system is provided. The method comprises: receiving a first task and a second task; determining a first hardware resource associated with the first task and a second hardware resource associated with the second task from hardware resources of the cloud system; obtaining available hardware resources of the cloud system; determining a main time period for executing the first task and a fragment time period for executing the second task within a given time period according to the available hardware resources, the first hardware resources, and the second hardware resources; and executing the first task in the main time period and executing the second task in the fragment time period.

[0007] In a second aspect of the present application, a computing device is provided, comprising: a memory for storing a plurality of instructions; and at least one processor for executing the plurality of instructions so that the computing system performs the method described in the first aspect.

[0008] According to a third aspect of the present application, a non-transitory computer-readable storage medium is provided, wherein the non-transitory computer-readable storage medium stores a set of instructions for a computing device, wherein the set of instructions is used to enable the computing device to execute the method described in the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only for the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0010] Figure 1 A schematic diagram of a computing device according to an embodiment of the present application is shown.

[0011] Figure 2 A schematic diagram of a cloud system according to an embodiment of the present application is shown.

[0012] Figure 3 A schematic diagram of an EDA computing system according to an embodiment of the present application is shown.

[0013] Figure 4 A schematic diagram showing the utilization of fragmented time according to an embodiment of the present application is shown.

[0014] Figure 5 A flow chart of a method for performing cloud computing on a cloud system according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0015] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0016] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in this application should be understood by people with ordinary skills in the field to which this application belongs. The words "first", "second" and similar words used in this application do not indicate any order, quantity or importance, but are only used to distinguish different components. "Include" or "comprise" and similar words mean that the elements or objects appearing before the word include the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect.

[0017] Usually, a complete verification project can include multiple tasks. The number of hardware simulation tools in the cloud system is limited, and various tasks may occupy one or more of these hardware simulation tools. For tasks that require hardware simulation tools, as long as one hardware simulation tool is occupied by other tasks, the task cannot be executed. At the same time, the requirements for the continuity of running time are different between tasks, that is, some tasks need to occupy hardware resources for the entire period, while other subtasks can interrupt their execution at any time.

[0018] According to the above-mentioned characteristics of the verification task, in order to improve the utilization efficiency of the hardware resources of the cloud system, the embodiments of the present application provide a method, an apparatus and a storage medium for performing cloud computing on the cloud system.

[0019] Figure 1 FIG. 1 is a schematic diagram of a computing device 100 according to an embodiment of the present application. Figure 1 As shown, the computing device 100 may include: a processor 102, a memory 104, a network interface 106, a peripheral interface 108 and a bus 110. The processor 102, the memory 104, the network interface 106 and the peripheral interface 108 are connected to each other in communication within the computing device through the bus 110.

[0020] Processor 102 may be a central processing unit (CPU), an image processor, a neural network processor (NPU), a microcontroller (MCU), a programmable logic device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or one or more integrated circuits. Processor 102 may be used to perform functions related to the technology described in this application. In some embodiments, processor 102 may also include multiple processors integrated into a single logical component. Figure 1 As shown, the processor 102 may include a plurality of processors 102a, 102b, and 102c.

[0021] The memory 104 may be configured to store data (eg, instructions, lists of TCL objects, computer code, attributes of objects and values ​​of attributes, etc.). Figure 1 As shown, the data stored in the memory may include program instructions (for example, program instructions for implementing the method of the target module of the display logic system design of the present application) and data to be processed (for example, the memory may store temporary codes generated in the compilation process, attributes of the object and the values ​​of the attributes, etc.). The processor 102 may also access the program instructions and data stored in the memory, and execute the program instructions to operate on the data to be processed. The memory 104 may include a volatile storage device or a non-volatile storage device. In some embodiments, the memory 104 may include a random access memory (RAM), a read-only memory (ROM), an optical disk, a magnetic disk, a hard disk, a solid-state drive (SSD), a flash memory, a memory stick, etc.

[0022] The network interface 106 can be configured to provide the computing device 100 with communication with other external devices via a network. The network can be any wired or wireless network capable of transmitting and receiving data. For example, the network can be a wired network, a local wireless network (e.g., Bluetooth, WiFi, near field communication (NFC), etc.), a cellular network, the Internet, or a combination thereof. It is understood that the type of network is not limited to the above specific examples. In some embodiments, the network interface 106 may include any number of network interface controllers (NICs), radio frequency modules, transceivers, modems, routers, gateways, adapters, cellular network chips, etc., in any combination.

[0023] The peripheral interface 108 may be configured to connect the computing device 100 to one or more peripheral devices to implement information input and output. For example, the peripheral devices may include input devices such as a keyboard, a mouse, a touch pad, a touch screen, a microphone, and various sensors, and output devices such as a display, a speaker, a vibrator, and an indicator light.

[0024] The bus 110 may be configured to transmit information between various components of the computing device 100 (e.g., the processor 102, the memory 104, the network interface 106, and the peripheral interface 108), such as an internal bus (e.g., a processor-memory bus), an external bus (USB port, PCI-E bus), etc.

[0025] It should be noted that, although the above computing device architecture only shows the processor 102, the memory 104, the network interface 106, the peripheral interface 108 and the bus 110, in the specific implementation process, the computing device architecture may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above computing device architecture may also only include components necessary for implementing the embodiments of the present application, and does not necessarily include all the components shown in the figure.

[0026] Figure 2 A schematic diagram of a cloud system 120 according to an embodiment of the present application is shown.

[0027] like Figure 2 As shown, the cloud system 120 may include multiple cloud servers (122, 124). These cloud servers may be, for example, Figure 1 The computing device 100 shown is a computer provided by a cloud computing server. The cloud server (122, 124) can provide computing resources to users on the one hand, and can also serve as a host of hardware simulation resources to call multiple hardware simulation tools (e.g., 126a, 126b, 126c) in the cloud system 120 on the other hand. It is understandable that multiple hardware simulation tools can be connected to multiple hosts. Figure 2 Just an example.

[0028] The multiple hardware simulation tools may include a hardware emulator, a prototype verification tool, and a peripheral board (eg, various daughter cards, etc.) connected to the hardware emulator or the prototype verification tool. It is understandable that the multiple hardware simulation tools may include more hardware resources and are not limited to the above examples.

[0029] The cloud system 120 can be used to provide verification cloud computing resources. Therefore, the cloud system 120 is also referred to as cloud computing resources 120 in this application. It can be understood that the cloud system is just a name, and it does not require that the cloud system is a remote access system.

[0030] Figure 3 A schematic diagram of an EDA computing system 130 according to an embodiment of the present application is shown.

[0031] The EDA computing system 130 of the present application may be a local computing system, and may include a computing device 132 . In some embodiments, the computing system 130 may further include a local computing resource 134 .

[0032] The computing device 132 may be Figure 1 The computing device 100 shown. The computing device 132 can provide a resource manager to the user, and provide an interface connected to the cloud system 120 and an interface connected to the computing resources 134a and 134b. The local host 132 can also allocate different computing tasks to the cloud or local accordingly.

[0033] In some embodiments, the local computing resource 134 may include at least one of a server 134a or a hardware verification tool 134b. The plurality of EDA tasks may be partially executed on the cloud computing resource 120 and partially executed on the local computing resource 134. It is understood that the plurality of EDA tasks may also be executed only on the cloud computing resource 120 or only on the local computing resource 134.

[0034] The server 134a may be Figure 1 The computing device 100 shown. In some embodiments, the server 134a can run at least one EDA software tool (e.g., a software simulator, a formal verification tool, etc.). The server 134a can also serve as a host of a hardware verification tool 134b to collaborate with the hardware verification tool 134b to complete verification tasks and read verification results.

[0035] The hardware verification tool 134 b may illustratively include hardware verification tools such as a prototype verification board and a hardware emulator.

[0036] although Figure 3Only a limited number of local computing resources 134 are used, but those skilled in the art will appreciate that any number of local computing resources 134 can be provided according to actual needs. In other words, there can be multiple servers 134a and multiple hardware verification tools 134b. The servers 134a and the hardware verification tools 134b are not necessarily provided in a one-to-one pairing. For example, one server 134a can be connected to multiple hardware verification tools.

[0037] Figure 4 A schematic diagram of fragment time utilization 400 according to an embodiment of the present application is shown.

[0038] When the local computing system 130 sends a verification project 402 of a logic system design (eg, chip design) to the cloud system 120, the cloud system 120 may decompose the verification project into multiple tasks (eg, tasks 404 and 406). It is understood that the tasks here may not be chip verification tasks.

[0039] In order to perform verification tasks 404 and 406, cloud system 120 can obtain available hardware resources of cloud system 120. For example, cloud system 120 can obtain currently available hardware resources. The hardware resources of cloud system 120 may include multiple electronic devices (e.g., hardware emulators, prototype verification tools, and various daughter cards connected to hardware emulators or prototype verification tools, etc.). In one example, the hardware resources may include 4 hardware emulators and 1 DDR memory daughter card. Different electronic devices may be connected to each other to form different hardware resources. For example, the same hardware emulator may be connected to two different daughter cards to form two different hardware resources.

[0040] Different verification tasks may require different hardware resources. For example, a verification task for testing memory consistency requires connecting the prototype verification tool to a DDR memory daughter card; a verification task for testing wireless communication function requires connecting the prototype verification tool to a wireless communication daughter card. The above-mentioned prototype verification tool connected to the DDR memory daughter card and the prototype verification tool connected to the wireless communication daughter card respectively form two different hardware resources. It can be understood that when the only available prototype verification tool is connected to the DDR memory daughter card, even if the wireless communication daughter card is available, the hardware resource of the prototype verification tool connected to the wireless communication daughter card is unavailable.

[0041] Therefore, the cloud system 120 can determine the first hardware resource associated with the verification task 404 and the second hardware resource associated with the verification task 406 in the hardware resources of the cloud system 120. According to the available hardware resources and the required first hardware resources and second hardware resources, the cloud system 120 can further allocate the verification tasks 404 and 406. In one embodiment, the cloud system 120 has only four hardware emulators and one DDR memory daughter card. The first hardware resource may include four interconnected hardware emulators for completely simulating the entire logic system design; the second hardware resource may include a hardware emulator and a DDR memory daughter card connected to the hardware emulator, which is used to simulate the module related to memory reading and writing in the logic system design. That is, the hardware emulator is included in both the first hardware resource and the second hardware resource. It can be understood that when the verification task 404 occupies the first hardware resource, the verification task 406 cannot be executed because all hardware emulators are occupied.

[0042] Different verification tasks 404 and 406 typically have different priorities. In some embodiments, the compilation, synthesis, simulation, and debugging tasks of failed test cases of the logic system design may have a high priority, while the simulation of the regression case may have a low priority. In the example of the present application, the verification task 404 may have a high priority, requiring the occupation of all four hardware simulators for the complete simulation of the logic system design; the verification task 406 may have a low priority, requiring the occupation of only one hardware simulator and one DDR memory daughter card for executing the test case. It is understandable that the verification task may have many levels of priority, not limited to the high priority and low priority of the above examples.

[0043] In some embodiments, verification tasks 404 and 406 are placed in queue 410 corresponding to the first resource and queue 412 corresponding to the second resource, respectively. Verification task 406 may be one of a plurality of fragment tasks for executing a specific test case. Queue 412 may also be referred to as a fragment queue.

[0044] The cloud system 120 may allocate a period of time for executing the verification tasks 404 and 406 of the verification project. The cloud system 120 may determine the period of time based on the received verification project and available hardware resources, and allocate the period of time to the verification tasks 404 and 406.

[0045] Usually, verification tasks are not completely continuous. For example, verification task 404 can release the first hardware resource corresponding thereto after a period of time (also referred to as main period 422) of complete simulation logic system design, allowing verification task 406 to read and write memory. When verification task 404 needs to resume execution, verification task 406 must release the hardware emulator it occupies, so that the resource needs of verification task 404 are met and enter a new main period 424. Then the time period in which verification task 404 is suspended and verification task 406 can occupy the required hardware emulator can be referred to as fragment period 426. It can be seen that in this example, hardware emulator is a shortage resource and causes a fragment period. It can be understood that the shortage resource is needed by tasks 404 and 406 at the same time, and when task 404 uses the shortage resource, task 406 cannot use the shortage resource. If there is no shortage resource, verification task 406 does not need to release the hardware emulator it occupies, and there is no fragment period. Therefore, the cloud system 120 can determine the scarce resources based on the available hardware resources and the plurality of verification tasks (eg, 404 and 406 ), and determine the fragmentation period for the task 406 based on the scarce resources.

[0046] During the fragmentation period, other verification tasks (e.g., verification task 406) that require a hardware simulator can be used as fragmentation tasks to use this period, thereby improving the utilization rate of hardware resources. It is understandable that during the fragmentation period, the cloud system 120 may have enough time to execute multiple fragmentation tasks. In other words, task 406 may be one of the multiple fragmentation tasks executed during the fragmentation period 426.

[0047] In some embodiments, the main period 424 may enter a new fragment period 428, which is then followed by a new main period 430. That is, the main period 424 is located between the fragment periods 426 and 428. Unlike the above description of completing multiple fragment tasks within a fragment period, it is also possible that task 406 cannot be completed within the fragment period 426. In this case, when the fragment period 426 begins, the cloud system 120 may obtain task 406 from the queue 412 and execute task 406 on the second hardware resource associated with task 406. When the fragment period 426 ends, the cloud system 120 may pause the clock of task 406 and save the running data, release the second hardware resource, so that task 404 can use the first hardware resource (i.e., enter the main period 424). When the fragment period 428 begins, the cloud system 120 may read the saved running data to resume task 406 on the second hardware resource. It is understandable that there may also be a new main period 430 after the fragment period 428.

[0048] In some embodiments, the operation data may be a complete image of task 406. In some embodiments, the operation data may be a portion of key data sufficient to restore task 406. This application does not limit the storage of the operation data, and any technical solution that satisfies the restoration of task 406 may be used.

[0049] Compared with general cloud computing, since the computing resources of general cloud computing almost only include general computing power (for example, CPU and GPU) and storage, general cloud computing does not need to consider the problem that different combinations of different devices produce different computing resources, nor does it need to consider the use of fragmented time periods. In view of the general background of EDA on the cloud, the embodiment of the present application determines the fragmented time period by determining the shared hardware resources of the main task and the fragmented task (that is, limiting the shortage of resources of the fragmented task). By making full use of the fragmented time period, the hardware resource utilization rate of the cloud system is improved.

[0050] The embodiment of the present application also provides a method for performing cloud computing on a cloud system.

[0051] Figure 5 FIG. 5 is a flowchart of a method 500 for performing cloud computing on a cloud system according to an embodiment of the present application. The method 500 may be Figure 2 The method 500 is executed by the cloud system 120, and more specifically, by the computing device 100 in the cloud system 120. The method 500 may include the following steps.

[0052] In step 502, computing device 100 may receive a first task (eg, Figure 3 The first task and the second task are associated with a verification project of a logic system design (e.g., chip design), the first task has a high priority, and the second task has a low priority. That is, the priority of the first task is higher than that of the second task. Generally, a task that requires an entire section to occupy hardware resources can be a high priority task, while a task that can be interrupted at any time can be a low priority task. It is understandable that a verification project can include multiple verification tasks, not limited to 2 tasks. In some embodiments, the first task and the second task can be multiple subtasks of a certain verification task.

[0053] In step 504, the computing device 100 may determine the first hardware resource (e.g., 4 hardware emulators) associated with the first task and the second hardware resource (e.g., 1 hardware emulator and 1 DDR memory daughter card) associated with the second task in the hardware resources of the cloud system (e.g., cloud system 120). The hardware resources of the cloud system may include multiple electronic devices, such as computing resources (e.g., CPU, GPU and other computing resources), memory resources, hardware emulators, prototype verification tools, daughter cards, etc. Generally, we believe that software licenses do not constitute a resource restriction, but if a specific software license is bound to specific hardware, then the software bound to this specific hardware can also be regarded as a hardware resource. The first hardware resource and the second hardware resource have at least one identical electronic device.

[0054] In step 506, the computing device 100 may obtain the available hardware resources of the cloud system. The available hardware resources may be the currently available hardware resources or the available hardware resources in a certain time period in the future. In some embodiments, after receiving the first task and the second task, the computing device 100 of the cloud system 120 cannot process them immediately, but will start processing them in a certain time period in the future.

[0055] In step 508, the computing device 100 determines a main time period (eg, Figure 4 422, 424, 430) and a fragmented period for performing the second task (eg, Figure 4 426 and 428). The given time period is a time period for executing the verification project. The given time period may be determined by the cloud system according to the verification project and the available hardware resources.

[0056] The second task is one of a plurality of fragment tasks, and the plurality of fragment tasks are in a fragment task queue (eg, Figure 4 The fragment period includes a first sub-period (eg, 426) and a second sub-period (eg, 428), and the main period (eg, 424) is located between the first sub-period and the second sub-period.

[0057] The computing device 100 may determine the scarce resources based on the available hardware resources and the first and second verification tasks; and determine the scarce resources for the fragmentation period based on the scarce resources, wherein the scarce resources include the at least one identical electronic device.

[0058] In step 510, the computing device 100 may execute the first task in the main period and execute the second task in the fragment period. Executing the second task in the fragment period further includes: in response to the start of the first sub-period, obtaining the second task from the fragment task queue; executing the second task on a second hardware resource associated with the second task; in response to the end of the first sub-period, pausing the clock of the second task and saving running data; releasing the second hardware resource; and in response to the start of the second sub-period, reading the running data to resume the second task on the second hardware resource.

[0059] In view of the general background of EDA on the cloud, the embodiment of the present application determines the fragmentation period by determining the shared hardware resources of the main task and the fragmentation task (that is, the factors that limit the fragmentation task). By making full use of the fragmentation period, the hardware resource utilization rate of the cloud system is improved.

[0060] The present application also provides a computing device (for example, Figure 1 A computing device 100 includes: a memory for storing a plurality of instructions; and at least one processor for executing the plurality of instructions so that the computing system performs the method 500 described above.

[0061] An embodiment of the present application also provides a non-transitory computer-readable storage medium, which stores a set of instructions for a computing device, and the set of instructions is used to enable the computing device to execute the method 500 described above.

[0062] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0063] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0064] A person skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application (including the claims) is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the present application as described above, which are not provided in detail for the sake of simplicity.

[0065] Although the present application has been described in conjunction with specific embodiments of the present application, many alternatives, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the discussed embodiments.

[0066] This application is intended to cover all such substitutions, modifications and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application should be included in the scope of protection of this application.

Claims

1. A method for performing cloud computing on a cloud system, comprising: receiving a first task and a second task; Determining a first hardware resource associated with the first task and a second hardware resource associated with the second task from hardware resources of the cloud system, wherein the hardware resources of the cloud system include a plurality of electronic devices, and the first hardware resource and the second hardware resource have at least one identical electronic device; Obtaining available hardware resources of the cloud system; determining a main time period for executing the first task and a fragment time period for executing the second task within a given time period according to the available hardware resources, the first hardware resources, and the second hardware resources; as well as The first task is executed in the main period and the second task is executed in the fragment period.

2. The method of claim 1, wherein: The first task and the second task are associated with a verification project of a logic system design, the first task has a high priority, and the second task has a low priority.

3. The method of claim 2, wherein: The given time period is determined according to the verification item and the available hardware resources.

4. The method of claim 1, wherein: The second task is one of a plurality of fragment tasks, the plurality of fragment tasks are waiting in a fragment task queue, the fragment period includes a first sub-period and a second sub-period, and the main period is located between the first sub-period and the second sub-period.

5. The method of claim 4, wherein: Executing the second task in the fragmented period further comprises: In response to the first sub-period starting, acquiring the second task from the fragment task queue; The second task is executed on a second hardware resource associated with the second task.

6. The method of claim 5, wherein: Executing the second task in the fragmented period further comprises: In response to the end of the first sub-period, pausing the clock of the second task and saving the operation data; releasing the second hardware resource; and In response to the second sub-period starting, the running data is read to resume the second task on the second hardware resource.

7. The method of claim 1, further comprising: determining a scarce resource based on the available hardware resources and the first and second tasks; as well as The fragmented period is determined based on the scarce resources, wherein the scarce resources include the at least one identical electronic device.

8. A computing device, comprising: A memory for storing a plurality of instructions; as well as At least one processor is configured to execute the plurality of instructions so that the computing device performs the method according to any one of claims 1 to 7.

9. A non-transitory computer-readable storage medium storing a set of instructions for a computing device, the set of instructions being used to cause the computing device to execute the method according to any one of claims 1 to 7.

Images