Storing EFI variables in BMC using API

By using an API to store EFI variables in a BMC via JSON format, the system addresses the challenge of managing dynamic BIOS settings, enabling efficient and centralized management of EFI variables across data centers, reducing downtime and improving system management.

JP7581295B2Active Publication Date: 2024-11-12QUANTA COMPUTER INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2022157237
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-02-09
Filing Date
2022-09-30
Publication Date
2024-11-12
Estimated Expiration
2042-09-30

AI Technical Summary

Technical Problem

Current server management systems struggle to efficiently store and manage dynamic Extensible Firmware Interface (EFI) variables, which are essential for configuring network computing systems, leading to inefficiencies in managing BIOS settings across data centers.

Method used

The system employs an application programming interface (API) to modify and store EFI variables in a baseboard management controller (BMC) using JavaScript Object Notation (JSON) format, enabling the storage and management of dynamic BIOS settings, including EFI variables, through a Redfish API, allowing for centralized management and portability across systems.

Benefits of technology

This approach allows for the efficient storage and management of dynamic BIOS settings, including EFI variables, enhancing the ability to preserve, modify, and port BIOS settings across data centers, reducing downtime and improving system management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007581295000005
    Figure 0007581295000005
  • Figure 0007581295000006
    Figure 0007581295000006
  • Figure 0007581295000007
    Figure 0007581295000007
Patent Text Reader

Abstract

To provide a network computing system and method using extendable firmware interface (EFI) variables.SOLUTION: A method includes using an application programming interface (API) to receive a changed basic input-output system (BOIS) setting. The changed BIOS setting includes an attribute describing at least one EFI variable. The method further includes storing the changed BIOS setting in a future setting data structure in a base board management controller (BMC), providing a current setting data structure stored in the BMC, replacing at least a part of the current setting data structure with the changed BIOS setting to provide the changed current setting data structure, and applying the changed current setting data structure to a computing system.SELECTED DRAWING: Figure 3
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to network computing systems, and more particularly to configuring network computing systems using Extensible Firmware Interface (EFI) variables. [Background technology]

[0002] Computing systems (e.g., servers) are used in large quantities for high-demand applications such as network-based systems or data centers. The advent of cloud computing applications has increased the demand for data centers. Data centers have a large number of servers that store data and run applications accessed by users of remotely connected computer devices. A typical data center has a physical rack structure with attendant power and communication connections. Each rack can house multiple computing and storage servers. Typically, each server includes hardware components such as processors, memory devices, network interface cards, power supplies, and other specialized hardware. Servers typically include a baseboard management controller (BMC) that manages the operation of the hardware components and supporting components such as power supplies and fans. The BMC transmits operational data over a network to a central management station that manages the servers in the rack. The BMC alleviates the need for the server's central processing unit (CPU) to monitor the operation of the server. Downtime of a data center or computing systems within a data center is a concern. The BMC can be further enhanced to not only monitor the computing systems but also manage the startup of the computing systems. Summary of the Invention [Problem to be solved by the invention]

[0003] Configuration of a network computing system using Extensible Firmware Interface (EFI) variables is provided. [Means for solving the problem]

[0004] The term embodiment and similar terms (e.g., implementation, configuration, aspect, example, and option, etc.) are intended to broadly refer to all of the inventions of this disclosure and the following claims. Descriptions containing these terms are understood not to limit the inventions described herein, nor to limit the meaning or scope of the following claims. The embodiments of the disclosure covered herein are defined by the following claims, not this Summary. This Summary is a high-level overview of various aspects of the disclosure and introduces some of the concepts that are further described in the Detailed Description section below. This Summary is not intended to identify key or essential features of the claimed invention. Nor is this Summary intended to be used alone to determine the scope of the claimed invention. The invention should be understood by reference to the entire specification of this disclosure, appropriate portions, some or all of the drawings, and each claim.

[0005] According to certain aspects of the disclosure, a system includes one or more data processors and a non-transitory computer-readable storage medium including instructions that, when executed on the one or more data processors, cause the one or more data processors to perform operations. The operations include receiving a modified basic input / output system (BIOS) setting using an application programming interface (API). The modified BIOS setting includes an attribute describing at least one Extensible Firmware Interface (EFI) variable. The operations further include storing the modified BIOS setting in a future setting data structure in a baseboard management controller (BMC). The operations further include providing a current setting data structure stored in the BMC. The operations further include replacing at least a portion of the current setting data structure with the modified BIOS setting to provide a modified current setting data structure. The modified current setting data structure is then applied to the system.

[0006] In one embodiment, the EFI variables describe attributes of an Internet Small Computer System Interface (iSCSI) device, unified EFI (UEFI) Secure Boot settings, boot order of bootable devices, TLS authentication, and / or network VLAN settings. In one embodiment, execution of the instructions further includes causing the one or more data processors to perform operations to determine whether the BIOS is performing a first boot, and based at least in part on determining that the BIOS is performing a first boot, the BIOS sending an attribute registry to the BMC. In an embodiment, the attribute registry includes definitions of attributes describing the at least one EFI variable. In an embodiment, a type key of the attribute describing the at least one EFI variable is a string. In an embodiment, the definitions of the attributes describing the at least one EFI variable do not include a default value, and the definitions of the attributes describing general BIOS settings include a default value.

[0007] In one embodiment, the API is a Redfish API. In one embodiment, the future configuration data structure and the current configuration data structure are in JavaScript® Object Notation (JSON) format. In one embodiment, execution of the instructions further causes the one or more data processors to perform operations including storing the EFI variables in the current configuration data structure. In one embodiment, storing the EFI variables in the current configuration data structure includes packing the EFI variables as a binary structure, encoding the binary structure into a string, and storing the string in the current configuration data structure as a value of an attribute. In one embodiment, storing the EFI variables in the current configuration data structure further includes compressing the binary structure before encoding the binary structure. In one embodiment, the binary structure is encoded using Base64.

[0008] In one embodiment, replacing at least a portion of the current configuration data structure stored in the BMC with the modified BIOS settings from the future configuration data structure includes receiving a string from the future configuration data structure that is a value of an attribute. The string is then decoded into a binary structure. At least a portion of the current configuration data structure is replaced with the string in the future configuration data structure based on the binary data structure being applicable in the BIOS as an EFI variable. In one embodiment, replacing at least a portion of the current configuration data structure stored in the BMC with the modified BIOS settings from the future configuration data structure further includes decompressing the binary structure after decoding the string. In one embodiment, the binary structure is decoded using Base64.

[0009] In one embodiment, replacing at least a portion of the current settings data structure with the modified BIOS settings is performed during a BIOS power-on self-test (POST). In one embodiment, the system is a server. In one embodiment, the system is a data center including at least one server. In one embodiment, any one of the current settings data structure, the future settings data structure, or the attribute registry is generated from a Unified Extensible Firmware Interface (UEFI) human interface infrastructure (HII) database of the BIOS. In one embodiment, the at least one server includes a first server and a second server, and execution of the instructions further causes the one or more data processors to perform operations including populating the current settings data structure of the first server and the associated attribute registry of the first server to the second server.

[0010] According to certain aspects of the present disclosure, a method performed by a computing system includes receiving, with an application programming interface (API), a modified basic input / output system (BIOS) setting. The modified BIOS setting includes an attribute describing at least one Extensible Firmware Interface (EFI) variable. The modified BIOS setting is stored in a future setting data structure in a baseboard management controller (BMC). A current setting data structure stored in the BMC is provided. At least a portion of the current setting data structure is replaced with the modified BIOS setting to provide a modified current setting data structure. The modified current setting data structure is applied to the computing system.

[0011] In one embodiment, the future settings data structure and the current settings data structure are in JavaScript® Object Notation (JSON) format. In one implementation, the method further includes determining whether a BIOS of the system is performing a first boot. The attribute registry is sent by the BIOS to the BMC based at least in part on determining that the BIOS is performing a first boot.

[0012] The above summary is not intended to represent each embodiment or every aspect of the present disclosure. Rather, the above summary provides only some examples of the novel aspects and features described herein. The above features and advantages of the present disclosure, as well as other features and advantages, will be readily apparent from the following detailed description of exemplary embodiments and modes for carrying out the invention, taken in conjunction with the accompanying drawings and the appended claims. Additional aspects of the present disclosure will be apparent to those skilled in the art in view of the detailed description of the various embodiments, taken in conjunction with the drawings, a brief description of which is provided below.

[0013] The present disclosure and its advantages and advantages will be better understood from the following description of exemplary embodiments and the accompanying drawings, which depict only exemplary embodiments and therefore should not be considered limiting of the various embodiments or the claims. [Brief description of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram of a computing system according to an aspect of the present disclosure. [Diagram 2] FIG. 2 is a flow diagram illustrating steps for storing boot settings according to certain aspects of the present disclosure. [Diagram 3] FIG. 2 is a flow diagram illustrating steps for applying a boot setting in a computing environment in accordance with certain aspects of the present disclosure. [Figure 4] FIG. 2 is a first flow diagram illustrating steps performed during a BIOS POST in accordance with certain aspects of the present disclosure. [Diagram 5] FIG. 4 is a second flow diagram illustrating steps performed during a BIOS POST in accordance with certain aspects of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0015] In current servers, storage of Basic Input / Output System (BIOS) settings can be beneficial for centralized management of boot settings. Stored BIOS settings can be modified, preserved, or ported from one computing device to another. Currently, only general BIOS settings can be stored in current servers. General BIOS settings are typically variables that can take binary values, such as enabled or disabled values. These general BIOS settings are static variables. These general BIOS settings can be stored in a BMC associated with the server. However, BIOS settings include settings of variables other than general BIOS settings. For example, EFI variables may need to be set, preserved, or ported, but due to the dynamic nature of EFI variables, EFI variables are not stored in the BMC. Embodiments of the present disclosure provide systems and methods for storing EFI variables in a manner similar to general BIOS settings. Embodiments of the present disclosure improve computing systems and computing infrastructure by enabling the ability to port more complete BIOS firmware and improve management of BIOS settings across data centers.

[0016] Various embodiments are described with reference to the accompanying drawings, in which like reference numerals are used to denote similar or identical elements throughout. The drawings are merely for illustrating aspects and features of the present disclosure and are not necessarily drawn to scale. Numerous specific details, relationships, and methods are shown to provide a thorough understanding of certain aspects and features of the present disclosure, but those skilled in the art will understand that these aspects and features may be performed without one or more of the specific details, with other relationships, or using other methods. In some instances, well-known structures or operations have not been described in detail for purposes of explanation. The various embodiments disclosed herein are not necessarily limited to the order of acts or events depicted, and some acts may occur in different orders and / or simultaneously with other acts or events. Not all depicted acts or events are necessarily required to implement certain aspects and features of the present disclosure.

[0017] For purposes of the detailed description, unless otherwise noted, singular includes plural and plural includes singular, where appropriate. The term "including" means "including without limitation." Additionally, terms of approximation, such as, for example, "about," "almost," "substantially," "approximately," and the like, may be used herein to include, for example, "at," "near," "nearly at," "within 3-5% of," "within manufacturing tolerances," or any logical combination thereof. Similarly, the terms "vertical" or "horizontal" are intended to additionally include "within 3-5%" of the vertical or horizontal directions, respectively. Additionally, directional terms such as "top," "bottom," "left," "right," "upper," and "lower" are intended to relate to orientations that are understood in context from the object or element being referenced, such as equivalent orientations depicted in a referenced figure, commonly used positions for the object(s) or element(s), or as otherwise described herein.

[0018] As shown in FIG. 1, a block diagram of components of a computing system 100 is provided. The computing system 100 may be a server, but any suitable computing device may incorporate the principles disclosed herein. The computing system 100 includes a circuit board 102. The circuit board 102 may be a motherboard or multiple motherboards interconnected by one or more communication cables. The circuit board 102 includes a CPU 104, a random access memory (RAM) module 106, a BMC 108, a BIOS 110, a graphics processing unit (GPU) 112, and / or input / output (I / O) ports 114.

[0019] 1 illustrates one of each of the components of computing system 100, computing system 100 may support one or more of each of these components. For example, CPU 104 may represent one or more CPUs (e.g., two CPUs, three CPUs, four CPUs, six CPUs, etc.). Similarly, RAM module 106 may represent multiple RAM modules (e.g., multiple dual in-line memory modules (DIMMs), e.g., two DIMMs, four DIMMs, eight DIMMs, etc.). GPU 112 may provide dedicated processor functionality. In some embodiments, the dedicated functionality is provided by a field programmable gate array (FPGA) and / or a complex programmable logic device (CPLD) or an expansion card provided to computing system 100.

[0020] The CPU 104 can access the RAM module 106. The CPU 104 can be communicatively coupled to a platform controller hub or chipset of the circuit board 102. The chipset of the circuit board 102 can provide access to communication standards such as, for example, Serial Advanced Technology Attachment (SATA) devices, Peripheral Component Interconnect Express (PCIe) devices, Network Interface Cards (NICs), Redundant Array of Independent Disks (RAID) cards, Small Computer System Interface (SCSI), FPGA cards, GPU 112, and the like.

[0021] In some embodiments, the GPU 112 and / or video interface allows a monitor or screen to connect to the circuit board 102. Video processing and secondary memory access (e.g., RAM module 106) typically require high speed operation and access to the CPU 104 and therefore may be connected to the CPU 104 without going through the chipset of the circuit board 102. In some implementations, the GPU 112 is a PCIe card or an Accelerated Graphics Port (AGP) card. From a high level, the I / O port 114 represents any one of these interfaces that allow input and / or output devices to interface with the computing system 100. For example, the I / O port 114 may represent a Universal Serial Bus (USB) port supporting, e.g., USB4, USB3.2, USB3.1, USB3.0, USB2.0, etc. The I / O port 114 may represent a Network Interface Controller (NIC) port supporting a wired interface, such as Ethernet, or a wireless interface, such as Bluetooth, Wi-Fi, etc. I / O ports 114 may represent other ports such as an HDMI port, a headphone jack, an external SATA (eSATA), etc. In some implementations, some ports in I / O ports 114 are coupled to CPU 104 via GPU 112. That is, GPU 112 includes ports (e.g., USB-C port, HDMI port, etc.). In some implementations, some ports in I / O ports 114 are routed through a chipset of circuit board 102 (e.g., Ethernet port, headphone jack, keyboard interface, mouse interface, parallel port, serial port, USB 3.0 port, etc.).

[0022] BIOS 110 represents a read-only memory (ROM) or flash chip provided on circuit board 102 that allows access and basic configuration of computing system 100. Upon startup of computing system 100, BIOS 110 contains instructions (or code) on how to load basic computer hardware (e.g., some of the components mentioned above, such as GPU 112, keyboard interface, mouse interface, etc.). BIOS 110 includes a self-test that runs when computing system 100 is turned on and ensures that computing system 100 meets the requirements to start up properly. The self-test is called BIOS Power-On Self-Test (POST). If computing system 100 fails the BIOS POST, a series of beeps is typically provided. The pattern of beeps can indicate which hardware component has failed. The BIOS POST will discover any basic problems. For example, the BIOS POST may provide (a) basic memory checks (e.g., checking that items can be written to and read from memory), (b) basic storage checks (e.g., checking that hard drives are up and accepting commands and / or spinning up and allowing access), (c) basic checks of input and output devices (e.g., checking that there are no stuck keys on the keyboard or that at least one keyboard or mouse is connected), etc.

[0023] BIOS 110 further includes code that allows it to locate one or more partitions of operating systems of computing system 100. BIOS 110 can sequence the operating systems based on BIOS settings. BIOS 110 reads a boot loader from a partition and facilitates loading the operating system. Once the operating system is loaded, BIOS 110 relinquishes control to the operating system. In the case of a flash BIOS, BIOS settings can be updated and these settings can ensure proper configuration of devices upon startup of computing system 100.

[0024] During a firmware update of the BIOS 110, the BIOS settings may be lost. The code in the BIOS 110 may be updated for a variety of reasons. In one example, a firmware update of the BIOS 110 may include a driver update for better control of peripherals such as a mouse and keyboard. A firmware update of the BIOS may include adding additional features such as upgrading a text-based BIOS to a graphical user interface (GUI)-based BIOS. In general, when a firmware update is made to the BIOS 110, the BIOS settings may be lost. Thus, the BMC 108 may be used to store general BIOS settings.

[0025] As shown in FIG. 2, a flow diagram illustrating a process 200 for storing BIOS settings according to certain aspects of the disclosure is provided. A user of the computing system 100 can view and control the BIOS settings stored in the BMC 108 using an application user interface (API), such as the Redfish API 202. In some embodiments, the BIOS settings are stored in a JavaScript Object Notation (JSON) format, allowing the Redfish API 202 to be used to allow a user of the computing system 100 to control the BIOS settings or to be used to port the BIOS settings from the computing system 100 to other computing systems (not shown). Although the BMC 108 is used here as an example, other locations available at boot time can be used to store the BIOS settings. The BMC 108 here is beneficial because the BMC 108 supports the Redfish API 202. In some implementations, other storage locations, including remote servers that support Redfish, can store the BIOS settings and can be accessed over a network. That is, the remote server can perform one or more functions similar to those of BMC 108 (e.g., storing BIOS settings for computing system 100, providing Redfish APIs to users, and modifying the stored BIOS settings).

[0026] General BIOS settings are not the only type of BIOS settings that can benefit from being stored in the BMC 108. The embodiments of the present disclosure allow for storing other types of BIOS settings that may have variable value lengths or may change from one boot session to another. These types of BIOS settings are not currently stored in the BMC of current servers because their value lengths are typically determined dynamically at boot time. For example, UEFI Secure Boot settings include multiple databases that store certificates / signatures, and the total number of stored certificates / signatures may change. Thus, the value lengths for storing UEFI Secure Boot settings are not static. In another example, setting the boot order of bootable devices (e.g., solid state disks, DVDROM, PXE, etc.) is not static because the number of bootable devices may change depending on the actual devices installed in the computing system 100. In another example, TLS certificates used for HTTPs booting are not static because the number of CA certificates registered in the BIOS 110 that validate the HTTPs boot server may change. In another example, the network iSCSI and VLAN settings are not static as each network port can have its own settings, and the length of the value corresponding to the total number of ports will depend on the number of network ports in computing system 100.

[0027] Therefore, to handle these dynamic BIOS settings within the BMC 110, the original schema used to describe the general BIOS settings with fixed value lengths cannot be used, and a specific schema needs to be designed for each type of dynamic BIOS setting. For example, a specific schema is needed to describe the database that stores the certificates / signatures used in UEFI Secure Boot, and another specific schema is needed to describe the iSCSI and VLAN settings of each network port. Because this process can be inefficient, some embodiments of the present disclosure provide systems and methods that handle complex dynamic BIOS settings using the original schema used to describe the general BIOS settings. These systems and methods include using EFI variables without the need to design multiple types of specific schemas for different types of dynamic variables.

[0028] The process 200 can be adapted to store not only general BIOS settings, but also dynamic BIOS settings. Dynamic BIOS settings are generally represented in EFI variables and have a different format than general BIOS settings. In data centers, current servers currently extract general BIOS settings from a UEFI Human Interface Infrastructure (HII) database, transfer the general BIOS settings as a JSON format 204, and store them in the BMC 108. The UEFI HII database is typically located in the RAM module 106 (e.g., DRAM) of the computing system 100. The UEFI HII is created in the RAM module 106 and used by the BIOS 110 during each BIOS boot to display the BIOS setup menu to the user. Since the HII database contains data from the BIOS settings, the HII creates the BIOS settings in a JSON format that is used by the BIOS 110 and used in the Redfish API 202. The values ​​or contents stored in the EFI variables are not directly stored in the HII database. Furthermore, the contents of the EFI variables are typically binary contents that are not directly available in JSON format. Embodiments of the present disclosure provide a system and method for processing EFI variables. The process 200 transfers the contents of the EFI variables as a string that can be combined with general BIOS settings in JSON format and available to be stored in the BMC 108. The ability to store EFI variables within the BMC 108 allows a user of the computing system 100 to save, modify, or populate EFI variables using the Redfish API 202 in a manner similar to general BIOS settings.

[0029] General BIOS settings are stored by the BMC 108 in three types of JSON formatted data structures that can be used with the Redfish API 202. These three types of JSON formatted data structures are an attribute registry data structure, a current settings data structure, and a future settings data structure.

[0030] The attribute registry data structure stores each option or value that a key can hold. For example, an example attribute registry is provided below. Attribute Registry Example [Table 1]

[0031] The example attribute registry described above includes key-value pairs. The attribute name key "AttributeName" identifies the attribute being set, and in this example, the attribute being set is SELS015. The attribute may have a default value (i.e., "DefaultValue" key) set to "Enable". The attribute may have a display name (i.e., "DisplayName") that provides a human identifiable name for the attribute beyond just the variable name provided by the "AttributeName" key. The attribute may have a human readable description (i.e., "HelpText") that provides more information about the attribute. In some embodiments, a "ReadOnly" key and / or a "ResetRequired" key may be set with a Boolean value of true or false to further customize the attribute. The attribute may have an associated "Type" and / or "UEFINamespaceId" key. A default value is set, but different values ​​the attribute can take can be defined in the "Value" key, which in this example can be "Enable" or "Disable".

[0032] The current settings data structure stores the current BIOS settings currently being used by computing system 100. For example, attribute SELS015 may be set to "enabled." An example of a current settings data structure is shown below: Current Configuration Example [Table 2]

[0033] The current settings data structure has a list of attribute name / value pairs. In the example above, the attribute identified by "attribute name" SELS015 has a "value" of "enabled", the attribute identified by "attribute name" SELS016 has a "value" of 10, the attribute identified by "attribute name" SETUP003 has a "value" of 5, and the attribute identified by "attribute name" SETUP005 has a "value" of false. Each attribute identified in the current settings data structure has a corresponding definition in the attribute registry data structure. The example attribute registry data structure above is just an example definition of SELS015.

[0034] The future settings data structure, like the current settings data structure, contains pairs of attribute names and one or more values. The difference between the future settings data structure and the current settings data structure is in how they are used: current settings describe the current values ​​being used by the system, while future settings describe future values ​​that will be applied when computing system 100 is reset or when computing system 100 is turned on. Additionally, a user of computing system 100 cannot change current settings, only future settings.

[0035] As shown in FIG. 3, a flow diagram illustrating a process 300 for applying a startup configuration to a computing system (e.g., computing system 100) according to certain aspects of the present disclosure is provided. In step 302, a user of computing system 100 (FIG. 2) makes a change to a BIOS setting, and the changed BIOS setting is stored in BMC 108 (FIG. 2) using Redfish API 202 (FIG. 2). In step 304, the changed BIOS setting is stored in a future settings data structure on BMC 108, and a signal to reboot the host (e.g., computing system 100) is provided. Step 302 is performed by BMC 108, and step 304 may be performed by any component capable of rebooting computing system 100 (i.e., the host system). Components capable of rebooting a computing system include BMC 108, BIOS 110, an operating system running on CPU 104, etc.

[0036] In step 306, during boot of computing system 100, BIOS 110 determines whether the current signal to boot computing system 100 (step 304) is the first boot of BIOS 110 (FIG. 2) since the last BIOS update. If this is the first boot of BIOS 110, BIOS 110 sends its attribute registry to BMC 108 in step 308. If this is not the first boot of BIOS 110, step 308 is skipped and step 310 is performed. Because the attribute registry is a large file and sending the registry every time could slow down the boot process, the attribute registry is only sent when necessary.

[0037] In step 310, BIOS 110 searches the future settings data structure stored in BMC 108 to determine whether there are any changed BIOS settings contained within the future settings data structure. If there are any changed BIOS settings within the future settings data structure, then in step 314, BIOS 110 applies the changed BIOS settings to the BIOS settings stored in BIOS 110 (i.e., the flash chip or other physical memory containing the BIOS). BIOS 110 then clears the future settings data structure from BMC 108. If there are no changed BIOS settings in step 310, then in step 312, BIOS 110 sends the current settings data structure to BMC 108.

[0038] At step 316, BIOS 110 determines whether a reboot is required to activate the settings stored in the current settings data structure at step 312. If a reboot is not required, BIOS 110 allows computing system 100 to boot into the operating system at step 318. If a reboot is required, the reboot is performed by BIOS 110 at step 304.

[0039] As shown in FIG. 4, a flow diagram illustrating a process 400 for storing EFI variables in a current settings data structure during BIOS POST in accordance with certain aspects of the present disclosure is provided. In some embodiments, all steps in FIG. 4 are performed by BIOS 110. In step 402, BIOS POST is initiated. In step 404, BIOS 110 determines whether any EFI variables need to be stored in the current settings data structure. If no EFI variables need to be stored, BIOS POST ends in step 406.

[0040] If an EFI variable needs to be stored, then in step 408, the BIOS 110 packs the EFI variable that needs to be stored as a binary structure. The binary structure may include the EFI variable name (or attribute name), a globally unique identifier (GUID), a value associated with the EFI variable, a data size, etc. An example attribute registry entry for an EFI variable is shown below: Example of an EFI variable attribute registry entry [Table 3]

[0041] An attribute registry entry for an EFI variable contains the attribute name, display name, type, minimum length of the value parameter, and maximum length of the value parameter. Since the values ​​of EFI variables are dynamic, no default value parameters are provided for EFI variables. The type parameter is shown as "String" which stores the string transferred from the EFI variable's binary structure.

[0042] In step 410, the binary structure of step 408 is optionally compressed. Any algorithm that compresses binary data can be used. In some embodiments, a proposed method described in the UEFI specification is used, namely a combination of the LZ77 algorithm and Huffman coding. As described in the UEFI specification, the UEFI BIOS usually already includes libraries that can be used for compression and decompression.

[0043] In step 412, the binary structure is encoded into an American Standard Code for Information Interchange (ASCII) string. In some embodiments, a Base64 algorithm is used to encode the binary structure into the ASCII string. In step 414, the ASCII string is stored in the current configuration data structure as the value of an attribute corresponding to the EFI variable. An example entry for the "OEMVAR_ISCSI00" attribute in the current configuration data structure is shown below: Example of current settings of EFI variables [Table 4]

[0044] As shown in FIG. 5, a flow diagram illustrating a process 500 for extracting EFI variables from a future configuration data structure during BIOS POST in accordance with certain aspects of the present disclosure is provided. In some embodiments, all steps in FIG. 5 are performed by BIOS 110. In step 502, BIOS POST is initiated. In step 504, BIOS 110 determines whether any EFI variables from the future configuration data structure need to be set in the current configuration data structure. If no EFI variables need to be set, BIOS POST ends in step 506.

[0045] If an EFI variable needs to be set, the BIOS 110 obtains an ASCII string corresponding to the EFI variable from the future configuration data structure in step 508. In step 510, the BIOS 110 decodes the ASCII string to obtain a binary structure. The decoding algorithm may be a Base64 decoding algorithm.

[0046] Optionally, in step 512, the BIOS 110 decompresses the binary structure back into an EFI variable structure.

[0047] Based on the decompressed ASCII string, the BIOS 110 modifies the EFI variable using the SetVariable UEFI BIOS service function in step 514. The binary structure obtained in step 510 is used to verify whether the binary structure is applicable to the BIOS flash as an EFI variable. If this verification process is successful, the EFI variable is modified using the SetVariable function.

[0048] By being able to represent the values ​​or contents of the EFI variables in three types of JSON data formats, a user of the computing system 100, user management software of the computing system 100, or the BMC 108 can modify, save, or populate the EFI variables via the Redfish API 202. The contents of the EFI variables can be changed if the user, management software, or BMC 108 uses the Redfish API 202 to modify the values ​​in the future settings data structure. The BMC 108 can preserve the values ​​of the EFI variables stored in the current settings data structure in the BMC 108 when updating the firmware of the BIOS 110. The values ​​of the EFI variables can then be placed in the future settings data structure to provide the updated BIOS 110 with the original values ​​of the EFI variables. If these operations are not performed, the contents of the EFI variables will be cleared and lost with the erasure of the BIOS 110 during a firmware update of the BIOS 110.

[0049] In some embodiments, a user or management software can copy (or port) the contents of EFI variables from one computing system to another computing system by copying the current settings data structure from the source system and copying it to the future settings data structure of the target system via the Redfish API 202.

[0050] Although the embodiments of the present disclosure have been described in detail with respect to one or more embodiments, equivalent alterations and modifications may occur to those skilled in the art upon reading and understanding the specification and drawings. Also, although a particular feature of the invention is described in connection with one of several embodiments, such feature may be combined with one or more other features of the other embodiments as may be desired or advantageous for a given or particular application.

[0051] While various embodiments of the present disclosure have been described above, it should be understood that they are presented by way of example and not by way of limitation. Numerous modifications to the disclosed embodiments can be made in accordance with the disclosure herein without departing from the spirit or scope of the present disclosure. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described embodiments. Rather, the scope of the present disclosure should be defined in accordance with the appended claims and their equivalents. [Explanation of symbols]

[0052] 100…Computing Systems 102...Circuit board 104…CPU 106...Random Access Memory (RAM) module 108…BMC 110…BIOS 112…Graphics Processing Unit (GPU) 114...Input / output (I / O) port 200, 300, 400, 500... Flow diagram 202…Redfish Application User Interface (API) 204...JSON format 302, 304, 306, 308, 310, 312, 314, 316, 318, 402, 404, 406, 408, 410, 412, 414, 502, 504, 506, 508, 510, 512, 514… steps

Claims

1. 1. A computing system comprising: one or more data processors; and a computer-readable storage medium containing instructions that, when executed on said one or more data processors, cause said one or more data processors to perform operations; The operation is receiving, using an application programming interface (API), a modified basic input / output system (BIOS) setting, the modified BIOS setting including an attribute describing at least one Extensible Firmware Interface (EFI) variable; storing the modified BIOS settings in a future settings data structure in a baseboard management controller (BMC); providing a current configuration data structure stored in the BMC; replacing at least a portion of the current settings data structure with the modified BIOS settings to provide a modified current settings data structure; applying the modified current configuration data structure to the computing system; and determining whether a BIOS of the computing system is performing a first boot; and based at least in part on determining that the BIOS is performing the first boot, the BIOS sending an attribute registry to the BMC. Computing system.

2. the attribute registry includes definitions of the attributes describing the at least one EFI variable; The computing system of claim 1 .

3. the type key of the attribute describing the at least one EFI variable is a string; The computing system of claim 2 .

4. the definition of the attribute describing the at least one EFI variable does not include a default value, and the definition of the attribute describing the general BIOS settings includes a default value. The computing system of claim 2 .

5. Executing the instructions further causes the one or more data processors to perform operations; The operation is storing the EFI variables in the current settings data structure. The computing system of claim 1 .

6. Storing the EFI variables in the current settings data structure includes: Packing the EFI variables as a binary structure; encoding the binary structure into a string; storing said string as a value of said attribute in said current settings data structure. The computing system of claim 5 .

7. Replacing at least a portion of the current configuration data structure with the modified BIOS configuration includes: receiving a string from the future settings data structure that is a value of the attribute; Decoding the string into a binary structure; Verifying that the binary structure is available to the BIOS as an EFI variable; and replacing at least a portion of the current configuration data structure with the string in the future configuration data structure based on the binary structure being applicable to the BIOS as an EFI variable. The computing system of claim 1 .

8. 1. A method performed by a computing system, comprising: receiving, using an application programming interface (API), a modified basic input / output system (BIOS) configuration including an attribute describing at least one Extensible Firmware Interface (EFI) variable; storing the modified BIOS settings in a future settings data structure in a baseboard management controller (BMC); providing a current configuration data structure stored in the BMC; replacing at least a portion of the current configuration data structure with the modified BIOS configuration to provide a modified current configuration data structure; applying the modified current configuration data structure to the computing system; determining whether the BIOS of the computing system is performing a first boot; and based at least in part on determining that the BIOS is performing the first boot, the BIOS sending an attribute registry to the BMC. method.

Citation Information

Patent Citations

  • IPMI data expansion method and device

    CN112003826A

  • An out-of-band BIOS upgrading method and device, equipment and a medium

    CN113064625A

  • Methods of configuring BIOS in computer system and computer program products

    JP2013156993A

  • Enabling out-of-band hardware management via an in-band communications channel

    US20190050351A1