Best-Known Configuration (BKC) of nodes in a firmware framework
Systems and methods for Best Known Configuration (BKC) of nodes in a firmware framework. In some embodiments, an Information Handling System (IHS) may include a controller, where the controller comprises firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator, and a plurality of devices coupled to the controller, where each device comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a node as part of a firmware framework, and where the orchestrator is configured to apply a BKC to the plurality of nodes.
1 . An Information Handling System (IHS), comprising:
a controller, wherein the controller comprises firmware that, upon execution by a processing core, causes the processing core to instantiate an orchestrator; and
a plurality of devices coupled to the controller, wherein each device comprises firmware that, upon execution by a corresponding processing core, causes the corresponding processing core to instantiate a node as part of a firmware framework, and wherein the orchestrator is configured to apply a Best-Known Configuration (BKC) to each of the plurality of nodes based upon its confliction or interoperability with the BKC of the other nodes.
2 . The IHS of claim 1 , wherein the controller comprises an Embedded Controller (EC) or a Baseband Management Controller (BMC).
3 . The IHS of claim 1 , wherein the plurality of devices comprises at least one of: a sensor, a sensor hub, a Central Processing Unit (CPU), a Graphical Processing Unit (GPU), an audio Digital Signal Processor (aDSP), a Neural Processing Unit (NPU), a Tensor Processing Unit (TSU), a Neural Network Processor (NNP), an Intelligence Processing Unit (IPU), an Image Signal Processor (ISP), or a Video Processing Unit (VPU), a camera controller, an audio controller, a memory, a Universal Serial Bus (USB) device, a Peripheral Component Interconnect express (PCIe) device, or a Trusted Platform Module (TPM).
4 . The IHS of claim 1 , wherein at least one of the plurality of devices is coupled to the controller via at least one of: a Systems-on-Chip (SoC) interconnect, a Peripheral Component Interconnect Express (PCIe) bus, or a Universal Serial Bus (USB) port.
5 . The IHS of claim 4 , wherein the SoC interconnect comprises at least one of: an Advanced Microcontroller Bus Architecture (AMBA) bus, a QuickPath Interconnect (QPI) bus, or a HyperTransport (HT) bus.
6 . The IHS of claim 1 , wherein the BKC comprises, for each of the plurality of nodes, a set of one or more firmware modules, packages, or versions to be used during operation of the firmware framework.
7 . The IHS of claim 1 , wherein the BKC comprises, for each of the plurality of nodes, a set of one or more capabilities to be exposed during operation of the firmware framework.
8 . The IHS of claim 1 , wherein the orchestrator is configured to identify the BKC based, at least in part, upon a Look-Up Table (LUT) of different BKCs, wherein each of the different BKCs associates (i) selected one or more nodes with (ii) selected one or more firmware modules, packages, versions, or capabilities for each of the selected nodes.
9 . The IHS of claim 8 , wherein the orchestrator is configured to select the nodes, at least in part, in response to addition or removal of a given node from the firmware framework.
10 . The IHS of claim 9 , wherein the given node comprises a node external to a chassis of the IHS.
11 . The IHS of claim 8 , wherein the orchestrator is configured to select the nodes, at least in part, in response to an error metric meeting a threshold value.
12 . The IHS of claim 8 , wherein the orchestrator is configured to select the nodes, at least in part, in response to a change to an OS setting.
13 . The IHS of claim 12 , wherein the change to OS setting comprises a selection of at least one of: a performance persona, a battery persona, or a balanced persona.
14 . The IHS of claim 8 , wherein the orchestrator is configured to identify each of the different BKCs, at least in part, based upon at least one of: one or more data transfer metrics, or user feedback.
15 . The IHS of claim 1 , wherein the orchestrator is configured to identify the BKC through execution of an AI/ML model configured to select one or more firmware modules, packages, versions, or exposed capabilities for each of the plurality of nodes based, at least in part, upon context information.
16 . The IHS of claim 1 , wherein the orchestrator is configured to receive the BKC from a remote service, and wherein the remote service is configured to receive the BKC from another IHS.
17 . A method, comprising:
producing, via a controller, an orchestrator of a firmware framework; and
producing, via a plurality of devices coupled to the controller, a plurality of nodes in the firmware framework, wherein the orchestrator is configured to apply a Best-Known Configuration (BKC) of one or more firmware modules, packages, versions, or capabilities to each of the plurality of nodes based upon its confliction or interoperability with the BKC of the other nodes.
18 . The method of claim 17 , wherein to apply the BKC, the orchestrator is configured to arbitrate a conflict between a node's setting and the BKC based, at least in part, upon a policy.
19 . An Embedded Controller (EC) integrated into or coupled to a heterogeneous computing platform of an Information Handling System (IHS), the EC comprising:
a processing core distinct from any host processor of the heterogeneous computing platform; and
a memory coupled to the processing core, the memory having firmware instructions stored thereon that, upon execution by the processing core, cause the EC to:
produce an orchestrator as part of a firmware framework; and
apply, via the orchestrator, a Best-Known Configuration (BKC) of one or more firmware modules, packages, versions, or capabilities to each of the plurality of nodes based upon its confliction or interoperability with the BKC of the other nodes.
20 . The EC of claim 19 , wherein the orchestrator is configured to select a different BKC, at least in part, in response to a coupling or decoupling of an external node to the firmware framework.