System shutdown method based on multi-core heterogeneity and computer program product
By closing each domain in a multi-core heterogeneous system in sequence, the abnormal function problem of system on chip is solved when the power is off, ensuring that the system is shut down and started normally, and data errors are avoided.
Patent Information
- Application Number
- CN202411329440.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-23
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2044-09-23
AI Technical Summary
Multi-core heterogeneous system on chip may cause functional confusion or abnormality when power is off, especially when different domains are responsible for different functions. The existing technology lacks an effective multi-domain linkage shutdown method, resulting in abnormal system shutdown and affecting system startup. and data integrity.
Using a shutdown method based on multi-core heterogeneous systems, each domain of the system on chip is closed in sequence, including the virtualized front-end, hardware domain and information security domain. By generating and receiving shutdown signals, each domain can be closed within a preset time, avoiding Exceptional situation.
Ensure the normal shutdown and startup of the system on chip, avoid data errors and peripheral hardware state errors, and realize the integrity and stability of system data.
Smart Images

Figure CN118838658B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of multi-core heterogeneous systems, and in particular to a system shutdown method based on multi-core heterogeneous systems and a computer program product. Background Art
[0002] When the vehicle is turned off, if the system on chip (SOC system) that is running in the vehicle is directly powered off, it may cause the system on chip to be abnormal. For example, if the system on chip is accessing the embedded multimedia card (EMMC: Embedded MultiMediaCard) operation, directly powering off the system on chip may cause EMMC data errors. Different domains of a multi-core heterogeneous system on chip are responsible for different functions. For example, some domains execute the virtualization front end, and some domains execute the virtualization back end. If the entire system on chip is powered off at the same time, it may cause confusion or abnormality in the function of the system on chip; for example, when the system on chip is started again, it may affect the startup of the system on chip. Summary of the invention
[0003] The purpose of the embodiments of the present application is to provide a system shutdown method based on multi-core heterogeneity and a computer program product.
[0004] The embodiment of the present application adopts the following technical solution: a system shutdown method based on multi-core heterogeneity, applied to a system on chip, including:
[0005] In response to a system shutdown request, shut down a first domain of the system on chip, the first domain being used to execute a virtualization front end, the virtualization front end being used to interact with a user or an upper layer application;
[0006] In response to a shutdown completion signal of the first domain, a first hardware domain in a second domain of the system on chip is closed, a portion of running code of the first hardware domain is jumped to a first memory of the system on chip, and the jumped running code is run on the first memory; wherein, before the first hardware domain is closed, it is run on a second memory located outside the system on chip;
[0007] In response to a shutdown completion signal of the first hardware domain, shutting down a second hardware domain in the second domain of the system on chip;
[0008] The second domain is used to execute requests from the virtualization front end, and the operation of the first domain is at least partially dependent on the second domain; the operation of the first hardware domain is at least partially dependent on the second hardware domain.
[0009] In some embodiments, the first hardware domain is a security domain;
[0010] In response to a system shutdown request, shutting down a first domain of the system on chip includes:
[0011] The security domain receives a system shutdown request;
[0012] Based on the system shutdown request, the security domain sends a first shutdown signal to the first domain, wherein the first domain includes at least two application domains;
[0013] In response to the first shutdown signal, the first domain is shut down.
[0014] In some embodiments, in response to the first shutdown signal, shutting down the first domain includes:
[0015] In response to the first shutdown signal, at least two of the application domains are shut down simultaneously or successively;
[0016] After the application domain is closed, the application domain sends a first closing completion signal to the security domain;
[0017] After receiving the first shutdown completion signals sent by all the application domains, the security domain closes the security domain.
[0018] In some embodiments, after the first hardware domain is shut down, the method further includes:
[0019] Part of the running code of the first hardware domain jumps to a static random access memory, wherein the static random access memory is the first memory;
[0020] The jumped execution code is executed on the static random access memory.
[0021] In some embodiments, the second hardware domain is an information security domain;
[0022] Running the jumped running code on the first memory includes:
[0023] The first memory sends a second closing signal to the information security domain;
[0024] In response to the second shutdown signal, the information security domain is closed.
[0025] In some embodiments, the second domain further includes a third hardware domain, and the third hardware domain is a multifunctional domain; wherein the operation of the multifunctional domain is at least partially dependent on the information security domain;
[0026] Before sending the second shutdown signal to the information security domain, the method further includes:
[0027] The first memory sends a third shutdown signal to the multi-functional domain;
[0028] In response to the third shutdown signal, the multi-function domain is shut down.
[0029] In some embodiments, after the multi-functional domain is closed, the method further comprises:
[0030] The multifunctional domain sends a third closing completion signal to the first memory;
[0031] In response to the third shutdown completion signal, the first memory sends a second shutdown signal to the information security domain.
[0032] In some embodiments, after the information security domain is closed, the method further includes:
[0033] The information security domain sends a second closing completion signal to the first memory;
[0034] After the first memory receives the second shutdown completion signal, the system on chip is powered off.
[0035] In some embodiments, the method further comprises:
[0036] If the security domain has not received the first closing completion signal indicating that all the application domains have been closed within a first preset time, closing the security domain;
[0037] Within a second preset time, if the first memory does not receive the third shutdown completion signal, sending a second shutdown signal to the information security domain;
[0038] Within a third preset time, when the first memory does not receive the second shutdown completion signal, the system on chip is powered off.
[0039] An embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the method described in any of the above embodiments.
[0040] The beneficial effects of the embodiments of the present application are:
[0041] According to the operation characteristics of each domain of the system on chip, each domain of the system on chip is shut down in a linked shutdown manner before the system on chip is powered off. That is, before the entire system on chip is powered off, the corresponding software operations are shut down in sequence, ensuring the normal power-off of the system on chip, avoiding the abnormal shutdown of the system on chip, and the abnormal power-on of the system on chip caused by the abnormal shutdown of the system on chip, and avoiding the occurrence of system data errors including the system on chip and peripheral hardware status errors. BRIEF DESCRIPTION OF THE DRAWINGS
[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.
[0043] Figure 1 This is a flow chart of a system shutdown method based on multi-core heterogeneity in an embodiment of the present application;
[0044] Figure 2 For the embodiment of this application Figure 1 A flowchart of an embodiment of step S10;
[0045] Figure 3 This is a flow chart of a multi-core heterogeneous system according to an embodiment of the present application;
[0046] Figure 4 For the embodiment of this application Figure 2 A flowchart of an embodiment of step S103;
[0047] Figure 5 A schematic diagram of an embodiment of a method for shutting down a multi-core heterogeneous system when the system on chip includes a multi-function domain in an embodiment of the present application;
[0048] Figure 6 For the embodiment of this application Figure 1 Flow chart of a first embodiment of step S20;
[0049] Figure 7 For the embodiment of this application Figure 1 Flow chart of a second embodiment of step S20;
[0050] Figure 8 For the embodiment of this application Figure 1 Flow chart of a third embodiment of step S20;
[0051] Fig. 9 For the embodiment of this application Figure 1 Flow chart of the fourth embodiment of step S20;
[0052] Fig.10 For the embodiment of this application Figure 1 Flow chart of the fifth embodiment of step S20 in FIG. DETAILED DESCRIPTION
[0053] Various aspects and features of the present application are described herein with reference to the accompanying drawings.
[0054] It should be understood that various modifications may be made to the embodiments of the present application. Therefore, the above description should not be considered as limiting, but only as an example of an embodiment. Other modifications within the scope and spirit of the present application will occur to those skilled in the art.
[0055] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present application and, together with the general description of the present application given above and the detailed description of the embodiments given below, serve to explain the principles of the present application.
[0056] These and other characteristics of the present application will become apparent from the following description of a preferred form of embodiment given as a non-limiting example with reference to the accompanying drawings.
[0057] It should also be understood that although the present application has been described with reference to some specific examples, those skilled in the art will be able to readily implement many other equivalent forms of the present application.
[0058] The above and other aspects, features and advantages of the present application will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.
[0059] Specific embodiments of the present application are described hereinafter with reference to the accompanying drawings; however, it should be understood that the embodiments applied for are merely examples of the present application, which may be implemented in a variety of ways. Well-known and / or repeated functions and structures are not described in detail to avoid unnecessary or redundant details that obscure the present application. Therefore, the specific structural and functional details applied for herein are not intended to be limiting, but merely serve as a basis and representative basis for the claims to teach those skilled in the art to use the present application in a variety of ways with substantially any suitable detailed structure.
[0060] This specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," all of which may refer to one or more of the same or different embodiments according to the present application.
[0061] First, the technical terms involved in the embodiments of the present application are briefly introduced.
[0062] SOC (System on Chip) refers to the integration of multiple hardware components on a single chip, such as CPU, memory controller, graphics processing unit (GPU), etc., to realize a complete computing system; SOC can contain a wafer (Die) or multiple identical or different wafers.
[0063] A multi-core heterogeneous system is composed of multiple single-core or multi-core processors of different types. Multi-core heterogeneity is a difference at the hardware level. A core heterogeneous system includes at least two processor cores with different architectures. The processor cores and the hardware resources connected to the processor cores constitute independent hardware domains.
[0064] Domain, divides the chip into different areas or functional blocks, each area or functional block is called a domain.
[0065] A hardware domain is a collection of hardware resources. Multi-core heterogeneity is a difference at the hardware level. There may be multiple hardware domains in a multi-core heterogeneous SOC. Since the processor cores are heterogeneous, there is no cache consistency hardware between them. The hardware domains composed of the terminal controller, clock controller and memory of each processor core are hard-isolated. Each processor core cannot be directly scheduled uniformly by the operating system. The hardware resources in the hardware domain of each processor core can only be accessed by its processor core.
[0066] For systems on chips running on vehicles such as cars, if the running SOC is directly powered off when the car is turned off, it may cause SOC abnormalities. For example, if the SOC is accessing the EMMC operation, directly powering off the SOC may cause EMMC data errors. Different domains of multi-core heterogeneous SOCs are responsible for different functions. For example, some domains execute the virtualization front end, and some domains execute the virtualization back end. However, the existing technology only has a shutdown function on a single domain, and there is no shutdown function for multiple domains. For multi-core heterogeneous systems, a new method of shutting down each domain in sequence is needed.
[0067] This application needs to shut down each domain in sequence according to the different functions of different domains of the system on chip to ensure that when the system on chip is powered off, the system on chip can be shut down normally without causing abnormal shutdown.
[0068] After introducing the application scenarios and design concepts of the embodiments of the present application, the technical solutions provided by the embodiments of the present application are described below.
[0069] To solve the problems in the background technology, the present application provides a system shutdown method based on multi-core heterogeneity, such as Figure 1 As shown, the system shutdown method based on multi-core heterogeneity is applied to the system on chip, and the method includes:
[0070] S10, in response to a system shutdown request, shutting down a first domain of the system on chip, wherein the first domain is used to execute a virtualization front end, and the virtualization front end is used to interact with a user or an upper-layer application.
[0071] For example, the operating system in the vehicle cab runs a system on chip, and when the car is turned off, the system on chip needs to be turned off. That is, when the vehicle is turned off, a system shutdown request is sent to the system on chip, and after the system on chip receives the system shutdown request signal, in response to the system shutdown request, the first domain of the system on chip can be shut down first, and then based on the shutdown status of the first domain, corresponding operations are performed on other domains of the system on chip.
[0072] For example, after the first domain is shut down, some hardware domains in the second domain of the system on chip are shut down. Of course, it should be noted that the first domain and the second domain are not randomly selected, and there are differences in their functions, performances, and operations, as well as a dependency relationship between the two. Specifically, the operation of the first domain depends on the second domain. When a system shutdown request is received, the first domain of the system on chip is shut down first, and the shutdown of the first domain will not affect the shutdown of the second domain. Avoid shutting down the second domain before the first domain is shut down, which causes an abnormal shutdown of the first domain. When restarting the system on chip, there may be an abnormal startup problem of the first domain.
[0073] The software has a virtualization front-end and a virtualization back-end. When shutting down the system on a chip, you need to shut down the virtualization front-end first and then the virtualization back-end to avoid abnormal shutdown of the system on a chip caused by the virtualization back-end being shut down before the virtualization front-end.
[0074] For example, the first domain is used to execute the virtualized front end, which is used to interact with users or upper-layer applications. The virtualized front end enables the front-end application to start and load faster according to the needs of the user or the upper-layer application, thereby reducing the user's waiting time. Specifically, virtualized front-end technology generally refers to the use of virtualization technology to isolate the front-end environment from the underlying hardware or operating system to achieve flexible allocation and management of front-end resources. The virtualized front end can achieve efficient sharing between front-end resources and upper-layer applications. For example, in a microservice architecture, the front-end application can be deployed and managed as an independent service, while sharing computing resources and storage resources with other microservices. Of course, the execution of the virtualized front end, that is, the operation of the first domain, depends to a certain extent on the operation of other domains of the system-on-chip.
[0075] When the system on chip is shut down, the virtualization front end needs to be shut down first, that is, when the system on chip receives a system shutdown request, the first domain used to execute the virtualization front end needs to be shut down first. The first domain can be based on the application processor core, that is, the first domain can be but is not limited to the application domain of the system on chip. The application processor core has strong processing capabilities and can independently run large-volume operating systems such as Android.
[0076] S20, in response to a shutdown completion signal of the first domain, closing a first hardware domain in a second domain of the system on chip, redirecting part of the running code of the first hardware domain to a first memory of the system on chip, and running the redirected running code on the first memory; wherein, before the first hardware domain is closed, it runs on a second memory outside the system on chip.
[0077] Exemplarily, when the first domain is closed, the first domain may generate a close completion signal and send the generated close completion signal. The system on chip may monitor and detect the close completion signal sent by the first domain. Of course, the first domain here may include one application domain, or may include more than two application domains.
[0078] After all application domains in the first domain are closed, the first hardware domain of the second domain of the system on chip is closed. Here, the second domain is used to execute requests from the virtualization front end. Or it can be understood that the second domain is used to execute the virtualization back end. Here, the operation of the first domain needs to rely on the second domain, or partially rely on the second domain. More specifically, the operation of the first domain depends on the first hardware domain of the second domain. The first hardware domain of the second domain has an ultra-fast response speed and powerful functional safety features. Each function will not fail easily, and even if it fails, it can be detected.
[0079] The system on chip can receive the system shutdown request through the first hardware domain of the second domain, and send a notification signal to the first domain in response to the system shutdown request, wherein the notification signal is used to inform the first domain to start the shutdown process. The signal indicating that the shutdown of the first domain is completed can also be sent to the first hardware domain of the second domain, and the first hardware domain of the second domain receives the shutdown completion signal of the first domain.
[0080] Of course, it is understandable that when the first domain includes more (more than two) application domains, the first hardware domain of the second domain of the system on chip is shut down when shutdown completion signals of all application domains included in the first domain are detected.
[0081] It should be further explained that if the shutdown completion signal of all application domains of the first domain is not received within a certain time (the time can be preset as a preset time), the first hardware domain of the second domain can also be closed. The length of the preset time can be selected and set according to user needs or actual conditions.
[0082] That is, after the shutdown of the first domain is completed, the first hardware domain of the second domain also enters the shutdown process. For example, the first hardware domain of the second domain may start to run its own shutdown program.
[0083] The process of the first hardware domain of the second domain entering shutdown may include: jumping part of the running code of the first hardware domain to the first memory of the system on chip, and running the jumped running code on the first memory. Before the first hardware domain is shut down, it runs on the second memory outside the system on chip.
[0084] For example, the first hardware domain usually runs on DDR (short for "Double Data Rate", "double data rate" memory), that is, runs on the second memory outside the system on chip. The first hardware domain running on the second memory can execute the shutdown function of each module to stop access to the corresponding hardware resources. That is, before the first hardware domain is shut down, the first hardware domain runs on the second memory, and the second memory is located outside the system on chip.
[0085] When the first hardware domain itself enters the shutdown procedure, after the first hardware domain stops accessing the corresponding hardware resources, the first hardware domain will stop the current running code and jump to the first memory to execute another part of the running code of the first hardware domain. Among them, different from the second memory, the first memory is the memory located in the system on chip. The first memory executes the code jumped to the first memory by the first hardware domain, and the first hardware domain is closed without affecting the shutdown of other domains of the system; at the same time, it also avoids the shutdown of other domains of the system on chip causing the shutdown of the first hardware domain to be abnormal, thereby causing the shutdown of the entire system on chip to be abnormal.
[0086] The main operations performed on the first memory may include notifying other hardware domains in the second domain to shut down, powering off the system, etc., until the shutdown of the system on chip is completed.
[0087] S30: In response to a shutdown completion signal of the first hardware domain, shut down a second hardware domain in the second domain of the system on chip.
[0088] The second domain is used to execute requests from the virtualization front end, and the operation of the first domain is at least partially dependent on the second domain; the operation of the first hardware domain is at least partially dependent on the second hardware domain.
[0089] Exemplarily, after the first hardware domain of the second domain is closed, a closing completion signal of the first hardware domain may be generated. In response to the closing completion signal of the first hardware domain, the second hardware domain in the second domain of the system on chip is closed. The second hardware domain has a high security feature and uniformly handles system data security and other related matters. The operation of the first hardware domain is at least partially dependent on the second hardware domain. The closing of the first hardware domain may be initiated first, and the closing of the second hardware domain may be performed after the closing of the first hardware domain is completed.
[0090] According to the operation characteristics of each domain of the system on chip, the embodiment of the present application closes each domain of the system on chip in a linked closing manner before the system on chip is powered off. That is, before the entire system on chip is powered off, the corresponding software operations are closed in sequence, ensuring the normal power-off of the system on chip, avoiding the problem of abnormal power-on of the system on chip caused by abnormal shutdown of the system on chip, and avoiding the occurrence of system data errors including the system on chip and peripheral hardware status errors.
[0091] In some embodiments, in combination Figure 2 and Figure 3 , the first hardware domain is a safety domain.
[0092] In response to a system shutdown request, shutting down a first domain of the system on chip includes:
[0093] S101, the security domain receives a system shutdown request.
[0094] Exemplarily, the system on chip receives the system shutdown request through the security domain. The security domain has an ultra-fast response speed and powerful functional safety features. Each function will not fail easily, and even if it fails, it can be detected. For example, for the driving system of a car, the security domain uses a security processor, which can be used for power management, communication interface with the vehicle body (CAN communication), functional safety, etc. The operation of the first domain depends on the security domain to a certain extent, and the operation of the security domain depends on the second hardware domain to a certain extent. Therefore, the security domain can be used to receive the system shutdown request, and communicate information with the first domain based on the system shutdown request, so that the first domain can enter the shutdown process first.
[0095] S102: Based on a system shutdown request, the security domain sends a first shutdown signal to the first domain, wherein the first domain includes at least two application domains.
[0096] Exemplarily, after receiving the system shutdown request, the security domain sends a first shutdown signal to the first domain, where the first shutdown signal is used to notify the first domain to shut down completely.
[0097] For example, continue to combine Figure 3 The first domain of the system on chip includes a first application domain (AP1) and a second application domain (AP2). The security domain sends a first shutdown signal to the first application domain and the second application domain respectively to notify the first application domain and the second application domain to shut down.
[0098] Of course, it is understandable that the first shutdown signal may be a shutdown signal corresponding to each application domain, for example, the first shutdown signal includes a shutdown signal notifying the first application domain to shut down and a shutdown signal notifying the second application domain to shut down. The security domain may send the above two shutdown signals to the first application domain and the second application domain respectively at the same time.
[0099] S103: In response to the first shutdown signal, shut down the first domain.
[0100] Exemplarily, in combination with the above embodiment, after receiving the first shutdown signal, the first application domain and the second application domain respond to the first shutdown signal. For example, after receiving the first shutdown signal, the first application domain and the second application domain respectively start their own shutdown processes. The first application domain and the second application domain may respectively have their own shutdown programs or shutdown functions, and the shutdown programs or shutdown functions of the first application domain and the second application domain may also run in the security domain, and the shutdown programs or shutdown functions of the first application domain and the second application domain are started through the security domain.
[0101] After the closing program or closing function of the first application domain is executed, the closing of the first application domain is completed. After the closing program or closing function of the second application domain is executed, the closing of the second application domain is completed.
[0102] In some embodiments, in combination Figure 4 and Figure 5 , in response to the first shutdown signal, shutting down the first domain, comprising:
[0103] S1031: In response to the first shutdown signal, at least two of the application domains are closed simultaneously or successively.
[0104] For example, when the first domain includes more than two application domains, the closing completion speeds of the two or more application domains may be the same or different. The closing completion speed of the application domain is affected by many factors, including but not limited to the complexity of the system, the number of currently running processes, the occupation of system resources, and whether errors or exceptions occur during the closing process.
[0105] Continuing with the above embodiment, the first domain includes a first application domain and a second application domain. The progress and time of completing the shutdown of the first application domain and the second application domain may be the same or different.
[0106] S1032: After the application domain is closed, the application domain sends a first closing completion signal to the security domain.
[0107] Exemplarily, the first application domain and the second application domain respectively send out first shutdown completion signals corresponding to themselves based on the progress and time of their respective completion of shutdown. Specifically, the first shutdown completion signal is sent by the application domain to the security domain, and the security domain receives the above-mentioned first shutdown completion signal. The first shutdown completion signal is used to indicate that the shutdown of the application domain is complete. In the case where the first domain includes the first application domain and the second application domain, the first shutdown completion signal includes a shutdown completion signal indicating that the shutdown of the first application domain is complete and a shutdown completion signal indicating that the shutdown of the second application domain is complete, and the shutdown completion signals of the two application domains are independent of each other. After the two application domains complete the shutdown, each sends out a shutdown completion signal corresponding to itself, instead of sending a first shutdown completion signal to the security domain after all application domains (APs) have completed the shutdown.
[0108] For example, after receiving the first shutdown signal, the first application domain completes the shutdown of the first application domain within a first time, and the first application domain generates a shutdown completion signal, which indicates that the shutdown of the first application domain is complete. The first application domain sends the shutdown completion signal to the security domain. After receiving the shutdown signal, the second application domain completes the shutdown of the second application domain within a second time, and the second application domain generates another shutdown completion signal, which indicates that the shutdown of the second application domain is complete. The second application domain sends another shutdown completion signal to the security domain.
[0109] The length of the first time may be the same as or different from the length of the second time. When the first time is shorter than the second time, the security domain first receives a shutdown completion signal indicating that the first application domain has been shut down, and then receives another shutdown completion signal indicating that the second application domain has been shut down.
[0110] S1033: After receiving the first shutdown completion signals sent by all the application domains, the security domain closes the security domain.
[0111] Exemplarily, in combination with the above embodiment, when the first domain includes two application domains, the first application domain and the second application domain, after the security domain receives the shutdown completion signals corresponding to the first application domain and the second application domain respectively, it means that both the first application domain and the second application domain have been closed. At this time, closing the security domain will not affect the closing of the application domain, that is, it will not cause abnormal closing of the application domain. At this time, the security domain of the system on chip can be closed.
[0112] In some embodiments, in combination Figure 6 , after the first hardware domain is closed, the method further includes:
[0113] S201, part of the running code of the first hardware domain jumps to the static random access memory, wherein the static random access memory is the first memory.
[0114] Exemplarily, the first memory may be a static random access memory (IRAM: Internal Random Access Memory). After the first hardware domain is closed, some code still needs to be run to execute subsequent steps. This part of the code jumps from the first hardware domain to the IRAM of the system on chip, and the IRAM executes the code jumped from the first hardware domain to the IRAM, thereby closing the first hardware domain without affecting the closing of other domains of the system; at the same time, it also avoids the closing of other domains of the system on chip causing the closing of the first hardware domain to be abnormal, thereby causing the closing of the entire system on chip to be abnormal.
[0115] S202, running the jumped execution code on the static random access memory.
[0116] The main operations of the running code after the IRAM running jump may include: notifying other hardware domains of the second domain to shut down, powering off the system, etc.
[0117] In some embodiments, in combination Figure 7 The second hardware domain is the information security domain (secure domain), referred to as SEC. The information security domain has high security characteristics and uniformly handles data security-related matters. The information security domain uses an information security processor, which can be a collection of the information security domain (HSM), the storage service end (eMMC), and the OTA server end (eMMC).
[0118] Running the jumped running code on the first memory includes:
[0119] S207: The first memory sends a second shutdown signal to the information security domain.
[0120] Exemplarily, after the first hardware domain is shut down, the information security domain on which the first hardware domain depends can be shut down. Specifically, the first memory generates a second shutdown signal and sends the second shutdown signal to the information security domain to notify the information security domain to start the shutdown process.
[0121] S208: In response to the second closing signal, close the information security domain.
[0122] Exemplarily, after receiving the second shutdown signal from the first memory, the information security domain responds to the second shutdown signal. For example, the information security domain can run its own shutdown program or shutdown function, so that the information security domain can be closed after its shutdown program or shutdown function is completed.
[0123] The information security domain can be the last domain to be closed by the system on chip. After other domains that depend on the operation of the information security domain are completed, the closing of the information security domain will not have an adverse impact on the closing of other domains and cause abnormal closing of other domains.
[0124] In some embodiments, the second domain also includes a third hardware domain, and the third hardware domain is a multi-function domain (mp domain). The multi-function domain uses a multi-function processor. In combination with the car, it is used to run various back-ends, such as sound, display, backlight, and management of the back-end of reversing. The operation of the first domain may also depend on the operation of the multi-function domain to a certain extent. Therefore, the first domain enters the shutdown process earlier than the multi-function domain. The operation of the multi-function domain depends at least in part on the information security domain. Therefore, before the information security domain is closed, the shutdown process of the multi-function domain is started first. For example, the storage of the multi-function domain depends on the information security domain, so the multi-function domain enters the shutdown process before the information security domain to avoid the relevant data generated by the operation of the multi-function domain from being unable to be stored in the information security domain.
[0125] Combination Figure 8 , before sending the second shutdown signal to the information security domain, the method further includes:
[0126] S203: The first memory sends a third shutdown signal to the multi-functional domain.
[0127] Exemplarily, before the information security domain starts the shutdown process, the multifunctional domain is closed first. The closing of the multifunctional domain needs to be based on a corresponding shutdown signal, which can be a third shutdown signal. The first memory can generate the third shutdown signal and send the third shutdown signal to the multifunctional domain to notify the multifunctional domain to start the shutdown process.
[0128] S204: In response to the third shutdown signal, shut down the multifunctional domain.
[0129] Exemplarily, after receiving the third shutdown signal, the multifunctional domain starts to run the corresponding shutdown program or shutdown function, and after the corresponding shutdown program or shutdown function is completed, the multifunctional domain completes the shutdown.
[0130] In some embodiments, in combination Fig. 9 After the multifunctional domain is closed, the method further comprises:
[0131] S205: The multifunctional domain sends a third closing completion signal to the first memory.
[0132] Exemplarily, after the multifunctional domain is closed, the information security domain needs to be closed, and the closing of the information security domain needs to be based on the corresponding closing signal. Therefore, after the multifunctional domain is closed, the multifunctional domain can send a third closing completion signal to the first memory to indicate that the multifunctional domain has been closed, and at this time, the closing of the information security domain will no longer have an adverse effect on the closing of the multifunctional domain.
[0133] In combination with the specific usage scenarios of the car, the closing of the multi-function domain can be completed but is not limited to the following specific manifestations: the music in the car cab, navigation prompts and other sounds are turned off; the display screen is turned off and no relevant information is displayed; the lights inside and outside the car are turned off, etc.
[0134] S206: In response to the third shutdown completion signal, the first memory sends a second shutdown signal to the information security domain.
[0135] Exemplarily, after receiving the third shutdown completion signal sent by the multi-functional domain, the first memory generates a second shutdown signal in response to the third shutdown completion signal, and sends the second shutdown signal to the information security domain to notify the information security domain that it can enter the shutdown process.
[0136] Continuing with the above embodiment, after the sound, display, and vehicle lights in the car are turned off, the information security domain is still running. Although from the external performance, the relevant functions of the car have been turned off, the relevant data may still rely on the information security domain for storage. Therefore, the first memory needs to send a second shutdown signal to the information security domain to notify it to shut down.
[0137] In some embodiments, in combination Fig.10 After the information security domain is closed, the method further includes:
[0138] S209: The information security domain sends a second closing completion signal to the first memory.
[0139] Exemplarily, the completion of the shutdown of the information security domain does not mean that the shutdown of the system on chip is completed. Therefore, after the information security domain is closed, a second shutdown completion signal can be generated, and the second shutdown completion signal indicates that the information security domain is closed. The information security domain sends the second shutdown completion signal to the first memory, and the first memory can make a corresponding response after receiving the second shutdown completion signal.
[0140] S210: After the first memory receives the second shutdown completion signal, the system on chip is powered off.
[0141] Exemplarily, after receiving the second shutdown completion signal from the information security domain, the first memory may generate a power-off signal, and the system on chip completes power-off.
[0142] In some embodiments, the method further comprises:
[0143] If the security domain has not received the first shutdown completion signal indicating that all the application domains have been closed within a first preset time, the security domain is closed.
[0144] Exemplarily, if the security domain does not receive a signal that one or more application domains in the first domain have completed closing within a set time, for example, the first domain includes a first application domain and a second application domain, and the first application domain and / or the second application domain have not completed closing within the first preset time, the security domain will be forced to close and continue to execute subsequent steps.
[0145] If the security domain does not receive the first shutdown completion signal of all application domains within the first preset time, the following situations may occur:
[0146] The first situation is that there is an application domain in the first domain that has not been completely closed, and the application domain may not be completely closed in a short time;
[0147] The second situation is that all application domains in the first domain have completed closing, but the first closing completion signal is not successfully sent to the security domain for some reason, or is not successfully received by the security domain.
[0148] Regardless of which of the above situations occurs, the security domain will be forced to shut down and continue to execute subsequent steps to prevent other domains from being unable to enter the shutdown process and the entire on-chip system from being unable to shut down normally.
[0149] The first preset time can be set according to user needs or actual conditions.
[0150] Within a second preset time, when the first memory does not receive the third shutdown completion signal, a second shutdown signal is sent to the information security domain.
[0151] Exemplarily, the closing time of the multifunctional domain is also affected by many factors, such as the closing progress of the lights inside and outside the car, the closing progress of the prompt sounds of music, navigation, etc. A second preset time can be set in advance, and the second preset time is the time when the multifunctional domain can be completed under normal conditions. If the first memory fails to receive the third closing completion signal within the second preset time, that is, the multifunctional domain has not successfully completed the closing, or the multifunctional domain has been completed, but the third closing completion signal it sent has not been sent to the first memory (or the first memory has not successfully received the third closing completion signal), at this time, if you continue to wait for the closing of the multifunctional domain, it may cause other domains of the system on chip to never enter the closing process, and the entire system on chip cannot be closed normally. Therefore, it is necessary to send a second closing signal to the information security domain to notify the information security domain to start entering the closing process.
[0152] The second preset time may be the same as or different from the first preset time, and the specific time may be set according to user needs and specific circumstances.
[0153] Within a third preset time, when the first memory does not receive the second shutdown completion signal, the system on chip is powered off.
[0154] Exemplarily, the closing of the information security domain is also affected by many factors, such as the progress of the data storage process. A third preset time can be preset, and the third preset time is the time when the information security domain can be completed under normal conditions. If the first memory fails to receive the third closing completion signal within the second preset time, that is, the information security domain has not been successfully closed, or the information security domain has been completed, but the second closing completion signal it sent has not been sent to the first memory (or the first memory has not successfully received the second closing completion signal). At this time, a power-off signal can be generated so that the system on chip can be powered off in response to the power-off signal, and the entire system on chip is completed.
[0155] An embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of the method described in any of the above embodiments.
[0156] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0157] Those of ordinary skill in the art will appreciate that the various illustrative logic blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0158] In the several embodiments provided in this application, it should be understood that the disclosed systems and methods can be implemented in other ways. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0159] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk), etc.
[0160] Multiple embodiments of the present application are described in detail above, but the present application is not limited to these specific embodiments. Those skilled in the art can make various variations and modifications to the embodiments based on the concept of the present application, and these variations and modifications should all fall within the scope of protection required by the present application.
Claims
1. A system shutdown method based on multi-core heterogeneity, applied to system-on-chip, It is characterized in that include: In response to a system shutdown request, shut down a first domain of the system on chip, the first domain being used to execute a virtualization front end, the virtualization front end being used to interact with a user or an upper layer application; In response to a shutdown completion signal of the first domain, a first hardware domain in a second domain of the system on chip is closed, a portion of running code of the first hardware domain is jumped to a first memory of the system on chip, and the jumped running code is run on the first memory; wherein, before the first hardware domain is closed, the first hardware domain is run on a second memory located outside the system on chip; In response to a shutdown completion signal of the first hardware domain, shutting down a second hardware domain in the second domain of the system on chip; The second domain is used to execute requests from the virtualization front end, and the operation of the first domain is at least partially dependent on the second domain; the operation of the first hardware domain is at least partially dependent on the second hardware domain.
2. The method for shutting down a multi-core heterogeneous system according to claim 1, It is characterized in that The first hardware domain is a security domain; In response to a system shutdown request, shutting down a first domain of the system on chip includes: The security domain receives a system shutdown request; Based on the system shutdown request, the security domain sends a first shutdown signal to the first domain, wherein the first domain includes at least two application domains; In response to the first shutdown signal, the first domain is shut down.
3. The system shutdown method based on multi-core heterogeneity according to claim 2, It is characterized in that In response to the first shutdown signal, shutting down the first domain includes: In response to the first shutdown signal, at least two of the application domains are shut down simultaneously or successively; After the application domain is closed, the application domain sends a first closing completion signal to the security domain; After receiving the first shutdown completion signals sent by all the application domains, the security domain closes the security domain.
4. The method for shutting down a system based on multi-core heterogeneity according to claim 1, It is characterized in that After the first hardware domain is closed, the method further includes: Part of the running code of the first hardware domain jumps to a static random access memory, wherein the static random access memory is the first memory; The jumped execution code is executed on the static random access memory.
5. The method for shutting down a multi-core heterogeneous system according to claim 3, It is characterized in that The second hardware domain is an information security domain; Running the jumped running code on the first memory includes: The first memory sends a second closing signal to the information security domain; In response to the second shutdown signal, the information security domain is closed.
6. The method for shutting down a multi-core heterogeneous system according to claim 5, It is characterized in that The second domain further includes a third hardware domain, and the third hardware domain is a multifunctional domain; wherein the operation of the multifunctional domain at least partially depends on the information security domain; Before sending the second shutdown signal to the information security domain, the method further includes: The first memory sends a third shutdown signal to the multi-functional domain; In response to the third shutdown signal, the multi-function domain is shut down.
7. The method for shutting down a multi-core heterogeneous system according to claim 6, It is characterized in that After the multifunctional domain is closed, the method further includes: The multifunctional domain sends a third closing completion signal to the first memory; In response to the third shutdown completion signal, the first memory sends a second shutdown signal to the information security domain.
8. The method for shutting down a multi-core heterogeneous system according to claim 7, It is characterized in that After the information security domain is closed, the method further includes: The information security domain sends a second closing completion signal to the first memory; After the first memory receives the second shutdown completion signal, the system on chip is powered off.
9. The method for shutting down a multi-core heterogeneous system according to claim 8, It is characterized in that The method further comprises: If the security domain has not received the first closing completion signal indicating that all the application domains have been closed within a first preset time, closing the security domain; Within a second preset time, if the first memory does not receive the third shutdown completion signal, sending a second shutdown signal to the information security domain; Within a third preset time, when the first memory does not receive the second shutdown completion signal, the system on chip is powered off.
10. A computer program product comprising a computer program / instructions, It is characterized in that When the computer program / instructions are executed by a processor, the steps of the method as claimed in any one of claims 1 to 9 are implemented.
