CN101499041B - Method for preventing abnormal deadlock of main unit during access to shared devices - Google Patents
Method for preventing abnormal deadlock of main unit during access to shared devices Download PDFInfo
- Publication number
- CN101499041B CN101499041B CN2009100586214A CN200910058621A CN101499041B CN 101499041 B CN101499041 B CN 101499041B CN 2009100586214 A CN2009100586214 A CN 2009100586214A CN 200910058621 A CN200910058621 A CN 200910058621A CN 101499041 B CN101499041 B CN 101499041B
- Authority
- CN
- China
- Prior art keywords
- shared device
- task
- priority task
- low priority
- complement mark
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000002159 abnormal effect Effects 0.000 title abstract 2
- 230000000295 complement effect Effects 0.000 claims description 47
- 230000002093 peripheral effect Effects 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 6
- 239000011800 void material Substances 0.000 description 6
- 238000012545 processing Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000007717 exclusion Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 208000019901 Anxiety disease Diseases 0.000 description 1
- 230000036506 anxiety Effects 0.000 description 1
- 238000007796 conventional method Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
Images
Abstract
The invention discloses a method to avoid abnormal deadlock of a host computer in accessing shared device. The host computer sets an access conflict mark for the shared devices. When the low priority task accesses the shared device, and requires whether operation achieving mark of the shared devices is set as 1 in a circular manner, the host computer interrupts a service routine or a high priority task interrupts the lower one and accesses the shared devices, and requires whether operation achieving mark of the shared devices is set as 1, the host computer cleans the mark as 0 and sets the access conflict mark as 1. Along interruption returns or task re-transfer, the low priority task is executed continuously, and detects the operation achieving mark that is 0, the access conflict mark that is 1, the host computer escapes circular requirement (or the task enters deal circle, causing deadlock), re-accesses the shared devices. The technical solution of the invention can avoid the deadlock. Because of simple and reliable method, the invention is in particular applied to the embedded system field with a low-performance processor and inadequate memory resources.
Description
Technical field
The present invention relates to the embedded system technology field, particularly relate to a kind of method of avoiding main frame to cause unusual deadlock at the visit shared device.
Background technology
Flush bonding processor can connect various peripheral hardwares and realize various functions, though peripheral functionality has nothing in common with each other, flush bonding processor has only two kinds usually with the handshake method of peripheral hardware, and a kind of is inquiry mode, and a kind of is interrupt mode.In the system that has used inquiry mode work, may cause deadlock because of various reasons, guarantee that system is not considerable by deadlock so design reliable software.
For deadlock, different fields can provide different definition, is meant mainly that here flush bonding processor can not do other thing at the waiting facilities complete operation always.The necessary condition of deadlock is concluded following several:
1, mutual exclusion condition: a resource can only be used by a process at every turn.
2, request and conservation condition: when a process is blocked because of request resource, acquired resource is kept not putting.
3, do not deprive condition: the acquired resource of process, before the end uses, can not deprive by force.
4, circular wait condition: form a kind of connected head-to-tail circular wait resources relationship between some processes.
In some built-in system software, above-mentioned " process " can be understood as the particular code (being referred to as task in the description of back) of task or certain section access shared resources.Along with the development of software engineering, solving shared resource access conflict problem has had a variety of methods, such as disabled interrupt, utilizes the mutex amount and uses various resource locks or the like.How to use to different tasks the shared resource reasonable distribution but these methods all are intended to solve, guarantee that task can not cause deadlock because of attempting to obtain certain shared resource.
And in embedded system, task also might occur and obtain shared resource and the phenomenon of deadlock.Possible reason is:
1, shared device breaks down, and then operates complement mark and just may not can be set, and corresponding task will be in waiting status always and cause deadlock.
2, when a task when whether inquiry shared device operation complement mark is put 1, take place one and interrupted or produced task scheduling, this interruption or the new task of carrying out that is scheduled also will be visited this shared device by chance, and Interrupt Service Routine or the new task that is scheduled can be removed shared device operation complement mark (this is the equipment necessary condition of operate as normal again) after having visited shared device, rescheduled and cause before inquiring about shared device operation complement mark 1 the task of whether being put and continue to begin to carry out interrupting returning back or task so, go one of cyclic query can not be put 1 shared device operation complement mark again, then this task is just by deadlock.For example, a task need be gathered certain road simulating signal, after having started analog to digital converter, task begins to wait for that the analog to digital conversion complement mark is set, having taken place one this moment interrupts or task scheduling, also to use same analog to digital converter to gather certain road simulating signal in the new task that happens to be in the Interrupt Service Routine or be scheduled, analog to digital converter will be restarted so, behind EOC, convert and indicate that being shared equipment puts 1 automatically, interruption routine or the new task that is scheduled detect this sign and are set this sign of back removing, carry out other operation then, final interruption returns or task can be rescheduled, and the task of making the set of previous wait analog to digital conversion complement mark obtains continuing to carry out, but this moment, analog to digital converter was in idle state, converted sign and also just can not be set, and this task goes down to cause deadlock with Beyond so.This situation is more hidden, is difficult for being taken into account at the beginning of software design.
In sum, the peripheral hardware of embedded system belongs to hardware resource, and hardware breaks down and may cause system deadlock; The peripheral hardware of embedded system is mutual exclusion, and is imprescriptible, and its inherent characteristic has caused the necessary condition of deadlock; Conventional method can only solve the shared resource assignment problem, promptly can only solve the problem before the resources allocation, and the task in the embedded system of can not solving regains the problem that causes deadlock after the shared device control.
Summary of the invention
The invention provides a kind of main frame of avoiding and cause the method for unusual deadlock at the visit shared device, the problem of deadlock takes place in the task that can solve after having obtained the shared device control.
For reaching goal of the invention, the technical solution adopted in the present invention is:
A kind of main frame of avoiding causes the method for unusual deadlock at the visit shared device, is applicable to embedded system, may further comprise the steps:
A, an access conflict sign is set for described shared device;
B, a low priority task start described shared device;
C, described low priority task are inquired about described shared device operation complement mark and whether are put 1, if described shared device operation complement mark is put 1, then go to step D, otherwise go to step e;
D, described low priority task are finished the visit of described shared device, and described shared device operation complement mark is clear 0, and process ends;
E, described low priority task are inquired about described shared device access conflict sign and whether are put 1, if described shared device access conflict sign is put 1, then with its clear 0 and go to step B, retry is visited described shared device, otherwise goes to step C;
F, when described low priority task during in execution in step B, step C or step e, Interrupt Service Routine or high-priority task have interrupted the execution of described low priority task and have visited described shared device, then in described Interrupt Service Routine or high-priority task, start shared device, and go to step G;
G, described Interrupt Service Routine or high-priority task are inquired about described shared device operation complement mark and whether are put 1, if described shared device operation complement mark is put 1, then go to step H, otherwise re-execute step G;
H, described Interrupt Service Routine or high-priority task are clear 0 with described shared device operation complement mark, and shared device access conflict sign puts 1, and interrupt returning or task reschedules, and described low priority task continues execution in step B, step C or step e.
In task of visiting shared device or Interrupt Service Routine, the time-out count value is set, when the number of times of inquiring about described shared device operation complement mark when described task or Interrupt Service Routine surpasses described time-out count value, then withdraw from the inquiry circulation, carry out time-out error and handle.
In the low priority task of visit shared device the number of retries value is set, when the number of times of visiting described shared device when described low priority task surpassed described number of retries value, the collision error that conducts interviews was handled.
Described shared device is to have the peripherals that the hardware flags mirror operation has been finished, and comprises timer, serial ports controller, iic bus controller, spi bus controller, usb bus controller, PWM controller, comparer, analog to digital converter, digital to analog converter in the embedded system.
Described embedded system is the AM/BAM embedded system, or has the embedded system of operating system.
Adopted technical scheme of the present invention, can solve the problem that the visit shared device that causes owing to hardware or software reason causes the task deadlock, the problem of deadlock takes place in the task that also can solve after having obtained the shared device control, and the realization of method is simple, reliable, it is not high to be specially adapted to processor performance, the embedded system field of memory resource anxiety.
Description of drawings
Fig. 1 avoids visiting the process flow diagram that shared device causes deadlock among the present invention.
Fig. 2 is at avoiding visiting the process flow diagram that shared device causes deadlock in the AM/BAM embedded system among the present invention.
Fig. 3 is at avoiding visiting the process flow diagram that shared device causes deadlock in the embedded system with operating system among the present invention.
Embodiment
The present invention is further described below in conjunction with accompanying drawing and embodiment.
Fig. 1 avoids visiting the process flow diagram that shared device causes deadlock among the present invention.As shown in Figure 1, this flow process may further comprise the steps:
If step 108, after low priority task starts shared device, during shared device is finished assigned operation, having Interrupt Service Routine or high-priority task to visit shared device, described low priority task is interrupted, thereby go to step 109, enter in the execution in step of Interrupt Service Routine or high-priority task.
Under the guidance of above-mentioned steps, can draw embodiment at different embedded systems.
Describe below and avoid visiting the embodiment that shared device causes deadlock in a kind of AM/BAM embedded system.In the AM/BAM embedded system, background program all may be interrupted by foreground program at any time, so background program belongs to the code that may lose the shared device control (being the described low priority task of avoiding visiting in the process step that shared device causes deadlock), need detect shared device access conflict sign in inquiry shared device operation complement mark.Foreground program belongs to and has the code of seizing shared device control ability (being the described Interrupt Service Routine of avoiding visiting in the process step that shared device causes deadlock), if system allows interrupt nesting, and there are a plurality of interruptions to share an equipment, so, foreground program also belongs to the code that may lose the shared device control (being the described low priority task of avoiding visiting in the process step that shared device causes deadlock), so foreground program need be after having visited shared device set shared device access conflict sign, and determine whether that according to actual conditions needs detect shared device access conflict sign in inquiry shared device operation complement mark.
This embodiment is considered a kind of situation widely, in the AM/BAM embedded system, there are a background program and two foreground programs (foreground program 1 and foreground program 2) to share an equipment, this system allows interrupt nesting, and the interrupt priority level of foreground program 2 is higher than the interrupt priority level of foreground program 1.
Background program in the above-mentioned AM/BAM embedded system belongs to the code that may lose the shared device control, foreground program 1 had not only belonged to the code that may lose the shared device control but also had belonged to and had the code of seizing shared device control ability, and foreground program 2 belongs to and has the code of seizing shared device control ability.Provide the C language reference code of each program below respectively.
The background program identifying code:
#define?MaxLoopCycles?1000
#define?MaxRetryCycles?2
Unsigned char LootFlag; // 1. define shared device access conflict sign, be a global variable
void?BackgroundXxx(void)
{
unsigned?int?loop_count＝MaxLoopCycles；
unsigned?char?retry_count＝MaxRetryCycles；
while(retry_count)
{
StartDevice (); // 2. starting outfit, retry operation is also wanted restart facility
while(DCFlag＝＝0&&LootFlag＝＝0&&loop_count！＝0)//③
During query facility operation complement mark DCFlag
The test access of { // simultaneously collision flag LootFlag and
Loop_count--; // time-out count value loop_count
}
=0) // 4. the operation of equipment complement mark is by normal set
{
DCFlag=0; // then will operate the complement mark zero clearing
LootFlag=0; // with the zero clearing of access conflict sign
Break; // and withdraw from the retry circulation
}
=0) if // 5. access conflict taken place, promptly in the wait process by before
The platform program interrupts
{
LootFlag=0; // then with access flag clear 0
Retry_count--; // number of retries subtracts 1
Continue; // and carry out retry
}
If (loop_count==0) if // 6. visit overtime
{
Break; // then carry out time-out error to handle and withdraw from the retry circulation
}
}
If (retry_count==0) if // 7. in the number of retries of regulation, device access is not still
Corresponding fault processing is then carried out in success
{
}
}
The identifying code of foreground program 1:
void?ISR1Xxx(void)
{
unsigned?int?loop_count＝MaxLoopCycles；
unsigned?char?retry_count＝MaxRetryCycles；
while(retry_count)
{
StartDevice (); // 2. starting outfit, retry operation is also wanted restart facility
while(DCFlag＝＝0&&LootFlag＝＝0&&loop_count！＝0)//③
During query facility operation complement mark DCFlag
The test access of { // simultaneously sign LootFlag and
Loop_count--; // time-out count value loop_count
}
=0) // 4. the operation of equipment complement mark is by normal set
{
DCFlag=0; // then will indicate zero clearing
LootFlag=1; // 8. different with background program is, behind the normal complete operation of equipment
Need be the access conflict flag set
Break; // and withdraw from the retry circulation
}
=0) if // 5. access conflict taken place, promptly in the wait process by before
The platform program interrupts
{
LootFlag=0; // then with access flag clear 0
Retry_count--; // number of retries subtracts 1
Continue; // and carry out retry
}
If (loop_count==0) if // 6. visit overtime
{
Break; // then carry out time-out error to handle and withdraw from the retry circulation
}
}
If (retry_count==0) if // 7. in the number of retries of regulation, device access is not still
Corresponding fault processing is then carried out in success
{
}
}
The identifying code of foreground program 2:
void?ISR2Xxx(void)
{
unsigned?int?loop_count＝MaxLoopCycles；
StartDevice (); // 1. starting outfit
While (DCFlag==0﹠amp; ﹠amp;=0) // 2. query facility is operated complement mark
During DCFlag
{ // simultaneously detects time-out count value loop_count
loop_count--；
}
If (loop_count==0) if // 3. visit overtimely, then carry out time-out error and handle and withdraw from heavily
The examination circulation
{
}
DCFlag=0; // 4. the operation of equipment complement mark puts 0
LootFlag=1; // 5. access flag puts 1
}
Even this embodiment can avoid issuing at extreme case the phenomenon of life and death lock.Fig. 2 is that the specific embodiment of the invention one avoids visiting the process flow diagram that shared device causes deadlock in the AM/BAM embedded system.As shown in Figure 2, at t
0Constantly, whether background program inquiry shared device operation complement mark DCFlag after starting shared device is put 1, shared device access conflict sign LootFlag whether put 1 and time-out count value loop_count interruption has taken place when whether being 0 (3. the background program note is located), this interruption is the interruption of foreground program 1, then foreground program 1 begins to carry out, shared device operation this moment complement mark DCFlag is not also put 1, and shared device access conflict sign LootFlag also is 0.At t
1Constantly, whether inquiry shared device operation complement mark DCFlag was put 1 after foreground program 1 started shared device, shared device access conflict sign LootFlag whether put 1 and time-out count value loop_count interruption has taken place again when whether being 0 (3. foreground program 1 note is located), system allows interrupt nesting, and this interruption is the interruption of foreground program 2, then foreground program 2 will begin to carry out, shared device operation this moment complement mark DCFlag is not yet put 1, and shared device access conflict sign LootFlag still is 0.Foreground program 2 starts shared device and carries out smoothly afterwards, successfully inquire operation of equipment complement mark DCFlag put 1 after with its clear 0 (4. foreground program 2 notes is located), and shared device access conflict sign LootFlag put 1 (5. foreground program 2 notes are located), then at t
2Constantly turn back to foreground program 1 interrupted place (3. foreground program 1 note is located), if shared device access conflict this moment sign LootFlag is not put 1, so since shared device operation complement mark DCFlag in foreground program 2 the insides by clear 0, foreground program 1 will detect shared device operation complement mark DCFlag never and be put 1, thereby cause deadlock.But put 1 owing to used method of the present invention, foreground program 1 to detect shared device access conflict sign LootFlag, foreground program 1 will withdraw from the inquiry circulation so, and carry out retry operation.Suppose in retry operation, not interrupted by foreground program 2, foreground program 1 will be carried out smoothly so, after being finished, shared device operated clear 0 (4. foreground program 1 note is located) of complement mark DCFlag, and shared device access conflict sign LootFlag put 1 (8. foreground program 1 note is located), then at t
3Constantly be back to background program.Same, if background program does not detect shared device access conflict sign LootFlag, will cause deadlock.But put 1 owing to used method of the present invention, background program to detect shared device access conflict sign LootFlag, background program will withdraw from the inquiry circulation so, and carry out retry operation.Suppose in the background program retry operation, not interrupt, background program will be carried out smoothly so, successfully inquire shared device operation complement mark DCFlag put 1 after with its clear 0, and with shared device access conflict sign clear 0, and then carry out other operation, so just avoided the generation of deadlock.
Of particular note, the time-out count value will be set as the case may be, and assurance equipment is under the situation of normal complete operation, and the time-out count value can not reduce to 0.In addition, because shared device access conflict sign LootFlag is a global variable, belong to the software shared resource, if system can not guarantee can be finished in an instruction to the visit of this sign, need to use extra method to visit this global variable so, such as methods such as use mutex amounts.
The embodiment that solves the deadlock problem in a kind of embedded system with operating system is described below.In the embedded system of operating system is arranged, the task that task may newly be dispatched interrupts, so task had not only belonged to the code that may lose the shared device control (being the described low priority task of avoiding visiting in the process step that shared device causes deadlock) but also had belonged to and have the code of seizing shared device control ability (being the described high-priority task of avoiding visiting in the process step that shared device causes deadlock), whether put 1 o'clock at task inquiry shared device operation complement mark, need to detect shared device access conflict sign, and after task has been visited shared device, need shared device access conflict sign is put 1.
In the embedded system of operating system is arranged, (Interrupt Service Routine herein is the Interrupt Service Routine in the particular system to Interrupt Service Routine, distinguish to some extent with the described Interrupt Service Routine of avoiding visiting in the process step that shared device causes deadlock) with the foreground program in the AM/BAM embedded system, need after having visited shared device, shared device access conflict sign be put 1, and according to whether having nested interruption visit shared device to determine whether needs detect shared device access conflict sign when whether inquiry shared device operation complement mark is put 1.
This embodiment is considered a kind of situation widely, in the embedded system of operating system is arranged, two same Interrupt Service Routines of task are shared an equipment, and Fig. 3 is that the specific embodiment of the invention two avoids visiting the process flow diagram that shared device causes deadlock in the embedded system of operating system is arranged.As shown in Figure 3, task 1 and task 2 had not only belonged to the code that may lose the shared device control but also had belonged to and had the code of seizing shared device control ability, and Interrupt Service Routine belongs to and has the code of seizing shared device control ability.Task 1 is just identical with the form of above-mentioned foreground program 1 with task 2 so, and Interrupt Service Routine is just identical with the form of above-mentioned foreground program 2.Just no longer provided code sample herein.When access conflict takes place, its treatment scheme is similar substantially with above-mentioned treatment scheme, unique different be after Interrupt Service Routine is finished, task 1 may be carried out prior to task 2, this moment is because shared device access conflict sign LootFlag is put 1, so task 1 can deadlock, task 2 also can be put 1 and can deadlock because of shared device access conflict sign LootFlag afterwards.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (5)
1. avoid main frame to cause the method for unusual deadlock for one kind, be applicable to embedded system, it is characterized in that, may further comprise the steps at the visit shared device:
A, an access conflict sign is set for described shared device;
B, a low priority task start described shared device;
C, described low priority task are inquired about described shared device operation complement mark and whether are put 1, if described shared device operation complement mark is put 1, then go to step D, otherwise go to step e;
D, described low priority task are finished the visit of described shared device, and described shared device operation complement mark is clear 0, and process ends;
E, described low priority task are inquired about described shared device access conflict sign and whether are put 1, if described shared device access conflict sign is put 1, then with its clear 0 and go to step B, retry is visited described shared device, otherwise goes to step C;
F, when described low priority task during in execution in step B, step C or step e, Interrupt Service Routine or high-priority task have interrupted the execution of described low priority task and have visited described shared device, then in described Interrupt Service Routine or high-priority task, start shared device, and go to step G;
G, described Interrupt Service Routine or high-priority task are inquired about described shared device operation complement mark and whether are put 1, if described shared device operation complement mark is put 1, then go to step H, otherwise re-execute step G;
H, described Interrupt Service Routine or high-priority task are clear 0 with described shared device operation complement mark, and shared device access conflict sign puts 1, and interrupt returning or task reschedules, and described low priority task continues execution in step B, step C or step e.
2. method according to claim 1, it is characterized in that, in task of visiting shared device or Interrupt Service Routine, the time-out count value is set, when the number of times of inquiring about described shared device operation complement mark when described task or Interrupt Service Routine surpasses described time-out count value, then withdraw from the inquiry circulation, carry out time-out error and handle.
3. method according to claim 1, it is characterized in that, in the low priority task of visit shared device the number of retries value is set, when the number of times of visiting described shared device when described low priority task surpassed described number of retries value, the collision error that conducts interviews was handled.
4. according to the described method of each claim in the claim 1 to 3, it is characterized in that, described shared device is to have the peripherals that the hardware flags mirror operation has been finished, and comprises timer, serial ports controller, iic bus controller, spi bus controller, usb bus controller, PWM controller, comparer, analog to digital converter, digital to analog converter in the embedded system.
5. according to the described method of each claim in the claim 1 to 3, it is characterized in that described embedded system is the AM/BAM embedded system, or have the embedded system of operating system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100586214A CN101499041B (en) | 2009-03-17 | 2009-03-17 | Method for preventing abnormal deadlock of main unit during access to shared devices |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009100586214A CN101499041B (en) | 2009-03-17 | 2009-03-17 | Method for preventing abnormal deadlock of main unit during access to shared devices |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101499041A CN101499041A (en) | 2009-08-05 |
| CN101499041B true CN101499041B (en) | 2010-07-28 |
Family
ID=40946122
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009100586214A Expired - Fee Related CN101499041B (en) | 2009-03-17 | 2009-03-17 | Method for preventing abnormal deadlock of main unit during access to shared devices |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101499041B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2012073851A (en) * | 2010-09-29 | 2012-04-12 | Sony Corp | Bus system and deadlock avoidance circuit thereof |
| CN102063361A (en) * | 2010-12-28 | 2011-05-18 | 四川长虹电器股份有限公司 | Method for reducing probability of dead halt of embedded software |
| CN102170548A (en) * | 2011-01-28 | 2011-08-31 | 杭州海康威视数字技术股份有限公司 | Mutually exclusive resource remote-access method and digital video recorder |
| CN102226942B (en) * | 2011-06-01 | 2013-04-03 | 北京凡达讯科技有限公司 | Electronic ink controller bridging SDRAM |
| CN102970202B (en) * | 2012-11-26 | 2015-02-18 | 北京空间飞行器总体设计部 | 1553B bus communication method based on preemptive strategy |
| JP6295990B2 (en) * | 2015-03-31 | 2018-03-20 | 京セラドキュメントソリューションズ株式会社 | Electronic equipment and information processing program |
| CN106020980A (en) * | 2015-05-21 | 2016-10-12 | 中国科学院计算技术研究所 | Virtual desktop oriented VCPU (Virtual Central Processing Unit) scheduling method |
| CN106097600B (en) * | 2016-05-30 | 2019-01-25 | 广州广电运通金融电子股份有限公司 | Device management method, system and financial self-service equipment based on ATL |
| US20170351447A1 (en) * | 2016-06-03 | 2017-12-07 | Scale Computing, Inc. | Data protection implementation for block storage devices |
| CN106341399A (en) * | 2016-08-29 | 2017-01-18 | 锐捷网络股份有限公司 | User access control method and system |
| CN109086142B (en) * | 2018-09-25 | 2022-03-25 | 郑州云海信息技术有限公司 | Resource scheduling method and device based on Openlava |
| CN112069105B (en) * | 2020-07-31 | 2022-09-23 | 深圳市优必选科技股份有限公司 | Serial port communication processing method and device and electronic equipment |
| CN114385621A (en) * | 2020-10-21 | 2022-04-22 | 北京达佳互联信息技术有限公司 | Locking method, device, equipment and medium |
-
2009
- 2009-03-17 CN CN2009100586214A patent/CN101499041B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN101499041A (en) | 2009-08-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101499041B (en) | Method for preventing abnormal deadlock of main unit during access to shared devices | |
| CN103294533B (en) | task flow control method and system | |
| TWI233545B (en) | Mechanism for processor power state aware distribution of lowest priority interrupts | |
| CN101529383B (en) | Task processing device | |
| US7406699B2 (en) | Enhanced runtime hosting | |
| US20120260257A1 (en) | Scheduling threads in multiprocessor computer | |
| CN1983193A (en) | System and method for processing information | |
| RU2009118454A (en) | SOFTWARE TRANSACTION FIXING PROCEDURE AND CONFLICT MANAGEMENT | |
| US20090024985A1 (en) | Task control method and semiconductor integrated circuit | |
| US9086911B2 (en) | Multiprocessing transaction recovery manager | |
| CN106155803B (en) | A kind of thread pool sharing method and system based on semaphore | |
| CN113010275A (en) | Interrupt processing method and device | |
| CN112882828B (en) | Method for managing and scheduling a processor in a processor-based SLURM operation scheduling system | |
| US20060015876A1 (en) | Light weight context switching technique | |
| US20160179484A1 (en) | Code Generating Method, Compiler, Scheduling Method, Scheduling Apparatus and Scheduling System | |
| US20020099893A1 (en) | System and method for the handling of system management interrupts in a multiprocessor computer system | |
| US20080104602A1 (en) | Task switching control method and computer system | |
| JP2007108944A (en) | Semiconductor integrated circuit device | |
| US20090158294A1 (en) | Dynamic critical-path recalculation facility | |
| CN112463342A (en) | Platform architecture design method for multi-core CPU operation mode | |
| CN102436393A (en) | Task treatment device | |
| KR101770234B1 (en) | Method and system for assigning a computational block of a software program to cores of a multi-processor system | |
| EP4099161A1 (en) | Multi-core processor, multi-core processor processing method and related device | |
| CN115794355B (en) | Task processing method, device, terminal equipment and storage medium | |
| JP2020160482A (en) | Performance estimation device, terminal device, system LSI and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee |
Owner name: SICHUAN SUPERXON INFORMATION TECHNOLOGY CO., LTD. Free format text: FORMER NAME: SUPERXON TECHNOLOGY (CHENGDU) CO., LTD. |
|
| CP03 | Change of name, title or address |
Address after: 7, No. 216, No. 610000 South City Road, Chengdu hi tech Zone, Sichuan, 101, 201 Patentee after: SICHUAN SUPERXON INFORMATION TECHNOLOGY Co.,Ltd. Address before: 610041 B, building E9, 1 hi tech incubator Park, Tianfu Road, hi tech Zone, Sichuan, Chengdu Patentee before: Superxon (Chengdu) Technology Ltd. |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| C56 | Change in the name or address of the patentee | ||
| CP03 | Change of name, title or address |
Address after: 610041 D, 7, Tianfu Software Park, 599 century South Road, Chengdu hi tech Zone, Sichuan, 201 Patentee after: Nine letter asset management Limited by Share Ltd. Address before: 7, No. 216, No. 610000 South City Road, Chengdu hi tech Zone, Sichuan, 101, 201 Patentee before: SICHUAN SUPERXON INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20160616 Address after: 610041, 0, Tianfu District, Tianfu Road, 599 century South Road, Chengdu hi tech Zone, Sichuan, 7, 201 Patentee after: CHENGDU SUPERXON INFORMATION TECHNOLOGY Co.,Ltd. Address before: 610041 D, 7, Tianfu Software Park, 599 century South Road, Chengdu hi tech Zone, Sichuan, 201 Patentee before: Nine letter asset management Limited by Share Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100728 Termination date: 20180317 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |