CN103150208B - A kind of BIOS operation method and BIOS chip supporting multitask - Google Patents
A kind of BIOS operation method and BIOS chip supporting multitask Download PDFInfo
- Publication number
- CN103150208B CN103150208B CN201310095193.9A CN201310095193A CN103150208B CN 103150208 B CN103150208 B CN 103150208B CN 201310095193 A CN201310095193 A CN 201310095193A CN 103150208 B CN103150208 B CN 103150208B
- Authority
- CN
- China
- Prior art keywords
- task
- core cpu
- peidriver
- bios
- dxedriver
- 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
Landscapes
- Stored Programmes (AREA)
Abstract
The embodiment of the present invention provides a kind of BIOS operation method and the BIOS chip of supporting multitask, and wherein method comprises: in BIOS operational process, determines the scheduler that the current BIOS operation phase is corresponding; Described scheduler is used to transfer the driving Driver calling program corresponding with the current BIOS operation phase; Using described Driver calling program, putting into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.The embodiment of the present invention achieves the support of the multitask running under BIOS environment.
Description
Technical field
The present invention relates to computer communication technology field, more particularly, relate to a kind of BIOS(BasicInputOutputSystem supporting multitask, Basic Input or Output System (BIOS)) operation method and BIOS chip.
Background technology
BIOS is one group and is cured in computing machine a ROM(Read-OnlyMemory on mainboard, read-only memory) program on chip, self-check program and system self-triggered program after the program of the most important basic input and output of its in store computing machine, system set-up information, start; Its major function provides the bottom, the most direct hardware setting and control for computing machine.Under normal circumstances, BIOS runs when computer booting, when computer booting, BIOS will carry out the self-inspection of computing machine, and after self-inspection completes, BIOS calls in starting up's program, by starting up's program, the control of computing machine is transferred to the operating system of computing machine.
At present, the operational process of BIOS is mainly divided into four-stage: SEC(Security, the clean boot stage), PEI(PreEFIInitializationEnvironment, early stage EFI initial phase), DXE(DriverExecutionEnvironment, drives the execute phase) and RT(RunTimeOS, the operation phase).Inventor is realizing finding in process of the present invention: existing BIOS can only operate in BSP(boardsupportedpackage, plate support package) on, namely above-mentioned SEC, PEI, this four-stage of DXE and RT all can only run on BSP, this makes, and no matter computer system has how many CPU, all cannot support the operation of multitask under BIOS environment, the task treatment effeciency in BIOS operational process is reduced greatly.
Summary of the invention
In view of this, the embodiment of the present invention provides a kind of BIOS operation method and the BIOS chip of supporting multitask, can only operate on BSP to solve existing BIOS, and causes to support the problem of multitask running under BIOS environment.
For achieving the above object, the embodiment of the present invention provides following technical scheme:
Support a BIOS operation method for multitask, comprising:
In BIOS operational process, determine the scheduler that the current BIOS operation phase is corresponding;
Described scheduler is used to transfer the driving Driver calling program corresponding with the current BIOS operation phase;
Using described Driver calling program, putting into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
The embodiment of the present invention also provides a kind of BIOS chip, comprising: scheduler determination module, the routine call module be connected with described scheduler determination module, the task allocating module be connected with described routine call module;
Described scheduler determination module, in BIOS operational process, determines the scheduler that the current BIOS operation phase is corresponding;
Described routine call module, for using the determined scheduler of described scheduler determination module, transfers the driving Driver calling program corresponding with the current BIOS operation phase;
Described task allocating module, for using described Driver calling program, puts into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, and multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
Based on technique scheme, the BIOS operation method of the support multitask that the embodiment of the present invention provides, in the different BIOS operation phase, the scheduler corresponding with this BIOS operation phase is set, described scheduler is used to transfer the Driver calling program corresponding with the current BIOS operation phase, the Driver played by Driver calling program and the reciprocation of multi-core CPU, described Driver calling program is used to put into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase, the embodiment of the present invention achieves the object running BIOS on multi-core CPU, solve existing BIOS can only operate on BSP, and cause to support the problem of multitask running under BIOS environment, achieve the support of the multitask running under BIOS environment, improve the task treatment effeciency in BIOS operational process.
Accompanying drawing explanation
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
The process flow diagram of the BIOS operation method of the support multitask that Fig. 1 provides for the embodiment of the present invention;
The schematic diagram running multiple Drive on multiple core cpu that Fig. 2 provides for the embodiment of the present invention;
A kind of another process flow diagram supporting the BIOS operation method of multitask that Fig. 3 provides for the embodiment of the present invention;
The another process flow diagram of the BIOS operation method of the support multitask that Fig. 4 provides for the embodiment of the present invention;
A kind of process flow diagram again supporting the BIOS operation method of multitask that Fig. 5 provides for the embodiment of the present invention;
The another again process flow diagram of the BIOS operation method of the support multitask that Fig. 6 provides for the embodiment of the present invention;
What Fig. 7 provided for the embodiment of the present invention carries out the initialized schematic diagram of multi-core CPU;
The structured flowchart of the BIOS chip that Fig. 8 provides for the embodiment of the present invention;
Another structured flowchart of the BIOS chip that Fig. 9 provides for the embodiment of the present invention;
The structured flowchart of the first task allocation units that Figure 10 provides for the embodiment of the present invention;
The another structured flowchart of the BIOS chip that Figure 11 provides for the embodiment of the present invention;
A structured flowchart again of the BIOS chip that Figure 12 provides for the embodiment of the present invention;
The structured flowchart of the second task allocation unit that Figure 13 provides for the embodiment of the present invention;
The another again structured flowchart of the BIOS chip that Figure 14 provides for the embodiment of the present invention;
Another structured flowchart again of the BIOS chip that Figure 15 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtained under creative work prerequisite, belong to the scope of protection of the invention.
The process flow diagram of the BIOS operation method of the support multitask that Fig. 1 provides for the embodiment of the present invention, with reference to Fig. 1, the method can comprise:
Step S100, in BIOS operational process, determine the scheduler that the current BIOS operation phase is corresponding;
Can all arrange corresponding scheduler in each BIOS operation phase in the embodiment of the present invention, as arranged corresponding scheduler in the PEI stage, the DXE stage arranges corresponding scheduler etc.; Described scheduler drives for transferring the Driver(corresponding with the current BIOS operation phase) calling program.
Step S110, described scheduler is used to transfer the Driver calling program corresponding with the current BIOS operation phase;
In the embodiment of the present invention, Driver calling program is the mutual bridge of the Driver that multi-core CPU is corresponding with the current BIOS operation phase, plays the effect of Driver being put into multi-core CPU; Driver calling program can be a calling interface between Driver and multi-core CPU, also can be an invocation protocol, the Driver that the visual different BIOS operation phase is set of concrete Driver calling program, with the interactive mode of multi-core CPU and changing, unfixing restriction.
Step S120, using described Driver calling program, putting into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
Meeting pre-conditioned Driver can be whole Driver corresponding to current BIOS operation phase, also can be the Driver needing to put into multi-core CPU pre-set.
Optionally, the embodiment of the present invention can arrange BIOSPostTaskTable(BIOS and notify task list), notify to arrange the Driver information that each BIOS operation phase needs to put into multi-core CPU in task list at BIOS, as notified to arrange the Driver information that the PEI stage needs to put into multi-core CPU in task list at BIOS, notify to arrange the Driver information etc. that the DXE stage needs to put into multi-core CPU in task list at BIOS.Optionally, BIOS in the embodiment of the present invention notifies that task list can be static Driver allocation strategy, BIOS notifies that task list can just start to call at the beginning of BIOS runs, in BIOS operational process, BIOS notifies that the information arranged in task list can not change, only in the non-BIOS operation phase, the information updating in BIOS notice task list just can be carried out; Optionally, the BIOS in the embodiment of the present invention notifies that task list also can be dynamic Driver allocation strategy, can to needing the Driver putting into multi-core CPU to adjust in BIOS operational process.
Obviously, other Driver allocation rule also can be set, multi-core CPU is put into by meeting pre-conditioned Driver, as the Driver of quantity of information comparatively large (as quantity of information reaches certain threshold value) is put into multi-core CPU, Driver less for quantity of information is processed according to prior art, the concrete visual practical situations of Driver allocation rule is arranged, and the embodiment of the present invention does not fix restriction.
Multi-core CPU has multiple core, the mode that the embodiment of the present invention preferably runs multiple Drive on multiple core cpu can be: a core cpu synchronization only allows operation Drive, allow multiple core cpu to run multiple Drive simultaneously, can refer to the schematic diagram running multiple Drive on multiple core cpu shown in Fig. 2, synchronization can run multiple Driver on multiple core cpu simultaneously, and one of them AP represents a core cpu.
The BIOS operation method of the support multitask that the embodiment of the present invention provides, in the different BIOS operation phase, the scheduler corresponding with this BIOS operation phase is set, described scheduler is used to transfer the Driver calling program corresponding with the current BIOS operation phase, the Driver played by Driver calling program and the reciprocation of multi-core CPU, use described Driver calling program to put into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase; The embodiment of the present invention achieves the object running BIOS on multi-core CPU, solve existing BIOS can only operate on BSP, and cause to support the problem of multitask running under BIOS environment, achieve the support of the multitask running under BIOS environment, improve the task treatment effeciency in BIOS operational process.
Already described above, the operational process of BIOS is mainly divided into four-stage: SEC, PEI, DXE and RT.Obviously, the embodiment of the present invention can only stage wherein carries out method shown in Fig. 1, realizes the multitask support in this stage; Also can all carry out method shown in Fig. 1 at whole four-stages, realize the multitask support in full stage in BIOS operational process.Namely according to the service condition of reality, the embodiment of the present invention can arrange SEC, and at least one stage in PEI, DXE and RT carries out method shown in Fig. 1, realizes the multitask support in this stage.Due in BIOS operational process, the task quantity in PEI and DXE stage is more, and comparatively complicated, therefore hereafter specifically describes the BIOS operational process that PEI and the DXE stage carries out emphatically.It should be noted that by following description, those skilled in the art can know the BIOS operational process that SEC and the RT stage is corresponding, and therefore the present invention does not remake for the BIOS operational process of the correspondence in SEC and RT stage and repeats.
Optionally, the embodiment of the present invention can carry out multitask support in the PEI stage.A kind of another process flow diagram supporting the BIOS operation method of multitask that Fig. 3 provides for the embodiment of the present invention, with reference to Fig. 3, the method can comprise:
Step S200, PEI stage at BIOS operational process, determine the PEIDispatcher(scheduler that the PEI stage is corresponding);
Step S210, described PEIDispatcher is used to transfer PEIDriver calling interface (PPI);
In the embodiment of the present invention, PPI represents PEIM(Pre-EFIInitializationModule, early stage EFI initialization module)-to-PEIMInterface (PPI), be the calling interface of PEIdriver, call for other PEIDriver.PPI is the mutual bridge between PEIdrive and multi-core CPU, for being called in multi-core CPU by PEIDriver.
Step S220, use described PPI to put into multi-core CPU by meeting pre-conditioned PPIDriver in the PEI stage, multiple core cpu runs multiple PEIDriver.
Optionally, the embodiment of the present invention can arrange PEI service list, for recording the information of PEIDriver to be run, different PEIDriver to be run can PEIDriverGuid(mark) distinguish, PEI service list can record different PEIDriverGuid.
When performing step S220, the Guid waiting to run PEIDriver is obtained by PEI service list, thus corresponding the waiting to run in PEIDriver and meet pre-conditioned PEIDriver(task list is determined to meet pre-conditioned PEIDriver such as adopted BIOS to notify of obtained Guid can be judged, optionally, the Guid information that the PEIDriver needing to put into multi-core CPU is set in task list can be notified at BIOS, thus by the Guid information in PEI service list and BIOS notify Guid information in task list to response, determine to meet pre-conditioned PEIDriver), multi-core CPU is put into by meeting pre-conditioned PEIDriver, multiple core cpu runs and meets pre-conditioned PEIDriver.Optionally, in order to PEIDriver to be run and the PEIDriver run are distinguished, can be the PEIDriver allocating task ID(identify label run on multi-core CPU), the differentiation of PEIDriver to be run and the PEIDriver to have run is carried out by the difference of ID and Guid.Optionally, for after the PEIDriver allocating task ID that run, task ID can be back in PEI service list, by PEI service list, record be carried out to task ID.So far, the Guid waiting to run PEIDriver can be recorded in PEI service list simultaneously, and run the task ID of PEIDriver.
Optionally, when returning task ID to PEI service list, also can return the running status of PEIDriver corresponding to task ID on multi-core CPU to PEI service list, the corresponding relation of logger task ID and the running status of corresponding PEIDriver in PEI service list.It should be noted that the time returning task run state there is no particular/special requirement, it together can return with task ID, also can be later than the time of return of task ID.
After PEIDriver is put into multi-core CPU, the embodiment of the present invention also can realize checking of task status and to operate with the control of task run state adjustment, Fig. 4 shows the another process flow diagram of the BIOS operation method of the support multitask that the embodiment of the present invention provides, this process flow operation is after PEIDriver puts into multi-core CPU, and this flow process can comprise:
Step S221, return task ID to PEI service list, and the running status of PEIDriver corresponding to task ID;
Step S222, obtained the task ID of PEIDriver run by PEI service list, obtain the running status of the PEIDriver specifying task ID corresponding in described task ID;
The running status of the PEIDriver that appointed task ID is corresponding can be checked by step S222, make user grasp the operation conditions in PEI stage in real time.
Step S223, the running status of the PEIDriver specifying task ID corresponding in described task ID to be controlled, adjust the running status of PEIDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after PEIDriver adjustment corresponding to described appointed task ID to described PEI service list;
Control adjustment can being carried out to the running status of PEIDriver corresponding to appointed task ID by S223, as adjusted the running status of PEIDriver for running, stopping, dormancy etc.Optionally, the task ID of the PEIDriver run is obtained by PEI service list, thus carry out the determination that PEIDriver corresponding to appointed task ID adjusts state, after running status after determining PEIDriver adjustment corresponding to appointed task ID, the running status adjustment instruction of PEIDriver corresponding to appointed task ID can be sent to multi-core CPU, the core cpu that this PEIDriver runs carries out the adjustment of running status, after adjustment completes, the running status after PEIDriver adjustment corresponding to appointed task ID is returned to PEI service list, to show that the running status adjustment process of PEIDriver completes smoothly.
Step S224, obtained the task list of the PEIDriver of current operation by described PEI service list, cushion described task list in the buffer zone of specifying.
Described task list comprises the task ID of the PEIDriver be placed on multi-core CPU and the task run state of correspondence.Already described above, the PEI service list of the embodiment of the present invention can arrange the Guid information waiting to run PEIDriver, the task ID of the PEIDriver run also can be set, and the running status of the PEIDriver of correspondence (running status of the PEIDriver after adjustment can be comprised); In order to the task run situation making user better know PEIDriver, the same task list isolating the PEIDriver of current operation from PEI service list, the task ID of the PEIDriver on multi-core CPU and the task run state of correspondence is placed on by this task list record, and cushion this task list in the buffer zone of specifying, calling at any time with standby user.
It should be noted that step S222, step S223, step S224 is different treatment scheme, there is not the sequencing relation of step between three.Obviously, the embodiment of the present invention also can an administration step S222, step S223, and at least one step in step S224, is specifically determined by actual service condition.
In the embodiment of the present invention, PPI is the mutual bridge between PEIDriver and multi-core CPU, therefore PPI can be expressed as EFI(ExtensibleFirmwareInterface, Extensible Firmware Interface) _ PEI_MP(MultiCoreProcessor polycaryon processor) PPI, hereafter also show some optimum configurations of PPI, can with combine about the description of PEI stage BIOS operational process above; It should be noted that the visual concrete service condition of some parameters hereafter illustrated does necessary deleting.
EFI_PEI_MP_PPI
Describe: 1, multitask service is provided, PEIdriver is run on different CPU core; 2, control multitask, whole task run state of withering, for running, stops, dormancy; 3, current operation multitask list is returned.
Multi-task state defines:
Parameter:
RunDriver: run PEIdriver, it is put on multi-core CPU, multitask running service is provided; Refer to hereafter PeiRunDriver () API to describe.
GetState: obtain appointed task state; Refer to hereafter PeiGetState () API to describe.
SetState: setting task run state, refers to hereafter PeiSetState () API and describe.
GetTaskList: return current operation multitask list, refers to hereafter PeiGetTaskList () API and describes.
EFI_PEI_MP_PPI.PeiRunDriver()
Describe: run PEIdriver, it is put on multi-core CPU, multitask running service is provided.
Prototype:
Suction parameter: PeiServices, points to PEI service list; PeiDriverGuid, treats operation task GUID; TaskId, returns appointed task ID.
Outlet parameter: state value.
EFI_PEI_MP_PPI.PeiGetState()
Describe: obtain appointed task state.
Prototype
Suction parameter: PeiServices, points to PEI service list; TaskId, appointed task ID; TaskState, task status.
Outlet parameter: state value.
EFI_PEI_MP_PPI.PeiSetState()
Describe: setting task run state.
Prototype:
Suction parameter: PeiServices, points to PEI service list; TaskId, appointed task ID; TaskState, appointed task state.
Outlet parameter: state value.
EFI_PEI_MP_PPI.PeiGetTaskList()
Describe: return current operation multitask list.
Suction parameter: PeiServices, points to PEI service list; TaskListBuffer, buffer zone, for placing current whole operation task list; TaskListBufferSize, buffer size.
Outlet parameter: state value.
Optionally, the embodiment of the present invention can carry out multitask support in the DXE stage.A kind of process flow diagram again supporting the BIOS operation method of multitask that Fig. 5 provides for the embodiment of the present invention, with reference to Fig. 5, the method can comprise:
Step S300, DXE stage at BIOS operational process, determine the PEIDispatcher that the DXE stage is corresponding;
Step S310, described DXEDispatcher is used to transfer DXEDriver invocation protocol (Protocol);
In the embodiment of the present invention, Protocol is the mutual bridge between DXEdrive and multi-core CPU, for being called in multi-core CPU by DXEDriver.
Step S320, use described Protocol that the DXEDriver that the DXE stage meets default bar is put into multi-core CPU.
Optionally, the concrete executive mode of step S320 can be: obtain the Guid waiting to run DXEDriver, corresponding for described Guid is treated that meeting pre-conditioned DXEDriver in operation DXEDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned DXEDrive.Optionally, also can arrange the PEI service list similar with the PEI stage in the DXE stage, as DXE service list, for recording the information of DXEDriver to be run, employing DXEDriverGuid carries out the differentiation between DXEDriver.Obviously, for the DXE stage, also DXE service list can not be set, only a storage space need be used to carry out the record of Guid information.Optionally, multiple core cpu runs after meeting pre-conditioned DXEDrive, can be the DXEDriver allocating task ID run, and return distributed task ID; Optionally, task ID can be returned to DXE service list.
Optionally, when returning task ID, also can return the running status of DXEDriver corresponding to task ID on multi-core CPU, optionally, this task run state can be returned to DXE service list.
After DXEDriver is put into multi-core CPU, the embodiment of the present invention also can realize checking of task status and to operate with the control of task run state adjustment, Fig. 6 shows the another again process flow diagram of the BIOS operation method of the support multitask that the embodiment of the present invention provides, this process flow operation is after DXEDriver puts into multi-core CPU, and this flow process can comprise:
Step S321, return task ID, and the running status of DXEDriver corresponding to task ID;
The running status of the DXEDriver specifying task ID corresponding in step S322, acquisition task ID;
Optionally, the running status of DXEDriver corresponding to appointed task ID is obtained by DXE service list, obviously, when not arranging DXE service list, also can to DXEDriver place core cpu corresponding to appointed task ID, ask the task run state of this DXEDriver, thus obtain the running status of DXEDriver corresponding to appointed task ID.
Step S323, the running status of the DXEDriver specifying task ID corresponding in described task ID to be controlled, adjust the running status of DXEDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after DXEDriver adjustment corresponding to described appointed task ID;
The running status of the DXEDriver that adjustable appointed task ID is corresponding, for running, stops, dormancy etc.Concrete, after running status after determining the DXEDriver adjustment that appointed task ID is corresponding, the running status adjustment instruction of DXEDriver corresponding to appointed task ID can be sent to multi-core CPU, the core cpu that this DXEDriver runs carries out the adjustment of running status, after adjustment completes, return the running status after this DXEDriver adjustment; Optionally, the running status after this DXEDriver adjustment can be returned to DXE service list.
The task list of the DXEDriver that step S324, acquisition run, cushions described task list in the buffer zone of specifying.
Described task list comprises the task ID of the DXEDriver be placed on multi-core CPU and the task run state of correspondence.Optionally, the task list of the DXEDriver run is obtained by DXE service list; Certainly, when not arranging DXE service list, can to the running status of DXEDriver corresponding to each task ID of multi-core CPU request, thus by the task list of task ID and task run state group synthesis DXEDriver.
Optionally, the embodiment of the present invention can an administration step S322, step S323, and at least one step in step S324, is specifically determined by actual service condition.
In the embodiment of the present invention, DXEDriverProtocol is the mutual bridge between DXEDriver and multi-core CPU, therefore described Protocol can be expressed as EFI_MPPROTOCOL, hereafter also show some optimum configurations of described Protocol, can with combine about the description of DXE stage BIOS operational process above; It should be noted that the visual concrete service condition of some parameters hereafter illustrated does necessary deleting.
EFI_MP_PROTOCOL
Describe: multitask service is provided, DXEdriver is run on different CPU core; Control multitask, whole task run state of withering, for running, stops, dormancy; Return current operation multitask list.
Multi-task state defines:
Parameter: RunDriver, runs DXEdriver, it is put on multi-core CPU, provides multitask running service, refer to hereafter RunDriver () API and describe; GetState, obtains appointed task state, refers to hereafter GetState () API and describe; SetState, setting task run state, refers to hereafter SetState () API and describes; GetTaskList, returns current operation multitask list, refers to hereafter GetTaskList () API and describes.
EFI_MP_PROTOCOL.RunDriver()
Describe: run DXEdriver, it is put on multi-core CPU, multitask running service is provided.
Prototype
Suction parameter: DxeDriverGuid, waits to run DXEDriverGUID; TaskId, returns appointed task ID.
Outlet parameter: state value.
EFI_MP_PROTOCOL.GetState()
Describe: obtain appointed task state.
Prototype
Suction parameter: TaskId, appointed task ID; TaskState, task status.
Outlet parameter: state value.
EFI_MP_PROTOCOL.SetState()
Describe: setting task run state.
Prototype
Suction parameter: TaskId, appointed task ID; TaskState, appointed task state.
Outlet parameter: state value.
EFI_MP_PROTOCOL.GetTaskList()
Describe: return current operation multitask list.
Suction parameter: TaskListBuffer, buffer zone, for placing current whole operation task list; TaskListBufferSize, buffer size.
Outlet parameter: state value.
Hereafter also show BIOS and notify the optimum configurations of task list, can together with phase reference above.
EFI_PEI_MP_POST_TABLE
Describe: 1, whether the static PEIDriver that specifies operates on multinuclear; If 2 run PEIDriver on multinuclear, the need of specifying on fixing core.
Parameter: PeiDrive, points to PeiDriverGUID; Whether MpCapability, PEIDriver support multitask, if be 0, mean that this PEIDriver does not support multitask, non-zero, support multitask; CoreNum, if MpCapability is non-zero, is then appointed as the CPUCore(core that PEIDriver runs) Number, wherein Number0 is BSPNumber, Number1-N is that APNumber, Number-1 represent the appointment not carrying out CoreNumber, by BIOS selected CoreNumber voluntarily; It should be noted that visual concrete service condition being set and changing of the concrete numerical value of this section.
EFI_DXE_MP_POST_TABLE
Describe: 1, whether the static DXEDriver that specifies operates on multinuclear; If 2 run DXEDriver on multinuclear, the need of specifying on fixing core.
Parameter: DxeDriver, points to DXEDriverGUID; Whether MpCapability, DXEDriver support multitask, if be 0, mean that this DXEDriver does not support multitask, non-zero, support multitask; CoreNum, if MpCapability is non-zero, is then appointed as the CPUCoreNumber that DXEDriver runs, wherein Number0 is BSPNumber, Number1-N is that APNumbers, Number-1 represent the appointment not carrying out CoreNumber, by BIOS selected CoreNumber voluntarily; It should be noted that visual concrete service condition being set and changing of the concrete numerical value of this section.
Optionally, the embodiment of the present invention, at the beginning of operation BIOS, also can carry out the initialization operation of multi-core CPU; Concrete, BSP can be utilized to pass through APIC(AdvancedProgrammableInterruptController, Advanced Programmable Interrupt Controllers APICs) bus broadcasts SIPI(Start-upIPIMessage to multi-core CPU, start inter-processor interrupt, wherein, IPI represents InterprocessorInterrupt, inter-processor interrupt) information, with each core of initialization multi-core CPU.Fig. 7 shows and carries out the initialized schematic diagram of multi-core CPU, can together reference.
Be described the BIOS chip that the embodiment of the present invention provides below, it should be noted that BIOS chip described below is corresponding with above-described BIOS operation method, both can be cross-referenced.
The structured flowchart of the BIOS chip that Fig. 8 provides for the embodiment of the present invention, with reference to Fig. 8, BIOS chip can comprise: scheduler determination module 100, the routine call module 200 be connected with scheduler determination module 100, the task allocating module 300 be connected with routine call module 200;
Wherein, scheduler determination module 100, in BIOS operational process, determines the scheduler that the current BIOS operation phase is corresponding;
Routine call module 200, for using the determined scheduler of scheduler determination module 100, transfers the Driver calling program corresponding with the current BIOS operation phase;
Task allocating module 300, for using described Driver calling program, puts into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, and multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
Optionally, describedly meet pre-conditioned Driver and can comprise: notify to set in task list with preset BIOS, the Driver that the Driver putting into multi-core CPU in the current BIOS operation phase is corresponding, described BIOS notifies that task list carries the Driver information that each BIOS operation phase needs to put into multi-core CPU; Or, the Driver that the current BIOS operation phase is whole.
The BIOS chip that the embodiment of the present invention provides achieves the object running BIOS on multi-core CPU, solve existing BIOS can only operate on BSP, and cause to support the problem of multitask running under BIOS environment, achieve the support of the multitask running under BIOS environment, improve the task treatment effeciency in BIOS operational process.
Obviously, the BIOS chip that the embodiment of the present invention provides, at least one stage in BIOS operational process can realize multitask support, optionally, BIOS chip can realize multitask support in the PEI stage, and/or realizes multitask support in the DXE stage.
Another structured flowchart of the BIOS chip that Fig. 9 provides for the embodiment of the present invention, BIOS chip structure during the chip of BIOS shown in Fig. 9 to be the current BIOS operation phase be PEI stage, with reference to Fig. 9, in the PEI stage, scheduler determination module 100 can comprise: the first scheduler determining unit 110, during for being PEI stage in the current BIOS operation phase, determine the PEIDispatcher that the PEI stage is corresponding;
Routine call module 200 can comprise: the first routine call unit 210, and during for being PEI stage in the current BIOS operation phase, the PEIDispatcher using the first scheduler determining unit 110 to determine transfers PEIDriver calling interface PPI;
Task allocating module 300 can comprise: first task allocation units 310, during for being PEI stage in the current BIOS operation phase, uses described PPI to put into multi-core CPU by meeting pre-conditioned PEIDriver in the PEI stage.
Figure 10 shows the structure of first task allocation units, and with reference to Figure 10, first task allocation units 310 can comprise:
First waits that running task identification obtains subelement 311, for being obtained the Guid waiting to run PEIDriver by PEI service list;
First task places subelement 312, for corresponding for described Guid is treated that meeting pre-conditioned PEIDriver in operation PEIDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned PEIDriver;
First operation task identification feedback subelement 313, for obtaining the task identification ID of the PEIDriver run, returns described task ID to described PEI service list.
In the structure of the allocation units of first task shown in Figure 10, Figure 11 shows the another structure of BIOS chip, also comprises with reference to BIOS chip shown in Fig. 9 and Figure 11, Figure 11:
First task running status feedback module 01, at the first operation task identification feedback subelement 313 when returning described task ID to PEI service list, return the running status of PEIDriver corresponding to described task ID on multi-core CPU to PEI service list;
First task state acquisition module 02, for being obtained the task ID of the PEIDriver run by described PEI service list, obtains the running status of the PEIDriver specifying task ID corresponding in described task ID;
First task state adjusting module 03, for controlling the running status of the PEIDriver specifying task ID corresponding in described task ID, adjust the running status of PEIDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after PEIDriver adjustment corresponding to described appointed task ID to described PEI service list;
First task list determining module 04, for being obtained the task list of the PEIDriver of current operation by described PEI service list, described task list comprises the task ID of the PEIDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
Obviously, the chip of BIOS shown in the embodiment of the present invention can only include first task running status feedback module 01, and, at least one in first task state acquisition module 02, first task state adjusting module 03, first task list determining module 04.
A structured flowchart again of the BIOS chip that Figure 12 provides for the embodiment of the present invention, BIOS chip structure during the chip of BIOS shown in Figure 12 to be the current BIOS operation phase be DXE stage, with reference to Figure 12, in the DXE stage, scheduler determination module 100 can comprise: the second scheduler determining unit 120, during for being DXE stage in the current BIOS operation phase, determine the DXEDispatcher that the DXE stage is corresponding;
Routine call module 200 can comprise: the second routine call unit 220, during for being DXE stage in the current BIOS operation phase, uses the determined DXEDispatcher of the second scheduler determining unit 120 to transfer DXEDriver invocation protocol Protocol;
Task allocating module 300 can comprise: the second task allocation unit 320, during for being DXE stage in the current BIOS operation phase, uses described Protocol that the DXEDriver that the DXE stage meets default bar is put into multi-core CPU.
Wherein, the structure of the second task allocation unit 320 can as shown in figure 13, comprise:
Second waits that running task identification obtains subelement 321, for obtaining the mark Guid waiting to run DXEDriver;
Second task places subelement 322, for corresponding for described Guid is treated that meeting pre-conditioned DXEDriver in operation DXEDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned DXEDrive;
Second operation task identification feedback subelement 323, for obtaining the task ID of the DXEDriver run, returns described task ID.
On the basis of the second task allocation unit 320 shown in Figure 13, Figure 14 shows the another again structure of BIOS chip, also comprises with reference to BIOS chip shown in Figure 12 and Figure 14, Figure 14:
Second task run feedback of status module 1, for when the second operation task identification feedback subelement 323 returns described task ID, returns the running status of DXEDriver corresponding to described task ID on multi-core CPU;
Second task status acquisition module 2, for obtaining the running status of the DXEDriver specifying task ID corresponding in described task ID;
Second task status adjusting module 3, for controlling the running status of the DXEDriver specifying task ID corresponding in described task ID, adjust the running status of DXEDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after DXEDriver adjustment corresponding to described appointed task ID;
Second task list determination module 4, for obtaining the task list of the DXEDriver of operation, described task list comprises the task ID of the DXEDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
Another structured flowchart again of the BIOS chip that Figure 15 provides for the embodiment of the present invention, also comprises with reference to BIOS chip shown in Fig. 8 and Figure 15, Figure 15:
Initialization module 400, for utilizing BSP by APIC bus to multi-core CPU broadcast SIPI information, with each core of initialization multi-core CPU.
Initialization module 400 can carry out the initialization of multi-core CPU at the beginning of BIOS runs.
The BIOS operation method that the embodiment of the present invention provides and BIOS chip, achieve the support of the multitask running under BIOS environment.
In this instructions, each embodiment adopts the mode of going forward one by one to describe, and what each embodiment stressed is the difference with other embodiments, between each embodiment identical similar portion mutually see.For device disclosed in embodiment, because it corresponds to the method disclosed in Example, so description is fairly simple, relevant part illustrates see method part.
Professional can also recognize further, in conjunction with unit and the algorithm steps of each example of embodiment disclosed herein description, can realize with electronic hardware, computer software or the combination of the two, in order to the interchangeability of hardware and software is clearly described, generally describe composition and the step of each example in the above description according to function.These functions perform with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Professional and technical personnel can use distinct methods to realize described function to each specifically should being used for, but this realization should not thought and exceeds scope of the present invention.
The method described in conjunction with embodiment disclosed herein or the step of algorithm can directly use hardware,
The software module that processor performs, or the combination of the two is implemented.Software module can be placed in the storage medium of other form any known in random access memory (RAM), internal memory, ROM (read-only memory) (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
To the above-mentioned explanation of the disclosed embodiments, professional and technical personnel in the field are realized or uses the present invention.To be apparent for those skilled in the art to the multiple amendment of these embodiments, General Principle as defined herein can without departing from the spirit or scope of the present invention, realize in other embodiments.Therefore, the present invention can not be restricted to these embodiments shown in this article, but will meet the widest scope consistent with principle disclosed herein and features of novelty.
Claims (17)
1. support a BIOS operation method for multitask, it is characterized in that, comprising:
In BIOS operational process, determine the scheduler that the current BIOS operation phase is corresponding;
Described scheduler is used to transfer the driving Driver calling program corresponding with the current BIOS operation phase;
Using described Driver calling program, putting into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
2. method according to claim 1, is characterized in that, the current BIOS operation phase is the PEI stage; Describedly determine that scheduler corresponding to current BIOS operation phase comprises: determine the PEI scheduler Dispatcher that the PEI stage is corresponding;
The described scheduler of described use is transferred the Driver calling program corresponding with the current BIOS operation phase and is comprised:
Described PEIDispatcher is used to transfer PEIDriver calling interface PPI;
The described Driver calling program of described use, put into multi-core CPU comprise meeting pre-conditioned Driver in the current BIOS operation phase:
Described PPI is used to put into multi-core CPU by meeting pre-conditioned PEIDriver in the PEI stage.
3. method according to claim 2, is characterized in that, the described PPI of described use puts into multi-core CPU comprise meeting pre-conditioned PPIDriver in the PEI stage:
The mark Guid waiting to run PEIDriver is obtained by PEI service list;
Corresponding for described Guid is treated that meeting pre-conditioned PEIDriver in operation PEIDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned PEIDriver, obtain the task identify label ID of the PEIDriver run, return described task ID to described PEI service list.
4. method according to claim 3, also comprises when returning described task ID to PEI service list: return the running status of PEIDriver corresponding to described task ID on multi-core CPU to PEI service list;
Described method also comprises:
Obtained the task ID of the PEIDriver run by described PEI service list, obtain the running status of the PEIDriver specifying task ID corresponding in described task ID; Or,
The running status of the PEIDriver specifying task ID corresponding in described task ID is controlled, adjust the running status of PEIDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after PEIDriver adjustment corresponding to described appointed task ID to described PEI service list; Or,
Obtained the task list of the PEIDriver of current operation by described PEI service list, described task list comprises the task ID of the PEIDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
5. method according to claim 1, is characterized in that, the current BIOS operation phase is the DXE stage; Describedly determine that scheduler corresponding to current BIOS operation phase comprises: determine the DXE scheduler Dispatcher that the DXE stage is corresponding;
The described scheduler of described use is transferred the Driver calling program corresponding with the current BIOS operation phase and is comprised:
Described DXEDispatcher is used to transfer DXEDriver invocation protocol Protocol;
The described Driver calling program of described use, put into multi-core CPU comprise meeting pre-conditioned Driver in the current BIOS operation phase:
Use described Protocol that the DXEDriver that the DXE stage meets default bar is put into multi-core CPU.
6. method according to claim 5, is characterized in that, the DXEDriver that the DXE stage is met default bar by the described Protocol of described use puts into multi-core CPU and comprises:
Obtain the mark Guid waiting to run DXEDriver;
Corresponding for described Guid is treated that meeting pre-conditioned DXEDriver in operation DXEDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned DXEDrive, obtain the task identify label ID of the DXEDriver run, return described task ID.
7. method according to claim 6, is characterized in that, also comprises while returning described task ID: return the running status of DXEDriver corresponding to described task ID on multi-core CPU;
Described method also comprises:
Obtain the running status of the DXEDriver specifying task ID corresponding in described task ID; Or,
The running status of the DXEDriver specifying task ID corresponding in described task ID is controlled, adjust the running status of DXEDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after DXEDriver adjustment corresponding to described appointed task ID; Or,
Obtain the task list of the DXEDriver run, described task list comprises the task ID of the DXEDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
8. the method according to any one of claim 1 to 7, it is characterized in that, describedly meet pre-conditioned Driver and comprise: notify to set in task list with preset BIOS, the Driver that the Driver putting into multi-core CPU in the current BIOS operation phase is corresponding, described BIOS notifies that task list carries the Driver information that each BIOS operation phase needs to put into multi-core CPU; Or, the Driver that the current BIOS operation phase is whole.
9. the method according to any one of claim 1 to 7, is characterized in that, also comprises:
BSP is utilized to start inter-processor interrupt SIPI information, with each core of initialization multi-core CPU by Advanced Programmable Interrupt Controllers APICs APIC bus to multi-core CPU broadcast.
10. a BIOS chip, is characterized in that, comprising: scheduler determination module, the routine call module be connected with described scheduler determination module, the task allocating module be connected with described routine call module;
Described scheduler determination module, in BIOS operational process, determines the scheduler that the current BIOS operation phase is corresponding;
Described routine call module, for using the determined scheduler of described scheduler determination module, transfers the driving Driver calling program corresponding with the current BIOS operation phase;
Described task allocating module, for using described Driver calling program, puts into multi-core CPU by meeting pre-conditioned Driver in the current BIOS operation phase, and multiple core cpu runs Driver corresponding to multiple current BIOS operation phase.
11. BIOS chips according to claim 10, is characterized in that, described scheduler determination module comprises:
First scheduler determining unit, during for being PEI stage in the current BIOS operation phase, determines the PEI scheduler Dispatcher that the PEI stage is corresponding;
Described routine call module comprises:
First routine call unit, during for being PEI stage in the current BIOS operation phase, the PEIDispatcher using described first scheduler determining unit to determine transfers PEIDriver calling interface PPI;
Described task allocating module comprises:
First task allocation units, during for being PEI stage in the current BIOS operation phase, use described PPI to put into multi-core CPU by meeting pre-conditioned PEIDriver in the PEI stage.
12. BIOS chips according to claim 11, is characterized in that, described first task allocation units comprise:
First waits that running task identification obtains subelement, for being obtained the mark Guid waiting to run PEIDriver by PEI service list;
First task places subelement, for corresponding for described Guid is treated that meeting pre-conditioned PEIDriver in operation PEIDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned PEIDriver;
First operation task identification feedback subelement, for obtaining the task identification ID of the PEIDriver run, returns described task ID to described PEI service list.
13. BIOS chips according to claim 12, is characterized in that, also comprise:
First task running status feedback module, at described first operation task identification feedback subelement when returning described task ID to PEI service list, return the running status of PEIDriver corresponding to described task ID on multi-core CPU to PEI service list;
First task state acquisition module, for being obtained the task ID of the PEIDriver run by described PEI service list, obtains the running status of the PEIDriver specifying task ID corresponding in described task ID;
First task state adjusting module, for controlling the running status of the PEIDriver specifying task ID corresponding in described task ID, adjust the running status of PEIDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after PEIDriver adjustment corresponding to described appointed task ID to described PEI service list;
First task list determining module, for being obtained the task list of the PEIDriver of current operation by described PEI service list, described task list comprises the task ID of the PEIDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
14. BIOS chips according to claim 10, is characterized in that, described scheduler determination module comprises:
Second scheduler determining unit, during for being DXE stage in the current BIOS operation phase, determines the DXE scheduler Dispatcher that the DXE stage is corresponding;
Described routine call module comprises:
Second routine call unit, during for being DXE stage in the current BIOS operation phase, uses the determined DXEDispatcher of described second scheduler determining unit to transfer DXEDriver invocation protocol Protocol;
Described task allocating module comprises:
Second task allocation unit, during for being DXE stage in the current BIOS operation phase, uses described Protocol that the DXEDriver that the DXE stage meets default bar is put into multi-core CPU.
15. BIOS chips according to claim 14, is characterized in that, described second task allocation unit comprises:
Second waits that running task identification obtains subelement, for obtaining the mark Guid waiting to run DXEDriver;
Second task places subelement, for corresponding for described Guid is treated that meeting pre-conditioned DXEDriver in operation DXEDriver puts into multi-core CPU, multiple core cpu runs and meets pre-conditioned DXEDrive;
Second operation task identification feedback subelement, for obtaining the task ID of the DXEDriver run, returns described task ID.
16. BIOS chips according to claim 15, is characterized in that, also comprise:
Second task run feedback of status module, for when described second operation task identification feedback subelement returns described task ID, returns the running status of DXEDriver corresponding to described task ID on multi-core CPU;
Second task status acquisition module, for obtaining the running status of the DXEDriver specifying task ID corresponding in described task ID;
Second task status adjusting module, for controlling the running status of the DXEDriver specifying task ID corresponding in described task ID, adjust the running status of DXEDriver corresponding to described appointed task ID at described multi-core CPU after, return the running status after DXEDriver adjustment corresponding to described appointed task ID;
Second task list determination module, for obtaining the task list of the DXEDriver of operation, described task list comprises the task ID of the DXEDriver be placed on multi-core CPU and the task run state of correspondence, cushions described task list in the buffer zone of specifying.
17., according to claim 10 to the BIOS chip described in 16 any one, is characterized in that, also comprise:
Initialization module, starts inter-processor interrupt SIPI information, with each core of initialization multi-core CPU by Advanced Programmable Interrupt Controllers APICs APIC bus to multi-core CPU broadcast for utilizing BSP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310095193.9A CN103150208B (en) | 2013-03-22 | 2013-03-22 | A kind of BIOS operation method and BIOS chip supporting multitask |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310095193.9A CN103150208B (en) | 2013-03-22 | 2013-03-22 | A kind of BIOS operation method and BIOS chip supporting multitask |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103150208A CN103150208A (en) | 2013-06-12 |
| CN103150208B true CN103150208B (en) | 2016-03-09 |
Family
ID=48548306
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310095193.9A Active CN103150208B (en) | 2013-03-22 | 2013-03-22 | A kind of BIOS operation method and BIOS chip supporting multitask |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103150208B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293620B (en) * | 2016-08-09 | 2019-05-14 | 浪潮电子信息产业股份有限公司 | Method for detecting parameters in Flash Rom by intel platform |
| CN116028129B (en) * | 2023-03-29 | 2023-06-13 | 湖南博匠信息科技有限公司 | UEFI (unified extensible firmware interface) quick starting method based on Feiteng platform and Feiteng platform |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1542606A (en) * | 2003-04-28 | 2004-11-03 | ض� | Methods and apparatus to operate in multiple phases of a basic input/output system (BIOS) |
| WO2010090636A1 (en) * | 2009-02-03 | 2010-08-12 | Hewlett-Packard Development Company, L.P. | Electronic device with overlapped boot task fetches and boot task execution |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8086838B2 (en) * | 2008-08-13 | 2011-12-27 | Dell Products L.P. | Methods and systems for providing manufacturing mode detection and functionality in a UEFI BIOS |
-
2013
- 2013-03-22 CN CN201310095193.9A patent/CN103150208B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1542606A (en) * | 2003-04-28 | 2004-11-03 | ض� | Methods and apparatus to operate in multiple phases of a basic input/output system (BIOS) |
| WO2010090636A1 (en) * | 2009-02-03 | 2010-08-12 | Hewlett-Packard Development Company, L.P. | Electronic device with overlapped boot task fetches and boot task execution |
| CN102308279A (en) * | 2009-02-03 | 2012-01-04 | 惠普开发有限公司 | Electronic device with overlapped boot task fetches and boot task execution |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103150208A (en) | 2013-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107577185B (en) | A kind of task executing method and the controller based on multi-core processor | |
| CN110888743B (en) | GPU resource using method, device and storage medium | |
| CN102890643B (en) | Resource scheduling system based on immediate feedback of application effect under display card virtualization | |
| EP0990977B1 (en) | Power control method and apparatus therefor | |
| JP5532271B2 (en) | Method and system for performing computer tasks in reduced power consumption states | |
| US20050132363A1 (en) | Method, apparatus and system for optimizing context switching between virtual machines | |
| US7051222B2 (en) | Robust computer subsystem power management with or without explicit operating system support | |
| DE10393969T5 (en) | Mechanism for distributing lowest priority interrupts considering the processor performance state | |
| US20180173299A1 (en) | System and method for performing distributed power management without power cycling hosts | |
| US11243795B2 (en) | CPU overcommit with guest idle polling | |
| JPH07306844A (en) | Non-stop program changing method for multiprocessor system, multiprocessor system, and non-stop program changing method for disk controller and disk controller | |
| US20130067133A1 (en) | Handling interrupts in data processing | |
| CN117311990B (en) | Resource adjustment method and device, electronic equipment, storage medium and training platform | |
| JPH11202988A (en) | System power consumption control method | |
| CN111858038A (en) | Method, device and medium for reading data in FPGA board memory | |
| EP0670539B1 (en) | Method and apparatus for conserving power in a computer system using a power management pseudo-device driver | |
| CN108196946A (en) | A kind of subregion multinuclear method of Mach | |
| CN103150208B (en) | A kind of BIOS operation method and BIOS chip supporting multitask | |
| EP2587374A1 (en) | Multi-core system and scheduling method | |
| US20080313483A1 (en) | Method and System for Power Management | |
| CN118819864A (en) | Resource unified scheduling method and system for multiple types of loads | |
| JPH04195619A (en) | Power consumption control method | |
| US20230185623A1 (en) | Method of task transition between heterogenous processors | |
| CN117724381A (en) | Multi-core parallel computing scheduling method based on logic configuration program | |
| CN117369986A (en) | Interrupt request equalization method and device and computing equipment |
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 |