CN115237429B - 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
- CN115237429B CN115237429B CN202210845820.5A CN202210845820A CN115237429B CN 115237429 B CN115237429 B CN 115237429B CN 202210845820 A CN202210845820 A CN 202210845820A CN 115237429 B CN115237429 B CN 115237429B
- 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.)
- Active
Links
- 238000012795 verification Methods 0.000 title claims abstract description 50
- 238000012360 testing method Methods 0.000 title claims abstract description 44
- 238000000034 method Methods 0.000 title claims abstract description 32
- 230000009471 action Effects 0.000 claims abstract description 5
- 230000008569 process Effects 0.000 claims description 13
- 230000003993 interaction Effects 0.000 claims description 3
- 238000013507 mapping Methods 0.000 claims description 3
- 238000011282 treatment Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 2
- 238000001514 detection method Methods 0.000 claims 1
- 230000007246 mechanism Effects 0.000 abstract description 4
- 238000010200 validation analysis Methods 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Virology (AREA)
- Debugging And Monitoring (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The invention discloses a cloud server test verification method based on firmware dynamic parameter adjustment, which comprises the steps of firstly, triggering a system management interrupt by a server BMC to send a dynamic parameter adjustment packet to a system firmware; then verifying the dynamic parameter adjustment package received from the BMC by the processing program of the system firmware, analyzing the data in the package, and carrying 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 server test validation based on the validated new firmware parameters. The invention is innovatively matched with the BMC by the system firmware, thereby realizing a mechanism for dynamically adjusting the firmware parameters during the system operation and greatly improving the efficiency of the test and verification of the server.
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
Servers are the core foundation of modern cloud computing centers. The current X86 architecture server is still the main stream of servers, accounting for more than 90% of the deployment volume of 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 infrastructures, and core basic servers are more and more powerful in performance and rich in functions. Taking the latest Intel X86 server platform as an example, the maximum number of cores of a single CPU reaches more than 60 cores, 8 DDR5 memory channels, 80 PCIE links, a large number of RAS (Availability/service Availability) and security characteristics are supported. Increasingly complex server systems present significant challenges for verification and deployment. The system firmware is the basis for initializing and healthy running of the server system, and comprises a large number of parameter settings which are critical for high-performance, high-reliability and high-safety operation of the server. Because the server system has complex structure, numerous components and rich firmware parameter configuration, the test verification complexity and workload of the server are rapidly increased.
The existing server test verification method generally deploys a batch of machines with typical hardware configuration, respectively sets different firmware parameter configurations and software configurations on the machines, and runs corresponding test cases (testcases) to verify various fields of server functions and performances. Most of the firmware parameters are required to be set and adjusted before running different test cases, and the server is restarted to validate the new firmware parameters.
Because of the complexity of server composition and system configuration, the existing server test verification method requires a long time for restarting the server, which is generally calculated in units of minutes, while the verification of some servers needs to be started or run under the operating system (workload), so that the server restarting needs to be restarted or run, which causes additional overhead (overhead), greatly increases the test verification time of the server system, has very low efficiency, greatly delays the product marketing period TTM (Time To Market) of the server and the time for deploying the application, and may reduce the coverage and depth of the test verification of the server.
Disclosure of Invention
The invention solves the technical problems that: the cloud server test verification method based on firmware dynamic parameter adjustment is characterized in that the system firmware and the BMC are matched to realize a mechanism for dynamically adjusting firmware parameters when the system runs, so that the efficiency of server test verification is greatly improved.
The technical scheme is as follows: in order to solve the technical problems, the invention adopts the following technical scheme:
Firstly, triggering a system management interrupt by using a server BMC to send a dynamic parameter adjustment packet to system firmware; then verifying the dynamic parameter adjustment package received from the BMC by the processing program of the system firmware, analyzing the data in the package, and carrying 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 server test validation based on the validated new firmware parameters.
Preferably, the method is divided into two aspects according to different stages in the starting and running process of the server:
S1: in the starting process of the server, a system firmware dynamic parameter adjustment system management interrupt processing program needs to be initialized, and a channel is established for the operation system running interaction between the BMC and the system firmware;
S2: and when the server is started to finish entering the operation system operation time stage, the system performs test verification under various parameter configurations according to a test verification plan.
Preferably, the implementation step of step S1 is as follows:
S11: the system is powered on and performs power-on self-checking;
s12: a general purpose input/output interface GPIO connected with the BMC is distributed as a system firmware dynamic parameter adjusting system management interrupt processing program trigger source;
S13: registering system firmware dynamic parameter adjustment system management interrupt handling program;
S14: initializing PCIE memory mapping space visible by the BMC in a server system host as a shared data buffer area with system firmware;
s15: a general purpose input/output interface GPIO connected with the BMC is used as a system firmware dynamic parameter to adjust a system management interrupt trigger source;
s16: and (5) completing the power-on self-checking and starting an operating system.
Preferably, the implementation step of step S2 is as follows:
s21: the BMC prepares a firmware parameter adjustment packet which needs to be deployed in the verification and puts the firmware parameter adjustment packet in a shared data buffer area;
S22: the BMC triggers system management interrupt through GPIO connected with a server system host end, and notifies system firmware to process;
S23: the system firmware responds to the system management interrupt, and the firmware dynamic parameter registered in the power-on self-checking process is called to adjust the system management interrupt processing program;
S24: the firmware dynamic parameter adjustment system manages an interrupt handler to receive a firmware parameter adjustment packet from a shared data buffer with the BMC; judging whether the receiving is successful or not, and restarting if the BMC is informed of unsuccessful receiving; if the reception is successful, step S25 is performed;
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, informing the BMC that the firmware parameter adjustment packet is an illegal data packet, and terminating the program; if the signature verification is passed, step S26 is performed;
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 verify the cloud server based on the parameter adjustment.
Preferably, in step S26, the firmware dynamic parameter adjustment system manages the interrupt handler, and after the verification of the firmware parameter adjustment package confirms that the source is legal and safe, the Payload in the firmware parameter adjustment package is parsed and applied.
6. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 5, wherein: the specific process of parsing and application is as follows:
S261: judging whether payload.platform ld= build-in platform ID, if yes, entryindex =0; if not, the Payload non-platform is suitable for Payload;
s262: judging whether payload.entry Num is more than 0 and Entryindex < payload.entry Num; if not, ending the flow; if the condition is satisfied, step S263 is performed;
s263: treatment was performed according to payload.Entries [ Entryindex ] OpType and Payload Entries [ Entryindex ] Address;
S264：Entryindex++。
The beneficial effects are that: compared with the prior art, the invention has the following advantages:
(1) According to the cloud server test verification method based on firmware dynamic parameter adjustment, the test verification efficiency of the server system is improved, and the breadth and the depth of the test verification of the server system are improved: because the firmware parameters can be dynamically adjusted, the expenditure of time consumed by restarting the server verification system and restarting the operating system by deploying new firmware parameters each time is avoided, and the server system verification test cases which can be completed in unit time are greatly improved. And because various firmware parameters can be conveniently combined and verified, the breadth and depth of system verification coverage can be well increased.
(2) Universality: the BMC and the like related by the invention belong to basic component units of the server, and the cooperation with the system firmware is easy to realize.
(3) And (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 in operation, and has good expansibility.
(4) Safety: the dynamic parameter adjustment package transmitted to the system firmware can go through the server platform development or the signature of the producer, and the system firmware can carry out the action of verifying the signature before analyzing the data in the use package after receiving the dynamic parameter adjustment package, so that the safety of the dynamic parameter adjustment package is ensured, and the malicious parameter adjustment data package is prevented from being used for system parameter adjustment;
(5) The invention has practical application in the verification of X86 server firmware testing of applicant (such as INTEL EAGLE STREAM platform).
Drawings
FIG. 1 is a system firmware dynamic parameter adjustment initialization process of the present invention;
FIG. 2 is a run time system firmware dynamic parameter adjustment flow of the present invention;
FIG. 3 is a firmware dynamic parameter adjustment package parsing and application of the present invention;
FIG. 4 is a related data structure of the firmware dynamic parameter adjustment package of the present invention.
Detailed Description
The invention will be further illustrated with reference to specific examples, which are carried out on the basis of the technical solutions of the invention, it being understood that these examples are only intended to illustrate the invention and are not intended to limit the scope thereof.
The invention discloses a cloud server test verification method based on firmware dynamic parameter adjustment, taking a mainstream X86 architecture cloud server as an example, and providing a server test verification method based on firmware parameter dynamic adjustment.
System firmware BIOS (Basic Input Output System): the system program is a group of system programs solidified into a memory chip on a main board of the computing device, plays an indispensable role in normal initialization, starting and operating system guiding of the computer system, and is also a key link for realizing key functions of safety, reliability and the like of the computer system.
System management Interrupt SMI (SYSTEM MANAGEMENT Interrupt): is a special management interrupt on the X86 architecture, transparent to the operating system, and is responded and processed by a system management interrupt handler (SMI HANDLER) registered by the system firmware BIOS during the boot initialization process, typically for platform specific management or implementation of additional functions.
BMC (Baseboard Management Controller): the system is a basic core function subsystem of the server, is responsible for the 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 the cloud computing industry.
The cloud server test verification method based on firmware dynamic parameter adjustment of the embodiment comprises the following steps:
Firstly, triggering a system management interrupt by using a server BMC to send a dynamic parameter adjustment packet to a system firmware; then the system management interrupt processing program of the system firmware verifies the dynamic parameter adjustment package received from the BMC, analyzes the data in the package (DYNAMIC SYSTEM configuration payload), and carries out corresponding dynamic parameter adjustment actions, including write/read/clear/lock/unlock/poll and the like of the 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 server test validation based on the validated new firmware parameters.
The present embodiment replaces the server BMC server system test with an organization coordinator (orchestration agent) that validates dynamic parameter adjustments, or with 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 process of the server:
S1: the system firmware dynamic parameter adjustment SMI HANDLER needs to be initialized during the server startup process, and a channel is established for the operation system Runtime (run) interaction between the BMC and the system firmware, specifically as shown in fig. 1, comprising the following steps:
s11: the system is powered on, and a power-on self-test (POST) of the BIOS is performed;
S12: distributing a general purpose input/Output interface GPIO (General Purpose Input/Output) connected with the BMC as a dynamic parameter of system firmware to adjust an SMI trigger source;
S13: register system firmware dynamic parameter adjustment SMI HANDLER;
S14: initializing PCIE memory mapping (Memory Mapped IO) space visible by the BMC at a Host end (namely a Host end) of the server system as a shared data buffer (sharedmemory buffer) between the BMC and system firmware;
s15: enabling a general purpose input/output interface GPIO connected with the BMC to serve as a dynamic parameter of system firmware to adjust an SMI trigger source;
S16: and finishing POST, and starting an operating system.
After the server is started and completed to enter a run time stage, the system can perform test verification under various parameter configurations according to a test verification plan. The dynamic adjustment flow of the firmware parameters before each test verification in the run time stage is shown in fig. 2, and the specific steps are as follows:
s21: the BMC prepares a firmware parameter adjustment packet which needs to be deployed in the verification and puts the firmware parameter adjustment packet in a shared data buffer area;
s22: the BMC triggers the system management interrupt to inform the system firmware of processing through GPIO connected with the host end of the server system;
S23: the system firmware responds to the system management interrupt, and the firmware dynamic parameter registered in the power-on self-checking process is called to adjust the system management interrupt processing program;
s24: the firmware dynamic parameter adjustment system manages the interrupt handler to receive the firmware parameter adjustment packet from the shared data buffer between the BMC and the interrupt handler; judging whether the receiving is successful or not, and restarting if the BMC is informed of unsuccessful receiving; if the reception is successful, step S25 is performed;
s25: the firmware dynamic parameter adjustment system management interrupt handler verifies the signature of the firmware parameter adjustment package; if the signature verification is not passed, informing the BMC that the firmware parameter adjustment packet is an illegal data packet, and terminating the firmware parameter adjustment; if the signature verification is passed, step S26 is performed;
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 cloud server verification based on the parameter adjustment.
Specifically, in step 26, the specific implementation and related data structure of the firmware dynamic parameter adjustment package are as follows:
After the firmware DYNAMIC parameter adjustment SYSTEM manages the interrupt handling program and completes verification of the validity and security of the source of the firmware parameter adjustment packet, the method analyzes and applies the Payload (Payload) in the firmware parameter adjustment packet (the data structure definition is shown as dynamic_system_configuration_payoad in fig. 4), and specifically includes the following steps:
S261: judging whether payload.plafform = build-in platform ID, if so, entryindex =0; if not, the Payload non-platform is suitable for Payload;
s262: judging whether payload.EntryNum is more than 0 and Entryindex < payload.EntryNum; if not, ending the flow; if the condition is satisfied, step S263 is performed;
S263: corresponding treatments are carried out according to payload.Entries [ Entryindex ] OpType and Payload Entries [ Entryindex ] Address;
S264：Entryindex++。
specifically, in step S263: when payload.Entricies [ EntryIndex ]. OpType =write,
Writing the payload.Entries [ EntryIndex ] and the OpData.WriteValue into a register designated by the payload.Entries [ EntryIndex ];
when payload.Entricies [ EntryIndex ]. OpType =read,
Performing a read operation on a register specified by payload.entries [ EntryIndex ] Address;
When payload.Entricies [ EntryIndex ]. OpType =clear,
Performing zero clearing operation on a register designated by payload.Entries [ EntryIndex ] Address;
when payload.Entricies [ EntryIndex ]. OpType =Lock,
Performing a Lock operation on a register specified by payload.Entries [ EntryIndex ] Address;
When payload.Entrices [ EntryIndex ]. OpType =unlock,
Performing an unlocking (Unlock) operation on a register specified by payload.Entries [ EntryIndex ] Address;
When payload.Entricies [ EntryIndex ]. OpType =polling,
The Polling (Polling) operation is performed on the register specified by payload.entries [ EntryIndex ] Address until the value of the register becomes the desired value:
Payload.Entries[EntryIndex].OpData.PollingExpectedValue。
if the polling time is long, the polling can be performed by periodically triggering a system management interrupt (Periodic SMI), so that the system is prevented from being blocked for too long in the system management interrupt to affect the normal operation of the system. The access mode of the registers specified by the payload.Entries [ EntryIndex ] Address requires different register access mechanisms (MSR/MMCFG/MMIO, etc.) to be selected according to the payload.Entries [ EntryIndex ] Address type.
The invention is innovatively matched with the BMC by the system firmware, thereby realizing a mechanism for dynamically adjusting the firmware parameters during the system operation and greatly improving the efficiency of the test and verification of the server.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.
Claims (4)
1. A cloud server test verification method based on firmware dynamic parameter adjustment is characterized in that: firstly, triggering a system management interrupt by using a server BMC to send a dynamic parameter adjustment packet to a system firmware; then verifying the dynamic parameter adjustment package received from the BMC by the processing program of the system firmware, analyzing the data in the package, and carrying 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 to perform server test verification based on the validated new firmware parameters;
according to the different stages in the start-up and operation of the server, two aspects are divided:
S1, a system management interrupt processing program needs to be initialized in the starting process of a server, and a channel is established for the operation system running interaction between the BMC and the system firmware;
S2, when the server is started to finish entering the operation system operation period, the system performs test verification under various parameter configurations according to a test verification plan; the implementation steps of the step S2 are as follows:
S21, BMC prepares firmware parameter adjustment package to be deployed in the verification and puts the firmware parameter adjustment package in a shared data buffer area;
s22, triggering system management interrupt by the BMC through GPIO connected with a server system host end, and informing the system firmware of processing;
s23, the system firmware responds to the system management interrupt, and the system management interrupt processing program is adjusted by calling the firmware dynamic parameters registered in the power-on self-test process;
S24, a firmware dynamic parameter adjustment system management interrupt processing program receives a firmware parameter adjustment packet from a shared data buffer area between the firmware dynamic parameter adjustment system management interrupt processing program and the BMC; judging whether the receiving is successful or not, and restarting if the BMC is informed of unsuccessful receiving; if the reception is successful, step S25 is performed;
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, informing the BMC that the firmware parameter adjustment packet is an illegal data packet, and terminating the program; if the signature verification is passed, step S26 is performed;
S26, analyzing and applying data of the firmware dynamic parameter adjustment package;
And S27, informing the BMC that the parameter adjustment is successful, and starting to verify the cloud server based on the parameter adjustment.
2. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 1, wherein: the implementation steps of the step S1 are as follows:
S11, powering up the system and performing power-up self-detection;
s12, distributing a general purpose input/output interface GPIO connected with the BMC as a system firmware dynamic parameter adjustment system management interrupt trigger source;
S13, registering a system firmware dynamic parameter adjustment system management interrupt handler;
s14, initializing PCIE memory mapping space visible by the BMC in a server system host as a shared data buffer area with system firmware;
s15, enabling a general purpose input/output interface GPIO connected with the BMC to serve as a system firmware dynamic parameter adjustment system management interrupt trigger source;
and S16, completing the power-on self-test and starting an operating system.
3. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 1, wherein: in step S26, the firmware dynamic parameter adjustment system manages the interrupt handler, and analyzes and applies the Payload in the firmware parameter adjustment package after verifying the tag of the firmware parameter adjustment package to confirm that the source is legal and safe.
4. The cloud server test verification method based on firmware dynamic parameter adjustment according to claim 3, wherein: the specific process of parsing and application is as follows:
S261: judging whether payload.platform ld= build-in platform ID, if yes, entryindex =0; if not, the Payload is not a Payload suitable for the present platform;
S262: judging whether payload, entry Num is more than 0 and Entryindex < payload, entry Num; if not, ending the flow; if the condition is satisfied, step S263 is performed;
S263: treatment was performed according to payload, entries [ Entryindex ] OpType and Payload Entries [ Entryindex ] Address;
S264：Entryindex++。
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210845820.5A CN115237429B (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 CN115237429B (en) | 2022-07-18 | 2022-07-18 | Cloud server test verification method based on firmware dynamic parameter adjustment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115237429A CN115237429A (en) | 2022-10-25 |
| CN115237429B true CN115237429B (en) | 2024-05-28 |
Family
ID=83673590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210845820.5A Active CN115237429B (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) | CN115237429B (en) |
Citations (8)
| 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 |
| CN111731147A (en) * | 2019-03-01 | 2020-10-02 | 通用汽车环球科技运作有限责任公司 | Modular dynamic capacity allocation storage system |
| CN113672263A (en) * | 2021-08-23 | 2021-11-19 | 联想(北京)有限公司 | Firmware parameter update control method and device and electronic equipment |
| CN114428963A (en) * | 2022-04-06 | 2022-05-03 | 浪潮(山东)计算机科技有限公司 | Server starting method, device, equipment and storage medium |
-
2022
- 2022-07-18 CN CN202210845820.5A patent/CN115237429B/en active Active
Patent Citations (8)
| 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 |
| CN111731147A (en) * | 2019-03-01 | 2020-10-02 | 通用汽车环球科技运作有限责任公司 | Modular dynamic capacity allocation storage system |
| 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 |
| CN114428963A (en) * | 2022-04-06 | 2022-05-03 | 浪潮(山东)计算机科技有限公司 | Server starting method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115237429A (en) | 2022-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8965749B2 (en) | Demand based USB proxy for data stores in service processor complex | |
| KR100524055B1 (en) | Computer system having the function of remote waking up and method for remote waking up the computer system | |
| US20090055157A1 (en) | Server Having Remotely Manageable Emulated Functions | |
| US11132314B2 (en) | System and method to reduce host interrupts for non-critical errors | |
| US9208292B2 (en) | Entering a secured computing environment using multiple authenticated code modules | |
| US10936300B1 (en) | Live system updates | |
| US11816220B2 (en) | Phased boot process to dynamically initialize devices in a verified environment | |
| EP4102359A1 (en) | Systems, apparatus and methods for rapid peripheral component interconnect express (pcie) system boot | |
| US11321077B1 (en) | Live updating of firmware behavior | |
| US9792437B2 (en) | System and method for securing embedded controller communications by providing a security handshake | |
| CN116881929B (en) | Safety protection method and device, electronic equipment and substrate controller chip | |
| US11651077B2 (en) | Systems and methods for providing secured boot and scan for devices with limited access | |
| CN115237429B (en) | Cloud server test verification method based on firmware dynamic parameter adjustment | |
| CN111709030B (en) | Trusted platform module board card | |
| US10996942B1 (en) | System and method for graphics processing unit firmware updates | |
| US20170344360A1 (en) | Protecting firmware flashing from power operations | |
| US11226862B1 (en) | System and method for baseboard management controller boot first resiliency | |
| CN108229209B (en) | BMC chip with double CPU frameworks and autonomous security improving method thereof | |
| US11977638B2 (en) | Low-impact firmware update | |
| US10003463B2 (en) | Systems and methods for revoking and replacing signing keys | |
| CN117667465B (en) | Code sharing method, device, switch, multi-host system, equipment and medium | |
| US20240028685A1 (en) | Authentication of memory expansion capabilities | |
| US20220222349A1 (en) | Information handling system host to management controller attestation service channel | |
| US20230325536A1 (en) | Power supply unit authentication | |
| US20240036744A1 (en) | Information handling system configured for authentication of memory expansion capabilities |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |