Managing use of non-standard features of components of data processing systems using third-party software

Methods and systems for managing operation of a data processing system are disclosed. Hardware resources of the data processing system may issue a command for execution by a channel card of the data processing system. The channel card may be manufactured by a vendor different to a manufacturer of the data processing system. A management controller of the data processing system may identify and screen the command based on vendor software for the channel card (e.g., proprietary software of the vendor). The vendor software may be usable to facilitate use of a non-standard feature of the channel card. When the vendor software indicates that the command implicates use of the non-standard feature, the command may be modified by the management controller. The modified command may be used to initiate execution of the non-standard feature by the channel card to facilitate provisioning of a computer-implemented service.

1. 11. A method for managing operation of a data processing system, the method comprising: making an identification, by a management controller of the data processing system, that hardware resources of the data processing system have issued a command, wherein the hardware resources of the data processing system comprise a channel card and a processor that issued the command based on execution of a program thereon, the management controller is physically installed within the data processing system and is separate from and tasked with managing operations of the hardware resources, and the command being for execution by the channel card, the channel card being manufactured by a vendor different to a manufacturer of the data processing system; and based on the identification: screening, by the management controller and using vendor software for the channel card, the command, the vendor software being proprietary software of the vendor and the vendor software being usable for facilitating use of a non-standard feature of the channel card, and in a first instance of the screening where the vendor software indicates that the command implicates use of the non-standard feature: modifying, by the management controller and using the vendor software, the command to obtain a non-standard feature customized command; and initiating, by the management controller, execution of the non-standard feature customized command by the channel card to facilitate provisioning of a computer-implemented service.
2. 22. The method of claim 1, wherein to perform the screening, the management controller monitors the processor to identify and intercept issued commands transparently to the processor.
3. 33. The method of claim 1, wherein the vendor software is adapted to obtain user input indicating whether the non-standard feature is to be utilized during processing by the channel card.
4. 44. The method of claim 3, wherein the user input is based on an interaction between the management controller and a user of the data processing system, the user desiring the computer-implemented service to be provided.
5. 55. The method of claim 1, wherein the non-standard feature of the channel card is based on standard features of a type of channel card, and the standard features of the type of the channel card are based on an industry standard with which the channel card is compliant.

FIELD
Embodiments disclosed herein relate generally to managing operation of data processing systems. More particularly, embodiments disclosed herein relate to systems and methods to manage use of non-standard features of components of the data processing systems.
BACKGROUND
Computing devices may provide computer-implemented services. The computer-implemented services may be used by users of the computing devices and/or devices operably connected to the computing devices. The computer-implemented services may be performed with hardware components such as processors, memory modules, storage devices, and communication devices. The operation of these components and the components of other devices may impact the performance of the computer-implemented services.



BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments disclosed herein are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
FIG. 1A shows a block diagram illustrating a system in accordance with an embodiment.
FIG. 1B shows a block diagram illustrating components of a data processing system in accordance with an embodiment.
FIGS. 2A-2B show interaction diagrams in accordance with an embodiment.
FIG. 3 shows a flow diagram illustrating a method in accordance with an embodiment.
FIG. 4 shows a block diagram illustrating a data processing system in accordance with an embodiment.



DETAILED DESCRIPTION
Various embodiments will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative and are not to be construed as limiting. Numerous specific details are described to provide a thorough understanding of various embodiments. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments disclosed herein.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment. The appearances of the phrases “in one embodiment” and “an embodiment” in various places in the specification do not necessarily all refer to the same embodiment.
References to an “operable connection” or “operably connected” means that a particular device is able to communicate with one or more other devices. The devices themselves may be directly connected to one another or may be indirectly connected to one another through any number of intermediary devices, such as in a network topology.
In general, embodiments disclosed herein relate to methods and systems for managing operation of a data processing system. The data processing system may provide computer-implemented services. To provide the computer-implemented services, hardware resources of the data processing system such as memory, processors, channel cards, etc., may operate in cooperation with one another. To do so, during manufacturing of the data processing system, the manufacturer may prepare the data processing system with firmware, drivers, and/or configuration settings that support the cooperative operation of the hardware resources included in the data processing system at its time of manufacturing (e.g., stock hardware components).
For example, a processor of the data processing system may interact with a channel card of the data processing system to facilitate provision of the computer-implemented services. The channel card may include, for example, a graphics card, a sound card, a storage card, and/or other types of hardware components of the data processing system that may be added, removed and/or replaced. To interact with the channel card, the processor may issue native commands (e.g., commands designed specifically for the processor that may be recognized by the channel card) that invoke known functionality of the channel card.
Over time (e.g., after an end user obtains the data processing system from the manufacturer), stock hardware components of the data processing system may be modified. For example, portions of the stock hardware components may be replaced, added, removed, and/or otherwise modified to improve performance of the data processing system. However, if a stock hardware component is modified, then any firmware, drivers, and/or configuration settings associated with the modified hardware component may be required to be updated so that the hardware resources may continue to operate cooperatively.
For example, the user may replace a stock channel card of the data processing system with an aftermarket channel card. The aftermarket channel card may include a channel card with different (e.g., additional) functionality from the stock channel card. For example, the aftermarket channel card may include standard features (e.g., known functionality, based on a current or preceding industry standard with which the aftermarket channel card is compliant) and non-standard features. The non-standard features may be additional to those of the industry standard (e.g., functionality not known by the stock hardware components), and therefore may not be natively invokable via commands issued by the stock hardware components and/or software hosted thereon. For example, native commands issued by the stock hardware resources may not include instructions for activating the non-standard functionality.
Thus, to utilize the non-standard features of the aftermarket channel card, operation of the hardware resources may be required to be reconfigured and/or otherwise updated (e.g., via software, firmware, and/or driver updates) by the user and/or via a remote system. However, this may present security risks and opportunities for error. For example, the host system (e.g., the hardware resources and software hosted thereon) may be compromised via communication channels established with a remote system when obtaining third-party (update) software and/or via the software itself (e.g., if the update software includes malware). Consequently, updates made to the hardware resources using third-party software may lead to disruptions to the computer-implemented services and/or an inability for the data processing system to provide the computer-implemented services. A third-party may include any entity (e.g., a vendor) other than the manufacturer of the data processing system.
Thus, to improve the likelihood of providing the computer-implemented services in view of modified hardware components of the data processing system, interactions between aftermarket hardware components and stock hardware components of the data processing system may be managed. To do so, the data processing system may include out-of-band (hardware) components (e.g., a management controller). The out-of-band components may operate independently from in-band components (e.g., the hardware resources) of the data processing system. The out-of-band components may obtain (e.g., via secure out-of-band communication channels), host (e.g., separately from the in-band components), and/or otherwise manage third-party software adapted to facilitate interactions between the stock hardware components and the aftermarket hardware components (e.g., aftermarket channel cards) of the data processing system.
The third-party software may include vendor software for an aftermarket hardware component (e.g., software that is proprietary to a manufacturer of the aftermarket hardware component). The third-party software may be obtained using out-of-band methods (e.g., by the out-of-band hardware components and/or via out-of-band secure communication channels), and may provide a mechanism for invoking non-standard features of the channel cards when providing the computer-implemented services. For example, the third-party software may translate (e.g., map) native commands issued by stock hardware components of the data processing system to customized commands recognized by the channel cards that may invoke the non-standard features.
By doing so, embodiments disclosed herein may provide a system for managing operation of a data processing system in a manner that increases the likelihood of facilitating desired computer-implemented services while reducing the likelihood of compromise of the host system and/or disruptions to the computer-implemented services after modifications to the hardware resources.
Thus, embodiments disclosed herein may address, among others, the technical problem of managing interactions that include aftermarket modified portions of hardware resources of data processing systems. By managing the interactions automatically and locally (e.g., without user intervention, using out-of-band components of the data processing systems), the data processing systems may be more likely to provide the desired computer-implemented services in a secure manner.
In an embodiment, a method for managing operation of a data processing system is provided. The method may include making an identification, by a management controller of the data processing system, that hardware resources of the data processing system have issued a command, the command being for execution by a channel card of the data processing system, and the channel card being manufactured by a vendor different to a manufacturer of the data processing system. Based on the identification, the method may include screening, by the management controller and using vendor software for the channel card, the command, the vendor software being proprietary software of the vendor and the vendor software being usable for facilitating use of a non-standard feature of the channel card.
In a first instance of the screening where the vendor software indicates that the command implicates use of the non-standard feature, the method may include: modifying, by the management controller and using the vendor software, the command to obtain a non-standard feature customized command; and, initiating, by the management controller, execution of the non-standard feature customized command by the channel card to facilitate provisioning of a computer-implemented service.
The management controller may be separate from and tasked with managing operation of the hardware resources, the hardware resources including the channel card and a processor that issued the command based on execution of a program thereon. To perform the screening, the management controller may monitor the processor to identify and intercept issued commands transparently to the processor.
The vendor software may be adapted to obtain user input indicating whether the non-standard feature is to be utilized during processing by the channel card. The user input may be based on an interaction between the management controller and a user of the data processing system, the user desiring the computer-implemented service to be provided.
The non-standard feature of the channel card may be based on standard features of a type of channel card, and the standard features of the type of the channel card may be based on an industry standard with which the channel card is compliant. The non-standard feature may be a capability of the channel card that is additional to those of the industry standard, and may not be natively invokable by the hardware resources and software hosted thereon.
The method may further include, prior to making the identification and by the management controller: obtaining the vendor software for the channel card from a remote system; performing, using the vendor software for the channel card, a feature identification process for the channel card to identify the non-standard feature; obtaining, using the vendor software for the channel card, user input regarding use of the non-standard feature; and, configuring the vendor software for the channel card based on the user input.
The vendor software may be adapted to translate commands to modified commands. The vendor software may be further adapted to facilitate updating of firmware of the channel card. Obtaining the vendor software may include: providing the vendor software to other management controllers of other data processing systems that host similar channel cards to the channel card to facilitate use of similar non-standard features.
A non-transitory media may include instructions that when executed by a processor cause the computer-implemented method to be performed.
A data processing system may include the non-transitory media and a processor, and may perform the computer-implemented method when the computer instructions are executed by the processor.
Turning to FIG. 1A, a block diagram illustrating a system in accordance with an embodiment is shown. The system shown in FIG. 1A may provide computer-implemented services. The computer-implemented services may include any type and quantity of computer-implemented services. For example, the computer-implemented services may include data storage services, instant messaging services, database services, data generation services, and/or any other type of service that may be implemented with a computing device. The computer-implemented services may be provided, at least in part, using various components of hardware resources of the data processing system, such as channel cards (e.g., graphics cards, network interface cards (NICs), accelerator cards, expansion cards).
To provide the computer-implemented services, hardware components of the data processing system may interact with one another cooperatively. For example, the computer-implemented services may require cooperative interaction between processors, memory modules, storage devices, and/or the channel cards. Based on these interactions, the hardware components may support execution of any number and/or types of software components (e.g., applications hosted by the hardware components), and, in some combination, the hardware and software components may provide for various types of computer-implemented services.
The interactions between the hardware and/or software components may depend on the presence of appropriate firmware, drivers, configuration data, and/or configuration settings of the data processing system that support the cooperative interactions. For example, a channel card of the data processing system may require that specialized firmware be installed to the data processing system, and the specialized firmware may define commands that, when issued to the channel card, may activate a feature of the channel card necessary for providing desired computer-implemented services. Thus, during setup (e.g., manufacturing) of the data processing systems, the appropriate firmware, drivers, configuration data, and/or configuration settings that reflect functionality of existing (e.g., stock) hardware components of the data processing system may be installed.
Over time (e.g., after manufacturing or setup), hardware components such as channel cards may be modified (e.g., by an end user). For example, a stock channel card may be replaced with an aftermarket channel card, and/or aftermarket channel cards may be added to the data processing system. Functionality of the aftermarket channel cards may vary to a high degree depending on their vendor (e.g., manufacturer of the channel card) and/or due to the programmable nature of some channel cards (SmartNICs, data processing unit (DPU) cards, etc.).
For example, channel cards may include programmable platform devices capable of performing various functions in various different ways and/or some may require special methods of communication (e.g., specialized application programming interfaces (APIs)). In other words, some functionality/features of the channel cards may (i) not adhere to an industry standard for similar types of channel cards, (ii) may be in addition to the functionality specified by the industry standard, and/or (iii) may otherwise require specialized or unusual information to utilize such functions/features. These functions or features may be referred to as non-standard features. Therefore, the host system (e.g., the stock hardware components and software hosted thereon, added by the manufacturer during manufacturing and that may only include capabilities to natively interact with industry standard functionalities/features) may be unable to natively invoke the non-standard features of the channel cards without using third-party proprietary drivers and/or APIs for the channel cards.
However, obtaining and/or hosting third-party software (for the aftermarket channel cards) may present security risks. For example, establishing connections with remote sources to obtain the third-party software may expose the host system to attacks where sensitive data accessible via (e.g., stored on) the host system may be compromised and/or malicious data may be introduced to the host system. In addition, for example, modifications made to a software stack (e.g., during installation of the third-party software) of the host system may result in errors when performed by an unseasoned user or when performed for a complex network of computers. Consequently, the introduction of third-party software to the host system may negatively impact functionality of the hardware resources and therefore the computer-implemented services. In general, embodiments disclosed herein may provide methods, systems, and/or
devices for managing operation of data processing system in a manner that facilitates use of non-standard features of aftermarket channel cards. To do so, the data processing system may include out-of-band (hardware) components, such as a management controller. The out-of-band components may operate independently from the hardware resources of the data processing system and may be tasked with managing third-party software for (aftermarket) channel cards.
For example, the third-party software may be obtained by the management controller via out-of-band communication channels that may be less susceptible to compromise than in-band communication channels of the hardware resources. Once obtained, the third-party software may be hosted and/or otherwise managed by the management controller, separately from hardware components of the host system. The third-party software may be used to manage interactions between the (stock) hardware components and the channel cards so that non-standard features of the channel cards may be utilized. For example, the third-party software may translate native commands (e.g., commands issued by the stock hardware components) for the channel cards to customized commands that may invoke the non-standard features.
By doing so, embodiments disclosed herein may facilitate use of non-standard features of channel cards of data processing systems in a manner that reduces the likelihood of compromise of the host system in view of using third-party software for the channel cards. The system may do so by obtaining and running the third-party software out of band.
To provide the above-mentioned functionality, the system of FIG. 1A may include data processing system 102, vendor system 104, and communication system 106. Data processing system 102 may include hardware resources 150 and management controller 152. The system, any components thereof, and/or any other types of devices or components not shown in FIG. 1A may perform all, or a portion of the computer-implemented services independently and/or cooperatively. Each of these components is discussed below.
Hardware resources 150 may include any number of hardware components (e.g., memory, processors, channel cards). For example, hardware resources 150 may include any number of channel cards 154 (e.g., 154A-154N). Channel cards 154 may include expansion cards and/or adapter cards that may add specific functions/features to data processing system 102. Each channel card of channel cards 154 may be designed to perform a specific task and/or provide additional capabilities to data processing system 102 (e.g., beyond what other hardware components such as a motherboard of data processing system 102 may offer). For example, channel cards 154 may include graphics processing units (GPUs), network interface cards (NICs), storage controller cards, wireless network cards, Universal Serial Bus (USB) expansion cards, and/or other types of cards. Channel cards 154 may include any number of stock channel cards (e.g., installed by a manufacturer of data processing system 102) and/or aftermarket channel cards (e.g., added by a user of data processing system 102). Channel cards 154 may function in cooperation with other components of hardware resources 150.
Hardware resources 150 may host applications and/or other software, and store and/or execute instructions provided by the applications and/or the software in order to facilitate provision of a computer-implemented service. For example, based on the instructions, a processor of data processing system 102 may interact with channel card 154A of data processing system 102 by issuing instructions (e.g., commands) to channel card 154A. Upon reading and/or executing the instructions, channel card 154A may perform a desired function in cooperation with the processor and/or other hardware components of hardware resources 150.
To support cooperative interactions between aftermarket (e.g., additional, replacement) channel cards and other hardware components of hardware resources 150, management controller 152 may manage third-party software for the aftermarket channel cards. The third-party software may be adapted to translate commands to modified commands. For example, the third-party software may include schemas (e.g., rule sets) usable to map the native commands to the non-standard commands and/or complex algorithms for invoking non-standard features of the channel cards based on commands issued by a processor of hardware resources 150.
As part of managing the third-party software, management controller 152 may, for example, (i) obtain third-party software for aftermarket channel cards (e.g., vendor software) installed on data processing system 102 from a remote system such as vendor system 104, (ii) identify features (e.g., non-standard features) of the aftermarket channel cards using the third-party software, (iii) obtain user input regarding use of the features, and/or (iv) configure the third-party software based on the features and/or the user input. Settings of the third-party software may be configured, for example, based on a type of non-standard feature desired to be available to the user. Refer to the discussion of FIG. 2A for more details regarding obtaining third-party software.
To obtain the third-party software for any of the aftermarket channel cards installed on data processing system 102, management controller 152 may establish connections with vendor system 104. Vendor system 104 may include any number of systems remote to data processing system 102 and may be managed by a manufacturer/vendor of channel cards different to a manufacturer/vendor of data processing system 102. Vendor system 104 may provide software for facilitating functionality of one of channel cards 154 such as channel card 154A. The vendor software may be proprietary to the vendor of channel card 154A and therefore may include third-party software for data processing system 102. The vendor software for channel card 154A may be configured to facilitate use of user desired non-standard features of channel card 154A.
Using the (configured) third-party software, management controller 152 may manage command processing for data processing system 102. For example, management controller 152 may (i) screen commands destined to the channel cards to identify whether any desired non-standard features of the channel cards are implicated in the commands, (ii) modify the commands to obtain non-standard feature customized commands capable of invoking the desired non-standard features, (iii) provide the non-standard feature customized commands to the channel cards, and/or (vi) perform other operations for managing operation of data processing system 102 and/or components thereof. Refer to the discussion of FIG. 2B for additional details regarding invoking of non-standard features of hardware components using third-party software.
Management controller 152 may be distinct from and/or may operate independently from hardware resources 150. To facilitate cooperation between hardware resources 150 and management controller 152, hardware resources 150 may host an agent for management controller 152 (not shown). The agent (e.g., a software program) may facilitate communication between management controller 152 and hardware resources 150. Refer to the discussion of FIG. 1B for more information regarding the functionality of management controller 152.
When providing their functionality, any of data processing system 102, vendor system 104, and/or components thereof may perform all, or a portion of the actions and methods illustrated in FIGS. 2A-3.
Any of data processing system 102 (and/or components thereof) and vendor system 104 may be implemented using a computing device (also referred to as a data processing system) such as a host or a server, a personal computer (e.g., desktops, laptops, and tablets), a “thin” client, a personal digital assistant (PDA), a Web enabled appliance, a mobile phone (e.g., smartphone), an embedded system, local controllers, an edge node, and/or any other type of data processing device or system. For additional details regarding computing devices, refer to the discussion of FIG. 4.
Any of the components illustrated in FIG. 1A may be operably connected to each other (and/or components not illustrated) with communication system 106. Communication system 106 may facilitate communications between the components of FIG. 1A. In an embodiment, communication system 106 includes one or more networks that facilitate communication between any number of components. The networks may include wired networks and/or wireless networks (e.g., and/or the Internet). The networks and communication devices may operate in accordance with any number and types of communication protocols (e.g., such as the Internet protocol).
While illustrated in FIG. 1A as including a limited number of specific components, a system in accordance with an embodiment may include fewer, additional, and/or different components than those illustrated therein.
Turning to FIG. 1B, a diagram illustrating components of a data processing system in accordance with an embodiment is shown. The components of the data processing system shown in FIG. 1B may be similar to those of data processing system 102 of in FIG. 1A.
To provide computer-implemented services, data processing system 102 may include any quantity of hardware resources 150. Hardware resources 150 may be in-band hardware components, and may include a processor operably coupled to memory, storage, channel cards, and/or other hardware components.
The processor may host various management entities such as operating systems, drivers, network stacks, and/or other software entities that provide various management functionalities. For example, the operating system and drivers may provide abstracted access to various hardware resources. Likewise, the network stack may facilitate packaging, transmission, routing, and/or other functions with respect to exchanging data with other devices.
For example, the network stack may support transmission control protocol/internet protocol communication (TCP/IP) (e.g., the Internet protocol suite) thereby allowing the hardware resources 150 to communicate with other devices via packet switched networks and/or other types of communication networks.
The processor may also host various applications that provide the computer-implemented services. The applications may utilize various services provided by the management entities and use (at least indirectly) the network stack to communicate with other entities.
However, use of the network stack and the services provided by the management entities may place the applications at risk of indirect compromise. For example, if any of these entities trusted by the applications are compromised, these entities may subsequently compromise the operation of the applications. For example, if various drivers and/or the communication stack are compromised, communications to/from other devices may be compromised. If the applications trust these communications, then the applications may also be compromised.
For example, to communicate with other entities, an application may generate and send communications to a network stack and/or driver, which may subsequently transmit a packaged form of the communication via channel 170 to a communication component, which may then send the packaged communication (in a yet further packaged form, in some embodiments, with various layers of encapsulation being added depending on the network environment outside of data processing system 102) to another device via any number of intermediate networks (e.g., via wired/wireless channels 176 that are part of the networks).
To reduce the likelihood of the applications and/or other in-band entities from being indirectly compromised, data processing system 102 may include management controller 152 and network module 160. Each of these components of data processing system 102 is discussed below.
Management controller 152 may be implemented, for example, using a system on a chip or other type of independently operating computing device (e.g., independent from the in-band components, such as hardware resources 150, of a host data processing system 102). For example, management controller 152 may host third-party software (e.g., vendor software for an aftermarket channel card of data processing system 102) separately from hardware resources 150 in order to avoid indirect compromise of software and/or network stacks hosted by hardware resources 150 by potentially malicious third-party software. Management controller 152 may provide various management functionalities for data processing system 102. For example, management controller 152 may monitor various ongoing processes performed by the in-band components, may manage power distribution, may participate in thermal management, and/or other may perform other functions, such as identifying and/or intercepting commands sent between the in-band components.
To do so, management controller 152 may be operably connected to various components via sideband channels 174 (in FIG. 1B, a limited number of sideband channels are included for illustrative purposes, it will be appreciated that management controller 152 may communicate with other components via any number of sideband channels such as 174A shown in FIG. 2A). The sideband channels may be implemented using separate physical channels, and/or with a logical channel overlay over existing physical channels (e.g., logical division of in-band channels). The sideband channels may allow management controller 152 to interface with other components and implement various management functionalities such as, for example, general data retrieval (e.g., to snoop ongoing processes), telemetry data retrieval (e.g., to identify a health condition/other state of another component), function activation (e.g., sending instructions that cause the receiving component to perform various actions such as displaying data, adding data to memory, causing various processes to be performed), and/or other types of management functionalities.
For example, sideband channels 174 may facilitate communications between management controller 152 and hardware resources 150 so that management controller 152 may identify and/or intercept commands issued by a processor of hardware resources 150 destined for a channel card of hardware resources 150. Management controller 152 may host vendor software for the channel card that may facilitate screening of the commands and/or command translation to obtain customized commands for the channel card. Management controller 152 may use sideband channels 174 to provide the customized commands to the channel card (and/or another hardware component of hardware resources 150).
To reduce the likelihood of indirect compromise of an application hosted by hardware resources 150, management controller 152 may enable information from other devices to be provided to the application without traversing the network stack and/or management entities of hardware resources 150. To do so, the other devices may direct communications including the information to management controller 152. Management controller 152 may then, for example, send the information via sideband channels 174 to hardware resources 150 (e.g., to store it in a memory location accessible by the application, such as a shared memory location, a mailbox architecture, or other type of memory-based communication system) to provide it to the application. Thus, the application may receive and act on the information without the information passing through potentially compromised entities. Consequently, the information may be less likely to also be compromised, thereby reducing the possibility of the application becoming indirectly compromised. Similarly, processes may be used to facilitate outbound communications from the applications.
Management controller 152 may be operably connected to communication components of data processing system 102 via separate channels (e.g., 172, 172A shown in FIG. 2A) from the in-band components, and may implement or otherwise utilize a distinct and independent network stack (e.g., TCP/IP). Consequently, management controller 152 may communicate with other devices independently of any portion of the in-band components (e.g., does not rely on any hosted software, hardware components, etc.). Accordingly, compromise of any of hardware resources 150 and hosted component may not result in indirect compromise of any management controller 152, and entities hosted by management controller 152.
To facilitate communication with other devices, data processing system 102 may include network module 160. Network module 160 may provide communication services for in-band components and out-of-band components (e.g., management controller 152) of data processing system. To do so, network module 160 may include traffic manager 162 and interfaces 164.
Traffic manager 162 may include functionality to (i) discriminate traffic directed to various network endpoints advertised by data processing system 102, and (ii) forward the traffic to/from the entities associated with the different network endpoints. For example, to facilitate communications with other devices, network module 160 may advertise different network endpoints (e.g., different media access control address/internet protocol addresses) for the in-band components and out-of-band components. Thus, other entities may address communications to these different network endpoints. When such communications are received by network module 160, traffic manager 162 may discriminate and direct the communications accordingly (e.g., over channel 170 or channel 172, in the example shown in FIG. 1B, it will be appreciated that network module 160 may discriminate traffic directed to any number of data units and direct it accordingly over any number of channels).
Accordingly, traffic directed to management controller 152 may never flow through any of the in-band components. Likewise, outbound traffic from the out-of-band component may never flow through the in-band components. For example, management controller 152 may obtain (or provide) vendor software from (or to) remote systems via a secure out-of-band communication channels (e.g., channel 172) independently from and/or without traversing a network stack of hardware resources 150.
To support inbound and outbound traffic, network module 160 may include any number of interfaces 164. Interfaces 164 may be implemented using any number and type of communication devices which may each provide wired and/or wireless communication functionality. For example, interfaces 164 may include a wide area network card, a Wi-Fi card, a wireless local area network card, a wired local area network card, an optical communication card, and/or other types of communication components. These components may support any number of wired/wireless channels 176.
Thus, from the perspective of an external device, the in-band components and the out-of-band components of data processing system 102 may appear to be two independent network entities, that may independently addressable, and otherwise unrelated to one another.
To facilitate management of data processing system 102 over time, hardware resources 150, management controller 152 and/or network module 160 may be positioned in separately controllable power domains. By being positioned in these separately power domains, different subsets of these components may remain powered while other subsets are unpowered.
For example, management controller 152 and network module 160 may remain powered while hardware resources 150 is unpowered. Consequently, management controller 152 may remain able to communication with other devices even while hardware resources 150 are inactive. Similarly, management controller 152 may perform various actions while hardware resources 150 are not powered and/or are otherwise inoperable, unable to cooperatively perform various process, are compromised, and/or are unavailable for other reasons.
To implement the separate power domains, data processing system 102 may include a power source (e.g., 180) that separately supplies power to power rails (e.g., power rail 184, power rail 186) that power the respective power domains. Power from the power source (e.g., a power supply, battery, etc.) may be selectively provided to the separate power rails to selectively power the different power domains. A power manager (e.g., 182) may manage power from power source 180, and power may be supplied via the power rails. Management controller 152 may cooperate with power manager 182 to manage supply of power to these power domains. Management controller 152 may communicate with power manager 182 via sideband channels 174 and/or via other means.
In FIG. 1B, an example implementation of separate power domains using power rails 184-186 is shown. The power rails may be implemented using, for example, bus bars or other types of transmission elements capable of distributing electrical power. While not shown, it will be appreciated that the power domains may include various power management components (e.g., fuses, switches, etc.) to facilitate selective distribution of power within the power domains.
To further clarify embodiments disclosed herein, interaction diagrams in accordance with an embodiment are shown in FIGS. 2A-2B. These interaction diagrams may illustrate how data may be obtained and used within the system of FIGS. 1A-1B. In the examples shown in
FIGS. 2A-2B, a data processing system (e.g., 102) may include components such as hardware resources 150 and management controller 152. As shown with respect to FIG. 2B, hardware resources 150 may include hardware component 151 and channel card 154A. The components of the data processing system may be similar to and/or include functionality similar to those described with respect to FIGS. 1A-1B.
In the interaction diagrams, processes performed by and interactions between components of a system in accordance with an embodiment are shown. In the diagrams, components of the system are illustrated using a first set of shapes (e.g., 104, 152), located towards the top of the figure. Lines descend from these shapes. Processes performed by the components of the system are illustrated using a second set of shapes (e.g., 204, 254, etc.) superimposed over these lines.
Interactions (e.g., communication, data transmissions, etc.) between the components of the system are illustrated using a third set of shapes (e.g., 202, 206) that extend between the lines. The third set of shapes may include lines terminating in one or two arrows. Lines terminating in a single arrow may indicate that one-way interactions (e.g., data transmission from a first component to a second component) occur, while lines terminating in two arrows may indicate that multi-way interactions (e.g., data transmission between two components) occur. Lines drawn in dashing may indicate that the corresponding interactions are optional and/or may not occur during operation of the system for various reasons.
Generally, the processes and interactions are temporally ordered in an example order, with time increasing from the top to the bottom of each page. For example, the interaction labeled as 206 may occur prior to the interaction labeled as 208. However, it will be appreciated that the processes and interactions may be performed in different orders, any may be omitted, and other processes or interactions may be performed without departing from embodiments disclosed herein.
Turning to FIG. 2A, a first interaction diagram in accordance with an embodiment is shown. The first interaction diagram may illustrate flows of data and processing of data that may occur when managing non-standard features of hardware components of a data processing system.
In the example shown in FIG. 2A, hardware resources 150 of the data processing system may include any number of channel cards. For example, channel card 154A may be installed to the data processing system after its time of manufacturing and/or after a recent setup of the data processing system; therefore, the data processing system may not include appropriate firmware, drivers, and/or other software necessary to utilize at least a portion of features offered by the channel card 154A.
To identify presence of channel card 154A, management controller 152 may communicate with hardware resources 150. For example, at interaction 202, data may be exchanged between any of hardware resources 150 and management controller 152 by (i) transmission via a message, (ii) storing in a storage with subsequent retrieval by the recipient (e.g., either management controller 152 or hardware resources 150), (iii) a publish-subscribe system where one of management controller 152 and hardware resources 150 subscribes to updates from the other thereby causing a copy of the data to be propagated to the recipient, and/or (iv) other processes. The data exchange may occur, for example, via sideband channel 174A (e.g., of sideband channels 174 of FIG. 1B).
For example, during startup of the data processing system, management controller 152 may identify that channel card 154A is present in the system (e.g., during a secured component verification process and/or via a notification from a startup management entity of the data processing system). Management controller 152 may be provided with (and/or may request) identifying information for channel card 154A such as a model number, a card type, etc. The identifying information may indicate that channel card 154A is manufactured by a vendor different to that of the data processing system and/or that functionality of channel card 154A may include non-standard features not natively invokable by hardware resources 150 (e.g., using software hosted by hardware resources 150).
Thus, to manage use of non-standard features of channel card 154A, management controller 152 may perform software update process 204. During software update process 204, third-party software for channel card 154A (e.g., software proprietary to the vendor of channel card 154A) may be obtained. To do so, management controller 152 may request vendor software from vendor system 104, based on identifying information for channel card 154A.
At interaction 206, a request may be provided to vendor system 104 by management controller 152 by (i) transmission via a message, (ii) storing in a storage with subsequent retrieval by vendor system 104, (iii) a publish-subscribe system where vendor system 104 subscribes to updates from management controller 152 thereby causing a copy of the request to be propagated to vendor system 104, and/or (iv) other processes. The request may be provided, for example, via out-of-band channel 172A (e.g., a communication channel similar to channel 172 of FIG. 1B). By providing the request to vendor system 104, vendor system 104 may provide third-party software services.
As part of the third-party software services, vendor system 104 may identify vendor software suitable for facilitating use of non-standard features of channel card 154A based on information received in the request. For example, the request may include identifying information for channel card 154A and/or identifying information for the data processing system (e.g., management controller 152). The vendor software may include a software plug-in and/or other types of software for invoking the non-standard features of channel card 154A. The vendor software may be included in a response to the request along with other information.
At interaction 208, the response to the request may be provided to management controller 152 by vendor system 104 via out-of-band channel 172A by (i) transmission via a message, (ii) storing in a storage with subsequent retrieval by management controller 152, (iii) a publish-subscribe system where management controller 152 subscribes to updates from vendor system 104 thereby causing a copy of the response to be propagated to management controller 152, and/or (iv) other processes. Upon obtaining the response, management controller 152 may use the vendor software to manage functionality of channel card 154A.
Upon establishing that management controller 152 is managing functionality of channel card 154A, management controller 152 may obtain update notifications from vendor system 104 (not shown). For example, vendor system 104 may notify management controller 152 when updated vendor software is available.
During software update process 204, management controller 152 may store, install, and/or execute instructions included in the response locally (e.g., without involving hardware resources 150). For example, using the vendor software, management controller 152 may (i) identify non-standard features of channel card 154A, and (ii) obtain user input regarding the identified non-standard features. The user input may be used to configure the vendor software so that commands managed (e.g., translated, modified) using the configured vendor software invoke non-standard functionality of channel card 154A in a manner that meets the needs of the user.
To identify the non-standard features of channel card 154A, management controller 152 may perform a feature identification process. To initiate the feature identification process, management controller 152 may execute instructions included in the vendor software. For example, the vendor software may include a list of features of channel card 154A (e.g., functionalities channel card 154A is capable of performing), and/or may be adapted to prompt channel card 154A for such information. Channel card 154A may include hardware components such as memory, processors, etc., and may include a discovery protocol. Therefore, a list of features supported by channel card 154A may be populated upon execution of the vendor software.
During the feature identification process, using the vendor software, management controller 152 may use the list of features to identify the non-standard features of channel card 154A. For example, management controller 152 may compare the list of features with a list of industry standard features for the card type (e.g., a class of card, such as a sound card, a graphics card, a network card) of channel card 154A. The non-standard features may include capabilities of channel card 154A that are additional to those of the industry standard for the card type (e.g., that are not found on the list of industry standard features for the card type). The non-standard features may not be natively invokable by any of hardware resources 150.
For example, hardware resources 150 may include a processor, and channel card 154A may include a performance sound card. Prior to a user installing the performance sound card to the data processing system, the data processing system may have been configured to use an integrated sound card for audio transmission. The integrated sound card may include standard features such as generating and recording audio; therefore, the processor may be configured to issue commands for generating and/or recording audio. However, the performance sound card may include non-standard features in addition to the standard features, such as data caching and/or data processing, and the processor may not be configured to issue such commands.
To provide functionality for invoking non-standard features of channel card 154A, during software update process 204, user input regarding the non-standard features may be obtained. To do so, using the vendor software, management controller 152 may communicate with a portion of hardware resources 150. For example, management controller 152 may provide instructions for obtaining user input to a processor of hardware resources 150. The instructions may be provided to hardware resources 150 by management controller 152 at interaction 210 using methods similar to those described with respect to interaction 202 and/or by other methods.
For example, management controller 152 may use a sideband channel to instruct its host system (e.g., hardware resources 150) to generate a pop-up interface (e.g., graphical user interface ((GUI)) through which the user may provide user input. The GUI may display, for example, the non-standard features (e.g., and/or standard features) of channel card 154A, and the user may be prompted to make a selection regarding use of the non-standard features (e.g., and/or standard features). The user may select a portion of the non-standard and/or standard features of channel card 154A. The user's selection, along with other information (e.g., identifying information for the user and/or other metadata), may be included in a data package (e.g., the user input), and the data package may be provided to (or collected by) management controller 152 from hardware resources 150 at interaction 210 using methods similar to those described with respect to interaction 202 and/or by other methods.
During software update process 204 (e.g., at interaction 210), management controller 152 may also provide information regarding the user's selection to the host system (e.g., via hardware resources 150). The information may indicate to the host system that management controller 152 may potentially modify (e.g., customize) commands issued to channel card 154A with respect to the user selected non-standard features. The host system may use the information to flag potential security issues with respect to modifying such commands and/or for other purposes.
Based on the user input regarding use of the non-standard features, management controller 152 may configure the vendor software for channel card 154A to reflect the user's selections. As a result, the vendor software may be configured to translate commands issued by hardware resources 150 to modified commands for channel card 154A. The modified commands may invoke user selected non-standard features that may otherwise not have been invoked by the commands. Thus, the modified command may include a non-standard feature customized command.
Returning to the performance sound card example, the user may desire to use the data caching and the data processing features of the performance sound card. The vendor software for the performance sound card may be configured to modify a (native) command that instructs the performance sound card to emit a sound (based on an audio file) from a speaker to a modified (e.g., non-standard feature customized) command that instructs the performance sound card to cache and process the audio file before emitting a sound (based on the processed audio file) from the speaker. The configured vendor software may function based on a set of predetermined criteria, which may include user-specified criteria. For example, the performance sound card may only be instructed to cache and/or process audio files based on characteristics of the audio file (e.g., file size, file type) and/or based on data processing system activity (e.g., usage levels of any of hardware resources 150).
In some examples, during software update process 204, management controller 152 may facilitate firmware updates for channel card 154A. The vendor software may include instructions for updating the firmware of channel card 154A and/or (new) firmware for channel card 154A. Therefore, when executed, the vendor software may modify how channel card 154A performs command processing so that commands issued to channel card 154A from hardware resources 150 do not require interception and/or modification by the vendor software running locally on management controller 152. Instead, the modification of the command may be performed locally by channel card 154A.
In addition to command modification/translation, once executed, the vendor software may publish data regarding channel card 154A to other systems. The published data may include information usable by an administrative console to facilitate management of non-standard features of channel card 154A. For example, the vendor software may publish the data to an administrative console (e.g., operated by an administrator of a deployment that includes the data processing system) that allows remote activation of non-standard features of channel card 154A (e.g., by the administrator) that may otherwise be unknown to the administrative console.
During software update process 204, management controller 152 may document updates made to vendor software for channel card 154A. For example, the (configured) vendor software may be included in a data package (along with other information) and the data package may be exported to other systems, such as a management system tasked with managing third-party software for a deployment. For example, while not shown in FIG. 2A, management controller 152 may provide the data package via an out-of-band communication channel to the management system that may distribute the data package to data processing systems of the deployment that host channel cards similar to channel card 154A. Therefore, in some examples, management controller 152 may receive (configured) vendor software (e.g., for channel card 154A) from a remote management system and/or from management controllers of other data processing systems.
Thus, the processes and interactions shown in FIG. 2A may be used to obtain and configure vendor software for hardware components (e.g., aftermarket channel cards) of a data processing system. The vendor software may provide for an interface for invoking non-standard features of the hardware components, independently from hardware resources 150.
Turning to FIG. 2B, a second interaction diagram in accordance with an embodiment is shown. The second interaction diagram may illustrate flows of data and processing of data that may occur when invoking non-standard features of (aftermarket) hardware components of the data processing system.
To determine whether non-standard features of channel card 154A should be invoked, management controller 152 may obtain (e.g., intercept) a command issued to channel card 154A from hardware component 151 of hardware resources 150 of the data processing system. For example, hardware component 151 may include a processor attempting to invoke a feature of channel card 154A via the command.
At interaction 252, the command may be provided to channel card 154A by hardware component 151 by transmission via a message and/or by other methods. However, management controller 152 may monitor activity of hardware resources 150 (e.g., hardware component 151) and may include functionality for identifying and/or intercepting commands issued to channel card 154A and/or other hardware components of hardware resources 150. For example, management controller 152 may identify and/or intercept the commands transparently (e.g., surreptitiously) to the processor and/or other hardware components of hardware resources 150. Obtaining (e.g., intercepting) the command by management controller 152 may include preventing channel card 154A from receiving the command for at least a period of time, as indicated by the dashed arrow of interaction 252A.
The command issued to channel card 154A by hardware component 151 may include a command that includes instructions for invoking standard features of channel card 154A, but may not include instructions for invoking non-standard features of channel card 154A. To determine whether non-standard features of channel card 154A should be invoked, management controller 152 may perform command modification process 254.
During command modification process 254, management controller 152 may identify (configured) vendor software associated with channel card 154A. For example, management controller 152 may identify (e.g., select) the vendor software for channel card 154A obtained via processes and interactions described with respect to FIG. 2A. Management controller 152 may use (e.g., execute portions of) the vendor software for channel card 154A to screen the command to determine whether the command implicates use of non-standard features of channel card 154A.
If the command does not implicate use of any non-standard features of channel card 154A, then management controller 152 may make the (native) command available to channel card 154A. For example, management controller 152 may provide the command to channel card 154A using methods similar to those described with respect to interaction 210 of FIG. 2A and/or by other methods (not shown).
If the command implicates use of a non-standard feature of channel card 154A, then management controller 152 may use the vendor software to translate the command to a non-standard feature customized command. The non-standard feature customized command may include instructions additional (e.g., appended) to existing instructions of the command to obtain the non-standard feature customized command. For example, the non-standard feature customized command may include instructions that may improve the coordinated operation of components of the data processing system in view of non-standard features of channel card 154A.
Returning to the performance sound card example, a processor of the data processing system may issue commands for depowering the data processing system. For example, time-dependent shutdown commands may be issued by the processor to specific hardware components of hardware resources 150 (e.g., power controllers). The time-dependent shutdown commands may be pre-programmed at a time of manufacturing of the data processing system based, at least in part, on the stock hardware components present at the time of manufacturing. However, the performance sound card (not present at the time of manufacturing) may require additional time to perform shut-down related functions associated with its non-standard features. For example, to avoid data loss, the performance sound card may require additional time to clear cached data from memory and/or to offload data to persistent storage. Therefore, when management controller 152 intercepts the commands for depowering the data processing system, the vendor software for the performance sound card may be configured to modify amounts of time specified in the shutdown instructions and/or the vendor software may instruct management controller 152 to hold intercepted depowering commands for a period of time.
At interaction 256, the modified command (e.g., the non-standard feature customized command) may be provided to channel card 154A by management controller 152 using methods similar to those described with respect to interaction 210 of FIG. 2A and/or by other methods. The modified command may be provided to channel card 154A for execution.
Upon obtaining the modified command, channel card 154A may perform execution process 258. During execution process 258, channel card 154A may execute instructions included in the modified command and/or other instructions (e.g., stored locally) to participate in provision of a computer-implemented service. By doing so, a non-standard feature of channel card 154A may be utilized to provide user desired computer-implemented services without re-configuring operation of hardware resources 150.
While described as having management controller 152 intercept the command issued from hardware component 151, management controller 152 may instead have configured (e.g., pre-programmed) channel card 154A to perform command modifications in accordance with the interaction model prior to issuance of the command (e.g., during a firmware update using vendor software). In this case, when commands are issued by hardware resources 150, management controller 152 may not be required to intercept and/or modify the commands since channel card 154A may already include instructions for performing any necessary command modifications, as well as for executing the modified command rather than the command itself.
Thus, the processes and interactions shown in FIG. 2B, interaction models may be used by a management controller of a data processing system to invoke non-standard features of hardware components of its host system without a need to reconfigure the host system.
Any of the processes illustrated using the second set of shapes and interactions illustrated using the third set of shapes may be performed, in part or whole, by digital processors (e.g., central processors, processor cores, etc.) that execute corresponding instructions (e.g., computer code/software). Execution of the instructions may cause the digital processors to initiate performance of the processes. Any portions of the processes may be performed by the digital processors and/or other devices. For example, executing the instructions may cause the digital processors to perform actions that directly contribute to performance of the processes, and/or indirectly contribute to performance of the processes by causing (e.g., initiating) other hardware components to perform actions that directly contribute to the performance of the processes.
Any of the processes illustrated using the second set of shapes and interactions illustrated using the third set of shapes may be performed, in part or whole, by special purpose hardware components such as digital signal processors, application specific integrated circuits, programmable gate arrays, graphics processing units, data processing units, and/or other types of hardware components. These special purpose hardware components may include circuitry and/or semiconductor devices adapted to perform the processes. For example, any of the special purpose hardware components may be implemented using complementary metal-oxide semiconductor-based devices (e.g., computer chips).
Any of the processes and interactions may be implemented using any type and number of data structures. The data structures may be implemented using, for example, tables, lists, linked lists, unstructured data, data bases, and/or other types of data structures. Additionally, while described as including particular information, it will be appreciated that any of the data structures may include additional, less, and/or different information from that described above. The informational content of any of the data structures may be divided across any number of data structures, may be integrated with other types of information, and/or may be stored in any location.
Turning to FIG. 3, a flow diagram illustrating a method in accordance with an embodiment is shown. The flow diagram may illustrate various operations performed while managing operation of a data processing system. The data processing system may include hardware resources and a management controller, and may be similar to the data processing system discussed with respect to FIGS. 1A-1B.
At operation 302, an identification that hardware resources of the data processing system have issued a command may be made. The identification may be made by (i) monitoring activity of the hardware resources, (ii) obtaining a notification (e.g., from the hardware resources) indicating that the command has been issued, and/or (iii) via other methods. The identification may be made by the management controller. The management controller of the data processing system may be separate from the hardware resources (e.g., may operate independently of the hardware resources) and may be tasked with managing operation of the hardware resources (e.g., including the channel card).
For example, the hardware resources may include a processor, and the processor may have issued the command based on execution of a program thereon. To identify issuance of the command, the management controller may monitor activity of the processor and may identify a portion of the activity that indicates that the command has been issued. Information included in the command (e.g., a data package of instructions) may indicate that the command may be for execution by a channel card of the data processing system.
The channel card may be manufactured by a vendor different to a manufacturer of the data processing system. For example, the channel card may be installed to the data processing system after a time of manufacturing (e.g., initial setup) of the data processing system by a user or administrator of the system.
Prior to operation 302, the management controller may (i) obtain vendor software (e.g., proprietary software of the vendor of the channel card) for the channel card, (ii) perform, using the vendor software for the channel card, a feature identification process for the channel card to identify a non-standard feature of the channel card, (iii) obtain, using the vendor software for the channel card, user input regarding use of the non-standard feature, and (iv) configure the vendor software for the channel card based on the user input.
The vendor software may be obtained, for example, by (i) reading the vendor software from storage, (ii) receiving the vendor software (e.g., from another device), and/or (iii) via other methods. For example, the vendor software may be obtained by the management controller from a remote server (e.g., a vendor system) using an out-of-band channel. Refer to interactions 206 and 208 of FIG. 2A for more details regarding obtaining the vendor software, and the discussion of FIG. 1B for more details regarding out-of-band communication.
The feature identification process may be performed using methods similar to at least a portion of those discussed with respect to software update process 204 of FIG. 2A. For example, performing the feature identification process may include executing at least a first portion of the vendor software locally (e.g., by the management controller). The first portion of the vendor software may include instructions for performing and/or initiating a discovery process for the channel card to obtain a list of features of the channel card (as well as other information regarding the channel card). The list of features of the channel card may be compared to a list of industry standard features for the type of the channel card to identify the non-standard feature of the channel card.
For example, standard features of the channel card may be based on an industry standard with which the channel card is compliant. The non-standard feature may be distinct from the standard features defined by the industry standard. For example, the non-standard feature may be a capability of the channel card that is additional to those of the industry standard and that is not natively invokable by the hardware resources (e.g., the processor) and software hosted thereon.
Obtaining the user input regarding use of the non-standard feature may include executing at least a second portion of the vendor software locally (e.g., by the management controller). The vendor software may be adapted to obtain user input indicating whether the non-standard feature is to be utilized during processing by the channel card. For example, the second portion of the vendor software may include instructions for (i) obtaining a list of non-standard features of the channel card (e.g., including the non-standard feature), and (ii) prompting the user to provide the user input based on the list of non-standard features. The user input may be based on an interaction between the management controller and a user of the data processing system, the user desiring the computer-implemented service to be provided.
For example, the management controller may provide instructions to the hardware resources that, once executed, initiate a pop-up GUI that displays the list of non-standard features of the channel card and that indicates that user input regarding use of the non-standard feature is requested. The vendor software may be configured based, at least in part, on the user input indicating whether the non-standard feature is to be utilized during processing by the channel card.
Configuring the vendor software may include modifying settings of the vendor software to reflect the user input. The vendor software may be adapted (e.g., configured) to translate commands to modified commands (e.g., non-standard feature customized commands) that invoke non-standard features of the channel card. For example, the user may specify that the non-standard function is to be used during command processing of the channel card, and the settings of the vendor software may be modified so that functionality of the non-standard feature is activated. The configured vendor software may be stored in local memory of the management controller.
The vendor software may be adapted to facilitate updating of firmware of the channel card. Updating the firmware may include programming the channel card to (i) perform command translation locally and/or (ii) to reflect improvements for the channel card issued by the manufacturer (e.g., to fix bugs, improve performance, enhance security, introduce new features, etc.). The channel card may be programmed by updating instructions stored in local memory of the channel card.
Obtaining the vendor software may also include exporting a data structure (e.g., the configured vendor software) to other management controllers of other data processing systems that host similar channel cards to the channel card to facilitate use of similar non-standard features. The data structure may be exported to other systems, for example, by the management controller, by transmitting the data structure to the other data processing systems via a communication channel (e.g., out-of-band communication channels established between the management controller and the other management controllers of the other systems). For more details regarding obtaining vendor software, refer to software update process 204 of FIG. 2A.
At operation 304, based on the identification, the command may be screened using the (configured) vendor software for the channel card. The command may be screened, at least in part, by the management controller. For example, the command may be screened by (i) identifying the vendor software for the channel card (e.g., from a repository of vendor software for various hardware components of the data processing system), and (ii) executing at least a portion of the vendor software so that the vendor software reads and/or processes the command.
To perform the screening, the management controller may monitor activity of the hardware resources (e.g., the processor) to identify and intercept issued commands transparently to the processor. For example, the management controller may perform the screening process (e.g., execute the vendor software) independently and surreptitiously (e.g., without notifying the processor). The screening process may include (i) obtaining a list of features invoked by the command (e.g., parsing the command), and (ii) comparing the list of features invoked by the command to the list of non-standard features of the channel card to identify whether the list of features includes any of the non-standard features.
At operation 306, a determination may be made regarding whether vendor software indicates that the command implicates use of the non-standard feature. The determination may be made based on a result of the screening. For example, the vendor software may publish a notification that the non-standard feature has been invoked. Otherwise, the vendor software may publish a notification indicating that the command does not invoke use of the non-standard feature.
If the vendor software does not indicate that the command implicates use of the non-standard feature, then the method end following operation 306. Otherwise, the method may proceed to operation 308 following operation 306.
At operation 308, the command may be modified using the vendor software to obtain a non-standard feature customized command. The command may be modified, at least in part, by the management controller. The command may be modified by allowing (by the management controller) execution of the vendor software to process the command. For example, the vendor software may (i) append instructions to the command, (ii) replace at least a portion of the command with a modified command, and/or (iii) use other methods to translate the command. The non-standard feature customized command may include instructions that invoke the non-standard feature of the channel card and/or standard features of the channel card.
At operation 310, execution of the non-standard feature customized command by the channel card may be initiated to facilitate provisioning of a computer-implemented service. The execution of the non-standard feature may be initiated by providing the non-standard feature customized command to the channel card using methods similar to those described with respect to interaction 256 of FIG. 2B and/or by other methods. The execution of the non-standard feature customized command may be initiated, at least in part, by the management controller.
The computer-implemented service may be facilitated and/or provided, in part, upon execution of at least a portion of the instructions included in the non-standard feature customized command by the channel card. For example, the channel card may execute the instructions included in the non-standard feature customized command in cooperation with execution of other instructions by other hardware resources of the data processing system to provide the computer-implemented service.
The method may end following operation 310.
Thus, as illustrated above, embodiments disclosed herein may provide systems and methods usable to manage operation of a data processing system using (third-party) vendor software that facilitates use of non-standard features of hardware components of the data processing system. The vendor software may be managed and executed separately from the hardware components by a management controller of the data processing system. By doing so, the non-standard features may be supported by the data processing system without a need for reconfiguration of hardware resources of the data processing system, and in a manner that reduces a risk of compromise of the hardware resources when using third-party software.
Thus, embodiments disclosed herein may provide an improved computing device that is able to invoke non-standard features of hardware components in a manner that reduces a likelihood of interruptions to the computer-implement services, and that reduces risk associated with reconfiguration of software hosted by hardware resources of the device and/or installation of third-party software to the host system. Accordingly, the disclosed process provides for both an embodiment in computing technology and an improved method for managing operation of the data processing system.
Any of the components illustrated in FIGS. 1A-3 may be implemented with one or more computing devices. Turning to FIG. 4, a block diagram illustrating an example of a data processing system (e.g., a computing device) in accordance with an embodiment is shown. For example, system 400 may represent any of data processing systems described above performing any of the processes or methods described above. System 400 can include many different components. These components can be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules adapted to a circuit board such as a motherboard or add-in card of the computer system, or as components otherwise incorporated within a chassis of the computer system. Note also that system 400 is intended to show a high-level view of many components of the computer system. However, it is to be understood that additional components may be present in certain implementations and furthermore, different arrangement of the components shown may occur in other implementations. System 400 may represent a desktop, a laptop, a tablet, a server, a mobile phone, a media player, a personal digital assistant (PDA), a personal communicator, a gaming device, a network router or hub, a wireless access point (AP) or repeater, a set-top box, or a combination thereof. Further, while only a single machine or system is illustrated, the term “machine” or “system” shall also be taken to include any collection of machines or systems that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
In one embodiment, system 400 includes processor 401, memory 403, and devices 405-407 via a bus or an interconnect 410. Processor 401 may represent a single processor or multiple processors with a single processor core or multiple processor cores included therein. Processor 401 may represent one or more general-purpose processors such as a microprocessor, a central processing unit (CPU), or the like. More particularly, processor 401 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 401 may also be one or more special-purpose processors such as an application specific integrated circuit (ASIC), a cellular or baseband processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, a graphics processor, a network processor, a communications processor, a cryptographic processor, a co-processor, an embedded processor, or any other type of logic capable of processing instructions.
Processor 401, which may be a low power multi-core processor socket such as an ultra-low voltage processor, may act as a main processing unit and central hub for communication with the various components of the system. Such processor can be implemented as a system on chip (SoC). Processor 401 is configured to execute instructions for performing the operations discussed herein. System 400 may further include a graphics interface that communicates with optional graphics subsystem 404, which may include a display controller, a graphics processor, and/or a display device.
Processor 401 may communicate with memory 403, which in one embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. Memory 403 may include one or more volatile storage (or memory) devices such as random-access memory (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or other types of storage devices. Memory 403 may store information including sequences of instructions that are executed by processor 401, or any other device. For example, executable code and/or data of a variety of operating systems, device drivers, firmware (e.g., input output basic system or BIOS), and/or applications can be loaded in memory 403 and executed by processor 401. An operating system can be any kind of operating systems, such as, for example, Windows® operating system from Microsoft®, Mac OS®/iOS® from Apple, Android® from Google®, Linux®, Unix®, or other real-time or embedded operating systems such as Vx Works.
System 400 may further include IO devices such as devices (e.g., 405, 406, 407, 408) including network interface device(s) 405, optional input device(s) 406, and other optional IO device(s) 407. Network interface device(s) 405 may include a wireless transceiver and/or a network interface card (NIC). The wireless transceiver may be a Wi-Fi transceiver, an infrared transceiver, a Bluetooth transceiver, a WiMAX transceiver, a wireless cellular telephony transceiver, a satellite transceiver (e.g., a global positioning system (GPS) transceiver), or other radio frequency (RF) transceivers, or a combination thereof. The NIC may be an Ethernet card.
Input device(s) 406 may include a mouse, a touch pad, a touch sensitive screen (which may be integrated with a display device of optional graphics subsystem 404), a pointer device such as a stylus, and/or a keyboard (e.g., physical keyboard or a virtual keyboard displayed as part of a touch sensitive screen). For example, input device(s) 406 may include a touch screen controller coupled to a touch screen. The touch screen and touch screen controller can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen.
IO devices 407 may include an audio device. An audio device may include a speaker and/or a microphone to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and/or telephony functions. Other IO devices 407 may further include universal serial bus (USB) port(s), parallel port(s), serial port(s), a printer, a network interface, a bus bridge (e.g., a PCI-PCI bridge), sensor(s) (e.g., a motion sensor such as an accelerometer, gyroscope, a magnetometer, a light sensor, compass, a proximity sensor, etc.), or a combination thereof. IO device(s) 407 may further include an imaging processing subsystem (e.g., a camera), which may include an optical sensor, such as a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, utilized to facilitate camera functions, such as recording photographs and video clips. Certain sensors may be coupled to interconnect 410 via a sensor hub (not shown), while other devices such as a keyboard or thermal sensor may be controlled by an embedded controller (not shown), dependent upon the specific configuration or design of system 400.
To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage (not shown) may also couple to processor 401. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a solid-state device (SSD). However, in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as an SSD cache to enable non-volatile storage of context state and other such information during power down events so that a fast power up can occur on re-initiation of system activities. Also, a flash device may be coupled to processor 401, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including a basic input/output software (BIOS) as well as other firmware of the system.
Storage device 408 may include computer-readable storage medium 409 (also known as a machine-readable storage medium or a computer-readable medium) on which is stored one or more sets of instructions or software (e.g., processing module, unit, and/or processing module/unit/logic 428) embodying any one or more of the methodologies or functions described herein. Processing module/unit/logic 428 may represent any of the components described above. Processing module/unit/logic 428 may also reside, completely or at least partially, within memory 403 and/or within processor 401 during execution thereof by system 400, memory 403 and processor 401 also constituting machine-accessible storage media. Processing module/unit/logic 428 may further be transmitted or received over a network via network interface device(s) 405.
Computer-readable storage medium 409 may also be used to store some software functionalities described above persistently. While computer-readable storage medium 409 is shown in an exemplary embodiment to be a single medium, the term “computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-readable storage medium” shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of embodiments disclosed herein. The term “computer-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media, or any other non-transitory machine-readable medium.
Processing module/unit/logic 428, components and other features described herein can be implemented as discrete hardware components or integrated in the functionality of hardware components such as ASICS, FPGAs, DSPs, or similar devices. In addition, processing module/unit/logic 428 can be implemented as firmware or functional circuitry within hardware devices. Further, processing module/unit/logic 428 can be implemented in any combination hardware devices and software components.
Note that while system 400 is illustrated with various components of a data processing system, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to embodiments disclosed herein. It will also be appreciated that network computers, handheld computers, mobile phones, servers, and/or other data processing systems which have fewer components, or perhaps more components may also be used with embodiments disclosed herein.
Some portions of the preceding detailed descriptions have been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as those set forth in the claims below, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
Embodiments disclosed herein also relate to an apparatus for performing the operations herein. Such a computer program is stored in a non-transitory computer readable medium. A non-transitory machine-readable medium includes any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a machine-readable (e.g., computer-readable) medium includes a machine (e.g., a computer) readable storage medium (e.g., read only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices).
The processes or methods depicted in the preceding figures may be performed by processing logic that comprises hardware (e.g., circuitry, dedicated logic, etc.), software (e.g., embodied on a non-transitory computer readable medium), or a combination of both. Although the processes or methods are described above in terms of some sequential operations, it should be appreciated that some of the operations described may be performed in a different order. Moreover, some operations may be performed in parallel rather than sequentially.
Embodiments disclosed herein are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of embodiments disclosed herein.
In the foregoing specification, embodiments have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the embodiments disclosed herein as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.