CN115237429A - Cloud server test verification method based on firmware dynamic parameter adjustment - Google Patents
Cloud server test verification method based on firmware dynamic parameter adjustment Download PDFInfo
- Publication number
- CN115237429A CN115237429A CN202210845820.5A CN202210845820A CN115237429A CN 115237429 A CN115237429 A CN 115237429A CN 202210845820 A CN202210845820 A CN 202210845820A CN 115237429 A CN115237429 A CN 115237429A
- Authority
- CN
- China
- Prior art keywords
- firmware
- parameter adjustment
- bmc
- dynamic parameter
- server
- 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.)
- Pending
Links
- 238000012795 verification Methods 0.000 title claims abstract description 54
- 238000012360 testing method Methods 0.000 title claims abstract description 50
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000009471 action Effects 0.000 claims abstract description 5
- 238000010200 validation analysis Methods 0.000 claims abstract description 5
- 230000008569 process Effects 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 6
- 230000003993 interaction Effects 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000007689 inspection Methods 0.000 claims description 2
- 238000013507 mapping Methods 0.000 claims description 2
- 230000007246 mechanism Effects 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 6
- 230000008520 organization Effects 0.000 description 5
- 239000003795 chemical substances by application Substances 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/56—Computer malware detection or handling, e.g. anti-virus arrangements
- G06F21/562—Static detection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Abstract
The invention discloses a cloud server test verification method based on firmware dynamic parameter adjustment, which comprises the following steps of firstly, triggering system management interruption by using a server BMC to send a dynamic parameter adjustment packet to system firmware; then, a processing program of the system firmware verifies the dynamic parameter adjustment packet received from the BMC, analyzes data in the packet and carries out corresponding dynamic parameter adjustment action; after the new parameter adjustment is completed, the system firmware informs the BMC that the new parameter adjustment is completed; finally, the BMC coordinates the server test validation based on the new firmware parameters that have been validated. The invention innovatively combines the system firmware and the BMC, realizes a mechanism for dynamically adjusting firmware parameters during the operation of the system, and greatly improves the efficiency of server test and verification.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a cloud server test verification method based on firmware dynamic parameter adjustment.
Background
The server is the core foundation of modern cloud computing centers. Currently, the servers of the X86 architecture are still the mainstream of the servers, and occupy more than 90% of the deployment amount of the servers. With the rapid development of the fields of cloud computing, artificial intelligence, edge computing and the like, higher and higher requirements are put forward on cloud computing core infrastructure, wherein the core basic server has stronger and stronger performance and richer functions. Taking the latest X86 server platform of Intel as an example, the maximum core number of a single CPU reaches more than 60 cores, and 8 DDR5 memory channels, 80 PCIE links, a large number of RAS (Reliability/Availability/Serviceability) and security characteristics are supported. Increasingly complex server systems pose significant challenges to validation and deployment. The system firmware is the basis of initialization and healthy operation of the server system and comprises a large number of parameter settings which are crucial to high-performance, high-reliability and high-safety work of the server. Due to the fact that the server system is complex in structure, numerous in components and rich in firmware parameter configuration, the test and verification complexity and workload of the server are increased rapidly.
The existing server test verification method generally deploys a batch of machines with selected typical hardware configuration, sets different firmware parameter configurations and software configurations on the machines respectively, and runs corresponding test cases (testcases) to verify each field of server function and performance. Before running different test cases, most of the test cases need to be adjusted in firmware parameter setting, and the server is restarted to enable new firmware parameters to take effect.
Due To complexity of server composition and system configuration, each Time a server is restarted, the existing server test verification method needs a long Time, generally, calculation is performed in units of minutes, meanwhile, verification of some servers needs To be performed by starting or running corresponding loads (workloads) under an operating system, the server is restarted, so that the loads also need To be restarted or run, additional overhead (overhead) is caused, time consumption and efficiency of server system test verification are greatly increased, time To Market (TTM) of a product of the server and Time for deploying applications are greatly delayed, and coverage breadth and depth of server test verification can be reduced.
Disclosure of Invention
The technical problems solved by the invention are as follows: the cloud server test verification method based on firmware dynamic parameter adjustment is characterized in that a system firmware and a BMC are matched to realize a mechanism for dynamically adjusting firmware parameters during system operation, and the efficiency of server test verification is greatly improved.
The technical scheme is as follows: in order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a cloud server test verification method based on firmware dynamic parameter adjustment comprises the following steps that firstly, a server BMC is used for triggering system management interruption to send a dynamic parameter adjustment packet to system firmware; then, a processing program of the system firmware verifies the dynamic parameter adjustment packet received from the BMC, analyzes data in the packet and carries out corresponding dynamic parameter adjustment action; after the new parameter adjustment is completed, the system firmware informs the BMC that the new parameter adjustment is completed; finally, the BMC coordinates the server test validation based on the new firmware parameters that have been validated.
Preferably, the method is divided into two aspects according to different stages in the starting and running process of the server:
s1: initializing a system firmware dynamic parameter adjustment system management interrupt processing program in the starting process of the server, and establishing a channel for operating system runtime interaction between the BMC and the system firmware;
s2: and when the server is started and enters the operation stage of the operating system, the system performs test verification under various parameter configurations according to the test verification plan.
Preferably, the step S1 is implemented as follows:
s11: powering up a system and carrying out power-up self-inspection;
s12: allocating a general input/output interface GPIO connected with the BMC as a trigger source of a system firmware dynamic parameter adjustment system management interrupt processing program;
s13: registering a system firmware dynamic parameter adjustment system management interrupt processing program;
s14: initializing a PCIE memory mapping space visible by a BMC at a host end of a server system as a shared data buffer area between the BMC and system firmware;
s15: enabling a general input/output interface GPIO connected with the BMC to be used as a trigger source for adjusting system management interrupt by using the dynamic parameters of the system firmware;
s16: and after the power-on self-check is completed, starting the operating system.
Preferably, the step S2 is implemented as follows:
s21: the BMC prepares a firmware parameter adjusting package which needs to be deployed during the verification and puts the firmware parameter adjusting package into a shared data buffer area;
s22: the BMC triggers system management interruption through a GPIO connected with a host end of the server system to inform system firmware processing;
s23: the system firmware responds to the system management interrupt, and a firmware dynamic parameter registered in the power-on self-test process is called to adjust a system management interrupt processing program;
s24: the firmware dynamic parameter adjustment system manages an interrupt processing program and receives a firmware parameter adjustment packet from a shared data buffer area between the firmware dynamic parameter adjustment system and the BMC; judging whether the receiving is successful, and restarting if the BMC is informed that the receiving is unsuccessful; if the receiving is successful, go to step S25;
s25: the firmware dynamic parameter adjustment shared data buffer area verifies the signature of the firmware parameter adjustment packet; if the signature verification is not passed, notifying the BMC that the firmware parameter adjusting packet is an illegal data packet, and terminating the program; if the signature verification is passed, go to step S26;
s26: analyzing and applying the data of the firmware dynamic parameter adjustment packet;
s27: and informing the BMC that the parameter adjustment is successful, and starting to carry out cloud server verification based on the parameter adjustment.
Preferably, in step S26, the firmware dynamic parameter adjustment system manages the interrupt handler, and after the signature verification of the firmware parameter adjustment package is completed and the source is legal and safe, the Payload in the firmware parameter adjustment package is analyzed and applied.
6. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 5, wherein: the specific process of analysis and application is as follows:
s261: judging whether payload is carried, platform and = built-in platform ID, if yes, entryindex =0; if not, the Payload non-platform applies Payload;
s262: judging whether payload is more than 0 and Entryindex is less than payload; if not, ending the process; if the condition is satisfied, go to step S263;
s263: processing according to Payload.
S264：Entryindex++。
Has the beneficial effects that: compared with the prior art, the invention has the following advantages:
(1) The cloud server test verification method based on firmware dynamic parameter adjustment improves the test verification efficiency of the server system and the test verification breadth and depth of the server system: the firmware parameters can be dynamically adjusted, so that the time consumption for restarting the server verification system and restarting the load of the operating system by deploying new firmware parameters every time is avoided, and the server system verification test case which can be completed in unit time is greatly improved. And because various firmware parameters can be conveniently combined and verified, the breadth and the depth of system verification coverage can be well increased.
(2) Universality: the BMC and the like belong to basic constituent units of the server, and the cooperation with system firmware are easy to realize.
(3) Expansibility: the invention can be used for testing and verifying the server system, provides a feasible method for real-time dynamic firmware parameter adjustment of the server which is actually deployed and operated, and has good expansibility.
(4) Safety is as follows: the dynamic parameter adjustment packet transmitted to the system firmware is developed by a server platform or signed by a producer, and the system firmware performs signature verification action after receiving the dynamic parameter adjustment packet before analyzing data in the use packet, so that the safety of the dynamic parameter adjustment packet is ensured, and a malicious parameter adjustment data packet is prevented from being used for system parameter adjustment;
(5) The invention has practical application in the verification of the X86 server firmware test (such as Intel Eagle Stream platform) of the applicant.
Drawings
FIG. 1 is a diagram of the system firmware dynamic parameter adjustment initialization process of the present invention;
FIG. 2 is a flow chart of adjusting dynamic parameters of Runtime system firmware according to the present invention;
FIG. 3 illustrates firmware dynamic parameter adjustment packet parsing and application according to the present invention;
FIG. 4 is a diagram of the data structure associated with the firmware dynamic parameter adjustment package of the present invention.
Detailed Description
The present invention will be further illustrated with reference to the following specific examples, which are carried out in the light of the technical solutions of the present invention, and it should be understood that these examples are only intended to illustrate the present invention and are not intended to limit the scope of the present invention.
The invention discloses a cloud server test verification method based on firmware dynamic parameter adjustment, which takes a mainstream X86 architecture cloud server as an example, and provides a server test verification method based on firmware parameter dynamic adjustment.
System firmware BIOS (Basic Input Output System): the system program is a set of system programs solidified in a storage chip on a mainboard of the computing equipment, plays an indispensable role in normal initialization, starting and operating system boot of a computer system, and is also a key link for realizing key functions of the computer system, such as safety, reliability and the like.
System Management Interrupt SMI (System Management Interrupt): the special management interrupt is a special management interrupt on an X86 architecture, is transparent to an operating system, is responded and processed by a system management interrupt Handler (SMI Handler) registered by a system firmware BIOS in the boot initialization process, and is generally used for realizing platform specific management or additional functions.
BMC (Basebaard Management Controller): the system is a basic core function subsystem of the server, is responsible for core functions of hardware state management, operating system management, health state management, power consumption management and the like of the server, can realize remote monitoring and management of the server, and is a core common technology of the server and cloud computing industry.
The cloud server test verification method based on firmware dynamic parameter adjustment in the embodiment includes the following steps:
firstly, triggering system management interruption by using a server BMC to send a dynamic parameter adjustment packet to system firmware; then, the system management interrupt processing program of the system firmware verifies the dynamic parameter adjustment packet received from the BMC, analyzes the data (dynamic system configuration payload) in the packet, and performs corresponding dynamic parameter adjustment actions, including write/read/clear/lock/unlock/polling of MSR register/PCI configuration space register/MMIO space register and the like; after the new parameter adjustment is completed, the system firmware informs the BMC that the new parameter adjustment is completed; finally, the BMC coordinates the server test validation based on the new firmware parameters that have been validated.
In the embodiment, an organization coordinator (organization agent) for testing and verifying dynamic parameter adjustment of the server BMC server system is used instead of the organization coordinator (organization agent) or an organization coordinator running in the cloud server operating system.
The specific implementation scheme is divided into two aspects according to different stages in the starting and running processes of the server:
s1: in the process of starting the server, the dynamic parameter adjustment SMI Handler of the system firmware needs to be initialized, and a channel is established for operating system Runtime (Runtime) interaction between the BMC and the system firmware, specifically as shown in fig. 1, the method includes the following steps:
s11: powering on a system, and carrying out power-on self-test (POST) of a BIOS;
s12: allocating a General Purpose Input/Output interface GPIO (General Purpose Input/Output) connected with the BMC as a trigger source of system firmware dynamic parameter adjustment SMI;
s13: registering a system firmware dynamic parameter to adjust an SMI Handler;
s14: initializing a PCIE Memory Mapped IO (input/output) space visible by a BMC (baseboard management controller) at a Host end (namely a Host end) of a server system as a shared data buffer (shared Memory buffer) with system firmware;
s15: enabling a general input/output interface GPIO connected with the BMC to serve as a system firmware dynamic parameter adjustment SMI trigger source;
s16: and after the POST is finished, starting the operating system.
And when the server is started and enters a Runtime stage, the system can carry out test verification under various parameter configurations according to a test verification plan. Fig. 2 shows a flow of dynamically adjusting firmware parameters before each test verification in the Runtime stage, which includes the following specific steps:
s21: the BMC prepares a firmware parameter adjusting package which needs to be deployed during the verification and puts the firmware parameter adjusting package into a shared data buffer area;
s22: the BMC triggers system management interruption to inform system firmware processing through GPIO connected with a server system host;
s23: the system firmware responds to the system management interrupt, and a firmware dynamic parameter registered in the power-on self-test process is called to adjust a system management interrupt processing program;
s24: the firmware dynamic parameter adjustment system management interrupt processing program receives a firmware parameter adjustment packet from a shared data buffer between the firmware dynamic parameter adjustment system management interrupt processing program and the BMC; judging whether the receiving is successful, and restarting if the BMC is informed that the receiving is unsuccessful; if the reception is successful, performing step S25;
s25: verifying the signature of the firmware parameter adjustment package by the firmware dynamic parameter adjustment system management interrupt processing program; if the signature verification is not passed, notifying the BMC that the firmware parameter adjustment packet is an illegal data packet, and terminating the firmware parameter adjustment; if the signature verification passes, go to step S26;
s26: analyzing and applying the data of the firmware dynamic parameter adjustment package;
s27: and informing the BMC that the parameter adjustment is successful, and starting the cloud server verification based on the parameter adjustment.
Specifically, in step 26, the specific implementation and related data structure for analyzing and applying the data of the firmware dynamic parameter adjustment package are as follows:
the firmware DYNAMIC parameter adjustment SYSTEM manages an interrupt handler, and after the verification of the firmware parameter adjustment packet is completed and the source thereof is determined to be legal and safe, analyzes and applies a Payload (Payload) (data structure definition is shown in fig. 4 as DYNAMIC _ SYSTEM _ CONFIGURATION _ Payload) in the firmware parameter adjustment packet, as shown in fig. 3, specifically includes the following steps:
s261: judging whether payload, plantafformld = = built-in platform ID, if yes, entryindex =0; if not, the Payload non-platform applies Payload;
s262: judging whether payload is more than 0 and Entryindex is less than payload; if not, ending the process; if the condition is satisfied, go to step S263;
s263: carrying out corresponding processing according to the Payload.
S264：Entryindex++。
Specifically, in step S263: when payload.
Writing a register specified by payload.
When payload.
Reading a register specified by payload.
When payload.
Carrying out zero clearing operation on a register specified by payload.
When payload.
Performing locking (Lock) operation on a register specified by Payload.
When payload.
Unlocking (Unlock) the register specified by payload.
When payload. Entries [ EntryIndex ]. OpType = Polling,
a Polling (Polling) operation is performed on the register specified by payload.
Payload.Entries[EntryIndex].OpData.PollingExpectedValue。
If the polling time is long, polling can be performed by means of periodically triggering system management interrupt (Periodic SMI), so that the influence of blocking for too long time in the system management interrupt on the normal operation of the system is prevented. For the access mode of the register specified by payload.
The invention innovatively realizes a mechanism for dynamically adjusting the firmware parameters during the operation of the system by matching the system firmware and the BMC, and greatly improves the efficiency of testing and verifying the server.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (6)
1. A cloud server test verification method based on firmware dynamic parameter adjustment is characterized in that: firstly, triggering system management interruption by using a server BMC to send a dynamic parameter adjustment packet to system firmware; then, a processing program of the system firmware verifies the dynamic parameter adjustment packet received from the BMC, analyzes data in the packet and carries out corresponding dynamic parameter adjustment action; after the new parameter adjustment is completed, the system firmware informs the BMC that the new parameter adjustment is completed; finally, the BMC coordinates the server test validation based on the new firmware parameters that have been validated.
2. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 1, wherein: the method is divided into two aspects according to different stages in the starting and running processes of the server:
s1: initializing a system firmware dynamic parameter adjustment system management interrupt processing program in the starting process of the server, and establishing a channel for operating system runtime interaction between the BMC and the system firmware;
s2: and when the server is started and enters the operation stage of the operating system, the system performs test verification under various parameter configurations according to the test verification plan.
3. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 2, wherein: the step S1 is realized by the following steps:
s11: powering up the system and carrying out power-up self-inspection;
s12: allocating a general input/output interface GPIO connected with the BMC as a trigger source for adjusting system management interrupt by using the dynamic parameters of the system firmware;
s13: registering a system firmware dynamic parameter adjustment system management interrupt processing program;
s14: initializing a PCIE memory mapping space visible by a BMC at a host end of a server system as a shared data buffer area between the BMC and system firmware;
s15: enabling a general purpose input/output interface GPIO connected with a BMC to be used as a trigger source for adjusting system management interrupt by dynamic parameters of system firmware;
s16: and after the power-on self-test is finished, starting the operating system.
4. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 2, wherein: the step S2 is realized by the following steps:
s21: the BMC prepares a firmware parameter adjusting package which needs to be deployed during the verification and puts the firmware parameter adjusting package into a shared data buffer area;
s22: the BMC triggers system management interruption through GPIO connected with a host computer end of the server system to inform system firmware processing;
s23: the system firmware responds to the system management interrupt, and a firmware dynamic parameter registered in the power-on self-test process is called to adjust a system management interrupt processing program;
s24: the firmware dynamic parameter adjustment system manages an interrupt processing program and receives a firmware parameter adjustment packet from a shared data buffer area between the firmware dynamic parameter adjustment system and the BMC; judging whether the receiving is successful, and restarting if the BMC is informed that the receiving is unsuccessful; if the receiving is successful, go to step S25;
s25: the firmware dynamic parameter adjustment shared data buffer area verifies the signature of the firmware parameter adjustment packet; if the signature verification is not passed, notifying the BMC that the firmware parameter adjusting packet is an illegal data packet, and terminating the program; if the signature verification is passed, go to step S26;
s26: analyzing and applying the data of the firmware dynamic parameter adjustment package;
s27: and informing the BMC that the parameter adjustment is successful, and starting to perform cloud server verification based on the parameter adjustment.
5. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 4, wherein: in step S26, the firmware dynamic parameter adjustment system manages the interrupt handler, and after the signature verification of the firmware parameter adjustment package is completed to confirm the validity and security of the source, the Payload in the firmware parameter adjustment package is analyzed and applied.
6. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 5, wherein: the specific process of analysis and application is as follows:
s261: judging whether payload is carried, platform, ld = built-in platform ID, if yes, entryindex =0; if not, the Payload non-platform applies Payload;
s262: judging whether payload is more than 0 and Entryindex is less than payload; if not, the process is ended; if the condition is satisfied, go to step S263;
s263: processing according to Payload.
S264：Entryindex++。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210845820.5A CN115237429A (en) | 2022-07-18 | 2022-07-18 | Cloud server test verification method based on firmware dynamic parameter adjustment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210845820.5A CN115237429A (en) | 2022-07-18 | 2022-07-18 | Cloud server test verification method based on firmware dynamic parameter adjustment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115237429A true CN115237429A (en) | 2022-10-25 |
Family
ID=83673590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210845820.5A Pending CN115237429A (en) | 2022-07-18 | 2022-07-18 | Cloud server test verification method based on firmware dynamic parameter adjustment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115237429A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262557A (en) * | 2010-05-25 | 2011-11-30 | 运软网络科技(上海)有限公司 | Method for constructing virtual machine monitor by bus architecture and performance service framework |
| CN103514399A (en) * | 2012-06-19 | 2014-01-15 | 鸿富锦精密工业（深圳）有限公司 | Firmware verification method and system |
| CN108920722A (en) * | 2018-08-01 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of method, apparatus and computer storage medium of parameter configuration |
| CN111142956A (en) * | 2019-12-31 | 2020-05-12 | 苏州浪潮智能科技有限公司 | Method, system, device and medium for modifying maximum effective load value |
| CN111459730A (en) * | 2020-03-12 | 2020-07-28 | 苏州浪潮智能科技有限公司 | PCH (physical channel) end parameter adjusting method and system under Whitley platform |
| CN113672263A (en) * | 2021-08-23 | 2021-11-19 | 联想(北京)有限公司 | Firmware parameter update control method and device and electronic equipment |
-
2022
- 2022-07-18 CN CN202210845820.5A patent/CN115237429A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102262557A (en) * | 2010-05-25 | 2011-11-30 | 运软网络科技(上海)有限公司 | Method for constructing virtual machine monitor by bus architecture and performance service framework |
| CN103514399A (en) * | 2012-06-19 | 2014-01-15 | 鸿富锦精密工业（深圳）有限公司 | Firmware verification method and system |
| CN108920722A (en) * | 2018-08-01 | 2018-11-30 | 郑州云海信息技术有限公司 | A kind of method, apparatus and computer storage medium of parameter configuration |
| CN111142956A (en) * | 2019-12-31 | 2020-05-12 | 苏州浪潮智能科技有限公司 | Method, system, device and medium for modifying maximum effective load value |
| CN111459730A (en) * | 2020-03-12 | 2020-07-28 | 苏州浪潮智能科技有限公司 | PCH (physical channel) end parameter adjusting method and system under Whitley platform |
| CN113672263A (en) * | 2021-08-23 | 2021-11-19 | 联想(北京)有限公司 | Firmware parameter update control method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8965749B2 (en) | Demand based USB proxy for data stores in service processor complex | |
| US10754955B2 (en) | Authenticating a boot path update | |
| US8898517B2 (en) | Handling a failed processor of a multiprocessor information handling system | |
| US10462664B2 (en) | System and method for control of baseboard management controller ports | |
| US20090055157A1 (en) | Server Having Remotely Manageable Emulated Functions | |
| US20210263868A1 (en) | System and method to reduce host interrupts for non-critical errors | |
| US11816220B2 (en) | Phased boot process to dynamically initialize devices in a verified environment | |
| US11321077B1 (en) | Live updating of firmware behavior | |
| US9792437B2 (en) | System and method for securing embedded controller communications by providing a security handshake | |
| US11144326B2 (en) | System and method of initiating multiple adaptors in parallel | |
| CN116881929B (en) | Safety protection method and device, electronic equipment and substrate controller chip | |
| CN110187922B (en) | Method, device, equipment and storage medium for setting and verifying BIOS (basic input output System) parameters | |
| US11651077B2 (en) | Systems and methods for providing secured boot and scan for devices with limited access | |
| CN106570402A (en) | Encryption module and process trusted measurement method | |
| US10996942B1 (en) | System and method for graphics processing unit firmware updates | |
| CN111198832B (en) | Processing method and electronic equipment | |
| US10198275B2 (en) | Protecting firmware flashing from power operations | |
| CN115237429A (en) | Cloud server test verification method based on firmware dynamic parameter adjustment | |
| US20190356655A1 (en) | Techniques of using facial recognition to authenticate kvm users at service processor | |
| US11226862B1 (en) | System and method for baseboard management controller boot first resiliency | |
| CN115129378A (en) | Intelligent network card starting method and device capable of being actively adjusted, storage medium and equipment | |
| CN111709030B (en) | Trusted platform module board card | |
| US20200195624A1 (en) | Secure remote online debugging of firmware on deployed hardware | |
| US11977638B2 (en) | Low-impact firmware update | |
| CN117667465B (en) | Code sharing method, device, switch, multi-host system, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |