CN109213627B - Fault-tolerant operation method and electronic device using same - Google Patents
Fault-tolerant operation method and electronic device using same Download PDFInfo
- Publication number
- CN109213627B CN109213627B CN201710532829.XA CN201710532829A CN109213627B CN 109213627 B CN109213627 B CN 109213627B CN 201710532829 A CN201710532829 A CN 201710532829A CN 109213627 B CN109213627 B CN 109213627B
- Authority
- CN
- China
- Prior art keywords
- program
- file
- fault
- operating system
- backup
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Retry When Errors Occur (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention provides a fault-tolerant operation method and an electronic device using the same. The method comprises the following steps: executing a first program by a first execution file installed in the electronic device; when an error occurs to cause the first program to be suspended, transmitting a suspension notice to a fault-tolerant module by the operating system, and obtaining suspension address information of the first program by the fault-tolerant module; and transmitting the suspension address information to the operating system by the fault tolerance module, so that the operating system calls the first execution file to continue executing the first program based on the suspension address information.
Description
Technical Field
The present invention relates to an operating method of an electronic device, and more particularly, to a fault-tolerant operating method and an electronic device using the same.
Background
In the existing recovery method, no matter the brand factory development or microsoft built-in system recovery method, once a Fatal error (Fatal error) occurs, the recovery process cannot be executed continuously, and the operation system cannot be entered smoothly. However, in many cases, the phenomenon is not repeated again by system reinstallation or recovery flow. It follows that many so-called "fatal errors" do not have a significant impact on the system, and therefore there is no fault-tolerant recovery mechanism, which is a nuisance for users and a heavy cost for enterprises. In addition, in the system backup program, if a backup failure occurs at a certain file address, the whole backup process needs to be executed again.
Disclosure of Invention
In view of the above, the present invention provides a fault tolerant operation method and an electronic device using the same, which can improve the execution efficiency of the restore/backup program.
An embodiment of the present invention provides a fault tolerant operation method for an electronic device having an operating system, the method including: executing a first program by a first execution file installed in the electronic device; when an error occurs to cause the first program to be suspended, transmitting a suspension notice to a fault-tolerant module by the operating system, and obtaining suspension address information of the first program by the fault-tolerant module; and transmitting the suspension address information to the operating system by the fault tolerance module, so that the operating system calls the first execution file to continue executing the first program based on the suspension address information.
Another embodiment of the present invention provides an electronic apparatus, which includes a storage device and a processor. The storage device comprises an operating system, a fault-tolerant module and a first execution file, and is used for executing a first program. The processor is connected to the storage device and is used for executing the operating system, the fault-tolerant module and the first execution file. When an error occurs to cause the first program to be suspended, the processor transmits a suspension notice to the fault-tolerant module through the operating system, and acquires suspension address information of the first program through the fault-tolerant module. In addition, the processor transmits the suspension address information to the operating system through the fault tolerance module, so that the operating system calls the first execution file to continue executing the first program based on the suspension address information.
Based on the above, the system restore/backup of the present invention has a fault-tolerant mechanism, and the complete restore/backup program is not repeatedly executed due to execution failure, thereby reducing the rework cost.
In order to make the aforementioned and other features and advantages of the invention more comprehensible, embodiments accompanied with figures are described in detail below.
Drawings
Fig. 1 is a schematic diagram of an electronic device with a restore/backup fault tolerance mechanism according to an embodiment of the invention.
FIG. 2 is a flow diagram illustrating a method of fault tolerant operation in accordance with one embodiment of the present invention.
Fig. 3A, 3B and 3C are schematic diagrams illustrating a backup program according to an embodiment of the invention.
FIG. 4 is a flow diagram illustrating a method of fault tolerant operation in accordance with another embodiment of the present invention.
Description of the reference numerals
100: electronic device
110: processor with a memory having a plurality of memory cells
120: storage device
121: fault tolerant module
122: operation system
123: execution file
301: file system
30: storage space
31: operating System (OS) partitions
32: user data area
33: reserved area
S205 to S220, S401 to S407: steps of a fault tolerant method of operation
Detailed Description
Fig. 1 is a schematic diagram of an electronic device with a restore/backup fault tolerance mechanism according to an embodiment of the invention. Referring to fig. 1, an electronic apparatus 100 includes a processor 110 and a storage device 120. The processor 110 is connected to a storage device 120.
The Processor 110 is, for example, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Physical Processing Unit (PPU), a programmable Microprocessor (Microprocessor), an embedded control chip, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), or the like.
The storage device 120 is a nonvolatile storage unit such as a Solid State Disk (SDD), a Hard Disk Drive (HDD), or a Flash Memory (Flash Memory). The storage device 120 includes a fault tolerant module 121, an operating system 122 and an execution file 123 (also referred to as a first execution file) for executing a predetermined program (also referred to as a first program). For example, the fault-tolerant module 121, the operating system 122 and the execution file 123 are installed in the electronic device 100, and the processor 110 may execute the fault-tolerant module 121, the operating system 122 and the execution file 123 to execute the first program. In addition, the fault tolerant module 121 can be implemented by software, hardware or a combination of software and hardware, and the invention is not limited thereto.
In one embodiment, the execution file 123 is a restore execution file for executing a restore process. In one embodiment, the execution file 123 is a backup execution file for executing a backup program. In an embodiment, the execution file 123 may also include a restore execution file and a backup execution file, so that the processor 110 can selectively execute the restore program or the backup program through the execution file 123. In addition, the fault tolerant module 121 obtains the suspension address information of the first program when the first program (which may be a restore program or a backup program) is suspended, so as to continue the first program that is not completed later.
More specifically, in one embodiment, after the first program starts to execute, when an error occurs to cause the first program to be suspended, the OS 122 sends a suspension notification to the fault tolerant module 121, and the fault tolerant module 121 obtains the suspension address information of the first program. Then, the fault tolerance module 121 transmits the suspension address message to the operating system 122, so that the operating system 122 calls the execution file 123 to continue executing the first program based on the suspension address message.
First embodiment
In the first embodiment, the execution file 123 is a recovery execution file, which is used to execute a recovery procedure. The steps of the fault-tolerant operation method according to the first embodiment are described below with the electronic device 100. FIG. 2 is a flow diagram of a method of fault tolerant operation in accordance with an embodiment of the present invention. It should be noted that the fault tolerant operation method of fig. 2 may also be referred to as a restoration method.
Referring to fig. 1 and fig. 2, in step S205, the execution file 123 (i.e., the recovery execution file) executes a recovery procedure. The execution file 123 is, for example, recovery. The user can use the input device such as mouse, keyboard, touch device to click the execution file 123, and after the execution file 123 is clicked, it will be loaded into the system memory to execute the recovery procedure.
Next, in step S210, when an error occurs during the execution of the restore program and the restore program is suspended, the operating system 122 transmits the process information (process information) of the restore program to the fault tolerant module 121. Specifically, when an error occurs and the recovery process is suspended, the operating system 122 sends a suspension notification (also referred to as a recovery suspension notification) to the fault tolerant module 121. When the fault tolerant module 121 receives the recovery suspension notification, the fault tolerant module 121 sends a request to the operating system 122. After the os 122 receives the request, the os 122 transmits the schedule information of the restore procedure to the fault tolerant module 121.
The execution file 123 stores the details of the process in the operating system 122 when executing the restore program. For example, the execution file 123 may store the virtual memory address and the page contents currently being read to the operating system 122. Therefore, when the recovery procedure is aborted due to an error, the operating system 122 can transmit the schedule information to the fault-tolerant module 121 for analysis by the fault-tolerant module 121.
In step S215, the trip information is analyzed by the fault tolerance module 121 to obtain address information of the recovery program at the time of suspension. Here, the address information (i.e., the suspension address information) includes execution information and physical address information. Specifically, the fault tolerant module 121 obtains the virtual memory address and the page contents from the program information. Then, the fault tolerance module 121 resolves the virtual memory address to obtain the execution information of the recovery program in the user mode when the fault is present. Furthermore, the fault tolerant module 121 parses the page content to obtain the entity address information of the restore program in the kernel mode. That is, the fault tolerant module 121 parses the page content to obtain the core mode execution procedure, and performs a reverse translation for the core mode execution procedure to obtain the entity address information, i.e., the address of the entity memory to which the run of the recovery program is mapped.
The execution information in user mode records the details of the process of the execution file 123 in user mode. Such as the action being performed in user mode, which file to call, the function being performed, the function or file to be performed next, etc. The entity address information in the kernel mode records details of the flow of the execution file 123 in the kernel mode. For example, when an error occurs in core mode, which memory address to execute to and which memory address to execute next.
Any program executing on the operating system 122 obtains a physical address through the virtual memory and paging techniques, and completes execution. The virtual memory can be used to know the process or thread (thread), the program behavior, and even the detailed flow, calling program, etc. contained in each program. In addition, if the page contents of a trip are fetched, it is known which physical or logical memory address the trip is currently at.
After obtaining the address information of the recovery program when the recovery program is suspended, in step S220, the fault tolerant module 121 transmits the address information to the operating system 122, so that the operating system 122 calls the execution file 123 to continue executing the (incomplete) recovery program. That is, the next physical memory address in the backup file contents is executed by the OS 122 calling the execution file 123, and the restore process is restarted from the physical memory address.
Second embodiment
In the second embodiment, the execution file 123 is a backup execution file for executing a backup program. The steps of the fault-tolerant operation method of the second embodiment are described below with the electronic device 100. Fig. 3A, 3B and 3C are schematic diagrams illustrating a backup program according to an embodiment of the invention. FIG. 4 is a flow diagram illustrating a method of fault tolerant operation in accordance with another embodiment of the present invention. It should be noted that the fault tolerant operation method of fig. 4 may also be referred to as a backup method.
Referring to fig. 1, fig. 3A and fig. 4, the storage device 120 has a storage space 30. For example, the storage space 30 may be a storage space of a nonvolatile storage unit such as a solid state disk, a hard disk, a flash memory, or a combination thereof. The storage space 30 is divided into an Operating System (OS) partition 31 and a user data area 32. Operating System (OS) partition 31 is used to store operating system 122 and files related to the operation of operating system 122. The user data area 32 is used for storing user data. For example, the user data includes a media file and/or an application file, etc. that is instructed to be stored by the user.
Assume that the file to be backed up (also referred to as a backup file) 301 is a file in the OS partition 31, and that the file 301 is stored at physical addresses 1000-1400 in the OS partition 31. For example, a physical address may refer to a physical block (block) address or a physical memory address of any size. In one embodiment, the physical addresses 1000-1400 are also referred to as file block addresses occupied by the file 301. It should be noted that, in the present embodiment, the file block addresses occupied by the file 301 are consecutive (e.g., 1000-1400). However, in another embodiment, the file block addresses occupied by the file 301 may be discontinuous.
In step S401, when the backup program for the file 301 is started, the OS 122 transmits the use block information of the file 301 to the fault tolerant module 121. For example, the block information of file 301 is associated with information indicating that file 301 is stored at physical addresses 1000-1400. In step S402, the fault tolerant module 121 allocates the reserved area 33 in the storage device 120 according to the used block information of the file 301. The reserved area 33 is used for storing the archive 301 through the backup program.
Taking fig. 3A as an example, the fault tolerant module 121 allocates a reserved area 33 in the storage space 30 according to the used block information of the file 301, and the reserved area 33 is used for storing the data copied from the physical addresses 1000-1400 in the backup procedure for the file 301. In addition, the storage capacity of the reserved area 33 is consistent with the file size of the file 301. For example, the storage capacity of reserved area 33 may be (approximately) equal to or greater than the archive size of archive 301. Thus, it is ensured that the file 301 can be completely stored in the reserved area 33 during the backup process for the file 301.
In step S403, the fault tolerant module 121 obtains file block addresses occupied by the file 301, i.e. physical addresses 1000 to 1400, according to the block information of the file 301. In an embodiment, step S403 may be performed before step S402, or performed together with step S402, to determine the reserved area 33 according to the file block address occupied by the file 301. In addition, the fault tolerant module 121 can also calculate the file size of the file 301 according to the block information of the file 301. For example, the file size of the file 301 is (approximately) equal to the total capacity of the physical addresses 1000-1400.
In step S404, after starting the backup process for the file 301, the fault tolerant module 121 starts a counter. The count value of the counter corresponds to one of the file block addresses of the file 301. Taking FIG. 3A as an example, the backup process for the file 301 starts from the physical address 1000, and stores the data in the physical addresses 1000-1400 in the reserved area 33 sequentially. The count value of the counter can be used to evaluate which physical address of the physical addresses 1000-1400 the current backup program is executed to.
In step S405, when the backup process for the file 301 is suspended due to an error, the OS 122 sends a suspension notification (also called backup suspension notification) to the fault tolerant module 121. In step S406, after receiving the suspension notification, the fault tolerant module 121 obtains the first file block address of the file block addresses according to the count value. It should be noted that the first file block address is the file block address where the error occurs. Then, in step S407, the fault tolerant module 121 transmits the first file block address to the operating system 122, so that the operating system 122 calls the execution file 123 to continue executing the backup program based on the first file block address.
For example, in FIG. 3B and FIG. 3C, it is assumed that the backup process is terminated when a storage failure occurs while the backup process is executed to the physical address 1250 (i.e., data is read from the physical address 1250 and stored in the reserved area 33). At this time, the fault tolerant module 121 may know that the error occurs when the backup program is accessing the physical address 1250 according to the counter value of the counter when the backup program is suspended. Thus, the fault tolerance module 121 may set the physical address 1250 as the first file block address and include the abort address information to the operating system 122. Accordingly, the operating system 122 can instruct the execution file 123 to continue executing the incomplete backup program from the physical address 1250, for example, to continue storing the data stored in the physical addresses 1250-1400 into the reserved area 33.
It is to be noted that, the steps in fig. 2 and fig. 4 can be implemented as a plurality of program codes or circuits, and the invention is not limited thereto. In addition, the embodiments shown in fig. 2 and fig. 4 can be used alone or in combination, and the invention is not limited thereto.
In summary, the present invention implements a set of tool programs or circuits (fault tolerant module), which can obtain a certain physical address (or physical memory address) and a next physical address (or next physical memory address) of a backup file executed during program interruption through the fault tolerant module when a recovery program or a backup program is interrupted due to an error. Then, the operating system can call the execution file to restart the restore program or the backup program from the address, and continue to execute the unfinished (remained) restore/backup program. Therefore, the whole restoring program or the backup program is not required to be executed again because a small part of programs fail to be executed, and the execution efficiency of the restoring/backup program can be improved.
Although the present invention has been described with reference to the above embodiments, it should be understood that various changes and modifications can be made therein by those skilled in the art without departing from the spirit and scope of the invention.
Claims (12)
1. A fault tolerant method of operation for an electronic device having an operating system, the method comprising:
executing a first program by a first execution file installed in the electronic device, wherein the first execution file comprises a reduction execution file, and the first program comprises a reduction program;
when an error occurs to cause the restoration program to be suspended, transmitting a suspension notice and the travel information of the restoration program to a fault-tolerant module by the operating system;
obtaining, by the fault tolerant module, virtual memory addresses and paging contents from the trip information;
analyzing the virtual memory address to obtain the execution information of the restoring program in a user mode;
analyzing the paging content to obtain entity address information of the restoring program in a core mode; and
transmitting, by the fault tolerance module, an abort address message to the operating system, so that the operating system calls the restore execution file to continue executing the restore program based on the abort address message, wherein the abort address message includes the execution message and the entity address message.
2. The fault tolerant operation method of claim 1 wherein the step of transmitting, by the operating system, the suspension notification and the trip information of the restore program to the fault tolerant module comprises:
transmitting, by the fault tolerant module, a request to the operating system after the fault tolerant module receives the suspension notification; and
after the operating system receives the request, the travel information of the restoring program is transmitted to the fault-tolerant module.
3. The method of fault tolerant operation of claim 1 wherein parsing the page contents to obtain the entity address information of the restore program in the kernel mode comprises:
analyzing the paging content to obtain the execution process of the core mode; and
reverse group translation for the execution of the core mode to obtain the entity address information.
4. The fault tolerant operation method of claim 1 wherein the first execution file further comprises a backup execution file, the first program further comprises a backup program, and the method further comprises:
when the backup program is started, the operating system transmits the use block information of the backup file to the fault-tolerant module; and
allocating, by the fault tolerant module, a reserved area in a storage device according to the usage block information,
wherein the reserved area is used for storing the backup file through the backup program, and the storage capacity of the reserved area is consistent with the file size of the backup file.
5. The method of fault tolerant operation of claim 4 further comprising:
the fault-tolerant module obtains at least one file block address occupied by the backup file according to the using block information; and
after the backup program is started, a counter is started by the fault tolerance module, wherein the count value of the counter corresponds to one of the at least one file block address.
6. The method of fault tolerant operation of claim 5 further comprising:
when the backup program is suspended due to an error, obtaining a first file block address of the at least one file block address by the fault tolerance module according to the count value of the counter, and
transmitting, by the fault tolerance module, the first file block address to the operating system, such that the operating system calls the backup execution file to continue executing the backup program based on the first file block address.
7. An electronic device, comprising:
a storage device, comprising:
an operating system;
a fault tolerant module; and
the first execution file executes a first program, wherein the first execution file comprises a reduction execution file, and the first program comprises a reduction program; and
a processor connected to the storage device for executing the operating system, the fault tolerant module and the first execution file,
wherein when an error occurs to cause the recovery program to abort, the processor transmits an abort notification and the run-time information of the recovery program to the fault-tolerant module via the operating system,
the processor obtains the virtual memory address and the paging content from the journey information through the fault-tolerant module,
the processor resolves the virtual memory address to obtain the execution information of the recovery program in the user mode,
the processor parses the page contents to obtain the entity address information of the restore program in the kernel mode, and
the processor transmits pause address information to the operating system through the fault-tolerant module, so that the operating system calls the restoring execution file to continue executing the restoring program based on the pause address information, wherein the pause address information comprises the execution information and the entity address information.
8. The electronic device of claim 7, wherein the processor further transmits a request to the operating system through the fault tolerant module after the fault tolerant module receives the suspension notification, an
After the operating system receives the request, the processor also transmits the trip information of the restore program to the fault tolerant module via the operating system.
9. The electronic device of claim 7, wherein the processor further parses the page contents to obtain an execution procedure of the core mode by the fault tolerant module, and performs a reverse translation for the execution procedure of the core mode to obtain the entity address information.
10. The electronic apparatus according to claim 7, wherein the first execution file further comprises a backup execution file, the first program further comprises a backup program, and when the backup program is started, the processor further transmits the use block information of the backup file to the fault-tolerant module via the operating system, and configures the reserved area in the storage device via the fault-tolerant module according to the use block information,
wherein the reserved area is used for storing the backup file through the backup program, and the storage capacity of the reserved area is consistent with the file size of the backup file.
11. The electronic device of claim 10, wherein the processor further obtains at least one file block address occupied by the backup file according to the usage block information through the fault tolerant module, and starts a counter through the fault tolerant module after starting the backup program, wherein a count value of the counter corresponds to one of the at least one file block address.
12. The electronic device of claim 11, wherein the processor further obtains, by the fault tolerance module, a first file block address of the at least one file block address according to the count value of the counter when the backup program is suspended due to an error, and
the processor transmits the first file block address to the operating system through the fault tolerance module, so that the operating system calls the backup execution file to continue executing the backup program based on the first file block address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710532829.XA CN109213627B (en) | 2017-07-03 | 2017-07-03 | Fault-tolerant operation method and electronic device using same |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710532829.XA CN109213627B (en) | 2017-07-03 | 2017-07-03 | Fault-tolerant operation method and electronic device using same |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109213627A CN109213627A (en) | 2019-01-15 |
| CN109213627B true CN109213627B (en) | 2021-10-22 |
Family
ID=64991789
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710532829.XA Active CN109213627B (en) | 2017-07-03 | 2017-07-03 | Fault-tolerant operation method and electronic device using same |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109213627B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101377750A (en) * | 2007-09-21 | 2009-03-04 | 中国科学院计算技术研究所 | System and method for cluster fault toleration |
| CN101448028A (en) * | 2009-01-08 | 2009-06-03 | 成都市华为赛门铁克科技有限公司 | Method for protecting continuous data, device and system thereof |
| US7853825B2 (en) * | 2005-08-16 | 2010-12-14 | Hewlett-Packard Development Company, L.P. | Methods and apparatus for recovering from fatal errors in a system |
| CN102541739A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Test method and device of Linux operating system |
| CN102890637A (en) * | 2009-06-01 | 2013-01-23 | 宇瞻科技股份有限公司 | Electronic device and method for installing instant-on operation systems |
| CN105718355A (en) * | 2016-01-21 | 2016-06-29 | 中国人民解放军国防科学技术大学 | Online learning-based super computer node active fault-tolerant method |
-
2017
- 2017-07-03 CN CN201710532829.XA patent/CN109213627B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7853825B2 (en) * | 2005-08-16 | 2010-12-14 | Hewlett-Packard Development Company, L.P. | Methods and apparatus for recovering from fatal errors in a system |
| CN101377750A (en) * | 2007-09-21 | 2009-03-04 | 中国科学院计算技术研究所 | System and method for cluster fault toleration |
| CN101448028A (en) * | 2009-01-08 | 2009-06-03 | 成都市华为赛门铁克科技有限公司 | Method for protecting continuous data, device and system thereof |
| CN102890637A (en) * | 2009-06-01 | 2013-01-23 | 宇瞻科技股份有限公司 | Electronic device and method for installing instant-on operation systems |
| CN102541739A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Test method and device of Linux operating system |
| CN105718355A (en) * | 2016-01-21 | 2016-06-29 | 中国人民解放军国防科学技术大学 | Online learning-based super computer node active fault-tolerant method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109213627A (en) | 2019-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10146627B2 (en) | Mobile flash storage boot partition and/or logical unit shadowing | |
| US10198343B2 (en) | Method for debugging a computer program | |
| US8356149B2 (en) | Memory migration | |
| US9678682B2 (en) | Backup storage of vital debug information | |
| US8127289B2 (en) | Enabling a third party application to participate in migration of a virtualized application instance | |
| JP5593856B2 (en) | Information processing apparatus and driver execution control method | |
| US20050204186A1 (en) | System and method to implement a rollback mechanism for a data storage unit | |
| US8219851B2 (en) | System RAS protection for UMA style memory | |
| CN109710317B (en) | System starting method and device, electronic equipment and storage medium | |
| US9235426B2 (en) | Multicore processor system, computer product, and notification method for updating operating system | |
| JP2007133544A (en) | Failure information analysis method and its implementation device | |
| JP2012190460A (en) | Device for improving fault tolerance of processor | |
| CN104866388B (en) | Data processing method and device | |
| CN113127263B (en) | Kernel crash recovery method, device, equipment and storage medium | |
| CN109213627B (en) | Fault-tolerant operation method and electronic device using same | |
| US10592329B2 (en) | Method and electronic device for continuing executing procedure being aborted from physical address where error occurs | |
| JP2007265137A (en) | Multi-task processing method and multi-task processing apparatus | |
| US11226755B1 (en) | Core dump in a storage device | |
| CN115421960A (en) | UE memory fault recovery method, device, electronic equipment and medium | |
| CN115576766A (en) | Flash memory management algorithm debugging method, system, device and readable storage medium | |
| TWI663544B (en) | Fault tolerant operating metohd and electronic device using the same | |
| CN114443330A (en) | Watchdog restart fault determination method and device, electronic equipment and storage medium | |
| CN111291034A (en) | Block chain plug-in data cleaning method, system, terminal and medium | |
| Lee et al. | Process resurrection: A fast recovery mechanism for real-time embedded systems | |
| US10013299B2 (en) | Handling crashes of a device's peripheral subsystems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |